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 10th - 14th May 2021)
- Android Architecture with Jorge Ortiz-Fuentes (Online Course on 17th - 19th May 2021)
- DDDx — Domain-Driven Design eXchange 2021 (Online Conference on 8th - 9th June 2021)
- Software Architecture Gathering Digital 2021 (Online Conference on 13th - 14th October 2021)
- LDN *Virtual* Talks Apr 2021 *Red Badger Takeover* (Online Meetup on 27th April 2021)
- Living with Your Legacy (SkillsCast recorded in April 2021)
- Real-world API Modularization with DDD and Hypermedia (SkillsCast recorded in April 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.