Please log in to watch this conference skillscast.
The domain model of an application describes the organization and partitioning of the business logic and rules. The business can look at that model and recognize itself. This is a good thing; but it's only part of the problem. An application is a system that connects the business domain model, the technical domain, and the specific use cases of a particular application. These three aspects of an application are often at odds with each other because they have opposing needs and affordances. It is the job of the System Architecture to balance those forces allowing these competing application aspects to work in harmony. Getting this right is critical to the lifecycle of the application and is an essential element in creating well-crafted applications.
YOU MAY ALSO LIKE:
- Clean Architecture: Drawing Lines (SkillsCast recorded in October 2017)
- Domain Models in Practice with Marco Heimeshoff (Online Course on 8th - 12th March 2021)
- Microservices Architecture with Jorge Ortiz‑Fuentes (Online Course on 19th - 21st April 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- Rust from a Frontend Perspective (SkillsCast recorded in February 2021)
- Meeting Our First Production Need with Rust (SkillsCast recorded in February 2021)
Systems and Domains. Triplet Sons of Different Mothers
Robert Martin (@unclebobmartin) is Master Craftsman at 8th Light, Skills Matter instructor and author of a range of books (as well as hundreds of articles), including: Clean Code: A Handbook of Agile Software Craftsmanship as well as his most recent, Clean Architecture: A Craftsman's Guide to Software Structure and Design.