7 Building a reusable microservice framework
This chapter covers
- Building a microservice chassis
- Advantages of enforcing uniform practices across teams
- Abstracting common concerns in a reusable framework
Once an organization fully embraces microservices and teams grow in number, it’s quite likely that each of those teams will start specializing in a given set of programming languages and tools. Sometimes, even when using the same programming language, different teams will choose a different combination of tools to achieve the same purpose. Although nothing is wrong with this, it may lead to an increased challenge for engineers moving between different teams. The ritual to set up new services, as well as the code structure, may be quite different. Even if teams eventually end up solving the same challenges in different ways, we believe this potential duplication is better than having to add a synchronization layer.