31
CHAPTER 3 | Architecting container and microservice-based applications
As Figure 4-8 shows, the catalog business microservice could be composed of several services or
processes. These could be multiple ASP.NET Web API services or any other kind of services using
HTTP or any other protocol. More importantly, the services could share the same data, as
long as
these services are cohesive with respect to the same business domain.
Figure 4-8. Business microservice with several physical services
The services in the example share the same data model because the Web API service targets the same
data as the Search service. So, in the physical implementation of the business microservice, you’re
splitting that functionality so you can scale each of those internal services up or down as needed.
Maybe the Web API service usually needs more instances
than the Search service, or vice versa.
In short, the logical architecture of microservices doesn’t always have to coincide with the physical
deployment architecture. In this guide, whenever we mention a microservice,
we mean a business or
logical microservice that could map to one or more (physical) services. In most cases, this will be a
single service, but it might be more.
Challenges and solutions for distributed data
management
Dostları ilə paylaş: