Microservices are designed and intended to operate as independently as possible. Still, they need to talk to each other once in a while. In this chapter, you will learn what good communication between microservices looks like and what you should avoid. Microservices sometimes have to communicate with each other; for example, when it comes to validating or aggregating information. Imagine that one microservice needs to get data from another one to then visualize it. The first microservice could, of course, access the database directly, but this might threaten the integrity of the second microservice. This is also dangerous because of the database's structure changes, or even the database itself, which means that the first microservice won't be able to operate anymore. So, for the first database to retrieve reliable information...
United States
United Kingdom
India
Germany
France
Canada
Russia
Spain
Brazil
Australia
Argentina
Austria
Belgium
Bulgaria
Chile
Colombia
Cyprus
Czechia
Denmark
Ecuador
Egypt
Estonia
Finland
Greece
Hungary
Indonesia
Ireland
Italy
Japan
Latvia
Lithuania
Luxembourg
Malaysia
Malta
Mexico
Netherlands
New Zealand
Norway
Philippines
Poland
Portugal
Romania
Singapore
Slovakia
Slovenia
South Africa
South Korea
Sweden
Switzerland
Taiwan
Thailand
Turkey
Ukraine