-
Book Overview & Buying
-
Table Of Contents
Machine Learning in Microservices
By :
In Chapter 2, we had to copy some schemas across multiple microservices and use saga patterns through the orchestrator to keep data consistent and preserve the microservice’s autonomy. This solution may be viable in a situation if you have a limited number of microservices within the MSA system. In a large number of microservices systems, copying schemas across different microservices to maintain the synchronization of the individual microservices database doesn’t scale well and can severely impact the system’s overall performance.
Consider an MSA system with 100 microservices and copy schemas across about 20 of those microservices to maintain the microservice’s autonomy. Each time any part of any of the schema’s data is updated, the orchestrator will have to sync those 20 schemas.
Moreover, even if we have all 100 microservices perfectly autonomous, what if one of the user’s operations needs to gather information...
Change the font size
Change margin width
Change background colour