The event-driven pattern

The microservice architecture has the database per service pattern, which means it has an independent database for every dependent or independent service:

  • Dependent service: Our application would require a few external services (third- party services or components, and so on) and/or internal services (these are our own services) to work or function as expected. For instance, CHECKOUT-SERVICE requires CUSTOMER-SERVICE; also, CHECKOUT-SERVICE requires an external (third-party) service to verify a customer's identity (such as Aadhaar card ID in the case of Indian customers). Here, our CHECKOUT-SERVICE is a dependent service, as it requires two services (an internal service and external service) to function as expected. ...

Get Building Microservices with .NET Core 2.0 - Second Edition 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.