the question is about building an application that is easier to split into microservices later. it all comes down to this - http://www.infoq.com/news/2015/01/m

the question is about building an application that is easier to split into microservices later. it all comes down to this - http://www.infoq.com/news/2015/01/microservices-sharing-code http://www.infoq.com/news/2015/01/microservices-sharing-code If you have multiple components that are depending on the same code, if you try to split them into multiple services that are being independently deployed, you need to keep the code they are depending on in sync. So making a change to the code shared by multiple services, means you have to deploy multiple services for a single change. I completely agree with you about the protobuf/thrift angle though. If you're in that situation, you are already doing it right.