Components

Once the bounded contexts are identified for microservices and the organization structure is aligned, each microservice must be considered as a product that is tested, deployed, and scaled in isolation by the same team that developed it. A well-designed microservice must never expose its internal data model to the outside world directly. Instead, it must maintain a service contract that maps to its internal model such that it can evolve over time without affecting the dependent microservices.

Component-based software engineering (https://en.wikipedia.org/wiki/Component-based_software_engineering) defines a component as a reusable module that is based on the principles of SoC and encapsulates a set of related functions and data. In the context of microservices architecture, it is recommended to implement each service as a component that is independently swappable and deployable without affecting any other microservices.