Yahoo Answers is shutting down on May 4th, 2021 (Eastern Time) and beginning April 20th, 2021 (Eastern Time) the Yahoo Answers website will be in read-only mode. There will be no changes to other Yahoo properties or services, or your Yahoo account. You can find more information about the Yahoo Answers shutdown and how to download your data on this help page.

Compare/Contrast loose coupling & strongly typed?

Studying SOA design (especially service integration), I come from a legacy mainframe background & I'm currently a messaging specialist.

What is the best description of the difference between loose coupling & strong typing as they relate to service interfaces.

I think I understand. But I'd appreciate a second explanation. THX.

1 Answer

Relevance
  • Pfo
    Lv 7
    1 decade ago
    Favorite Answer

    Loose coupling can be more dynamic, giving programmers more options as to how they can organize and key on data. It provides a simpler interface for logic.

    Strongly-typing is less dynamic and more specific. Strongly-typing usually enforces a lot of compile time constraints and or runtime error checking to ensure that code is executing properly and that interfaces are talking to each other correctly.

    I prefer strong-typing. It may be harder to design, but it's worth its weight in gold for large projects where your code won't compile if it might work incorrectly. Loosely coupled systems can be more bug prone and can also be a nightmare to debug.

Still have questions? Get your answers by asking now.