Anyone who has ever set up a domain with microservices already knows: APIs for service-to-service communication are of crucial importance. Since each team has its own style and implements interfaces differently, the number of various approaches tends to explode sooner or later. Defining a guideline with rules and examples right at the beginning of the project helps to guarantee consistent APIs which are as self-explanatory as possible.
Microservices lead to new challenges, making it necessary to find new technological approaches. Microservice frameworks are of course part of the solution, but they are certainly not the most important. Which technologies play a crucial role here?
In this interview, Kai Tödter emphasise that teams have to think carefully how microservices should interact with each other, like using orchestration or choreography. The services themselves should be self-contained or use resilience patterns when they need data of other microservices.
In this interview, Gil Tayar explains that building a microservices architecture from scratch is different, and easier, than taking an existing architecture and turning it into microservices.
Production hates you. The machines, the networks, the very users you hope to provide a service hate you. This is reality, and it makes production a hostile battle ground. In this interview, Russ Miles will talk about the reasons and how to turn this pain to your advantages.