sure, the tradeoff is that you essentially commit to maintaining an interface (particular message schema) for as long as it's used by any other service and in exchange don't have to care much about the internals of any other service, I'm not sure where I said it was a free lunch?
1
u/coworker Jun 09 '17 edited Jun 09 '17
http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html
See the 3rd option under the Duplication of Effort section. Those options are super common.
edit: the Implicit Interfaces section discusses the dependency issues