Q1: What is the principle of dividing services?

Criteria for judging good service

• Maintain high cohesion within the service itself (with its own domain model)
• Encapsulation internal changes, through the API external exposure function (only the service itself code can access the database of the domain model, other systems can only indirectly access the service data through the API exposed by the service)
• Be loosely coupled with other services, able to modify and deploy independently (other systems that rely on the service do not have to be modified and deployed at the same time)
• Be able to implement service governance and change independently

There can be multiple publishing units on top of the same domain model (context), but only one is the service

• One is the service
• One is a timed task.
• A management background

Q1: What is the principle of dividing services?