Refactoring the microservices

What we will start now is a giant change in our application. In the first chapters, we say that microservices do not have a long life, which can and should be modified whenever a business requirement arises. It is precisely this kind of moment that we have reached now.

Due to a business need, we will apply a new pattern that will have a direct impact on our stack and microservices. It is important to understand that the News microservices do not have external communication, they are Internal Services, and good practice is not to use HTTP in the communication between internal microservices.

Our News microservices were built on the Flask framework and had an API that spoke directly to the client. Now, this will ...

Get Microservice Patterns and Best Practices now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.