What are the main principles to follow when developing system architecture using Domain-Driven Design?

When developing system architecture using Domain-Driven Design (DDD), it is important to follow these principles:

• Focus on the domain: the main attention is given to understanding and modeling business logic and rules.
• Ubiquitous Language: developers and domain experts use a common language that reflects the terminology of the subject area.
• Bounded Contexts: the system is divided into separate areas with clear boundaries, within which concepts and models are unambiguous.
• Modeling through entities, aggregates, and services: key objects and their behaviors are highlighted, as well as operations that do not belong to specific objects.
• Infrastructure isolation: business logic is separated from technical details (databases, UI, integrations).
• Integration through contracts and events: interaction between contexts occurs through well-defined interfaces and events.

Example: in an order management system, you can identify the "Orders" context, which has an aggregate "Order" with methods for changing status, and the "Payments" context, which processes payments by interacting through events.