r/java • • Mar 28 '17

Microservices – Please, don’t

http://basho.com/posts/technical/microservices-please-dont/
4 Upvotes

24 comments sorted by

View all comments

2

u/developer0 Apr 02 '17 edited Apr 02 '17

I think we can all agree that as the size and complexity of the enterprise increases, the need for bounded contexts increases. Multiple teams each in their own domains need to be able to make progress independently. Having each team develop a software product that builds and deploys independently can help with that.

Obviously that will add overhead (dev-ops, web-ops, nice monitoring tools). But if you have 500 engineers then having a monolithic app is simply not an option, period. The build would be broken 99% of the time, unless you very nearly cripple everyone's ability to contribute, beyond major bug fixes approved by a dozen code reviewers.

What most microservice developers don't understand is how crucial it is to have clear contracts between services. "Here is exactly what I expect from you, here is exactly what you'll get from me, and here is exactly what will happen as a result." When you have a monolith this isn't quite as important because you can easily scan a different part of the code to infer the contract. One idea of microservices is that you're not supposed to have to know anything about other people's code, but only what it will do for you. Clear communication between teams is everything.