Loose coupling is always a good idea. After all, what's wrong with abstracting away separate layers of concern, creating pluggability points, making your design more flexible, and creating a software ...
A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...
Some of the tools you use in building applications also apply as you build out your services. The Single Responsibility Principle (SRP), for example, makes as much sense at the service level as it ...
In my previous post, I discussed the virtues of loosely coupling, rising it to the level of an IT commandment. One reader, Richard Veryard, responded in his own Weblog, however, that maybe loose ...
Get an overview of design patterns, then use what you've learned to evaluate whether the Composite pattern is a good choice for a particular Java use case Numerous strategies have been devised to ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results