Was the status model common to the entire system or only within a certain number of services?

The status model typically depends on the scale and architecture of the system. In small or monolithic applications, the status model can be common across the entire system, providing a unified state for objects.

In distributed systems and microservices architecture, the status model is often limited to individual services to avoid excessive coupling and simplify state management. In such cases, each service manages its own statuses, and consistency is achieved through events or APIs.

For example, in an e-commerce system, the order service may have its own statuses (created, paid, shipped), while the delivery service has its own (waiting, in transit, delivered).