>web services where the http routing layer is the actual public interface definition and so you're benefiting from strong encapsulation at that layer this is a

>web services where the http routing layer is the actual public interface definition and so you're benefiting from strong encapsulation at that layer this is actually one of the best ways anyone has put it. You may be right. I have often wondered how does the huge amount of Ruby/Python/JS work in building large companies and products, when Java mandates all this amount of massive complexity. You may be right here - in the web services world, the hard contract of the API layer makes up for less strict encapsulation everywhere else.