Do you mostly write DTO classes, property bags with data from database or from APIs? Do you name every class in the service layer managers, processors, or services? Are you disappointed that you can't do DDD as your day to day job is to build simple CRUDy APIs? Then, come and join my talk to discuss how we can domain driven design our API development. You will be surprised that you can benefit from DDD with even the simplest CRUD APIs by putting all validation and business logic in central domain models, not scattering them around.
YOU MAY ALSO LIKE:
- Value objects will lead you to the world of DDD (SkillsCast recorded in May 2016)
- Sociotechnical Domain-Driven Design with Kacper Gunia (Online Course on 18th - 19th February 2021)
- Android Architecture with Jorge Ortiz-Fuentes (Online Course on 22nd - 24th February 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- DDDx — Domain-Driven Design eXchange 2021 (Online Conference on 8th - 9th June 2021)
- Evolutionary Architecture (SkillsCast recorded in January 2021)
- What an Architect Can Learn from Retrospective Failures (SkillsCast recorded in December 2020)
Solving 5 typical Issues in API development with Domain Driven Design
Andrew Young H. Chaa is an experienced Backend-focused full-stack developer with a background of working on large scale, high volume distributed services. He currently works as a lead developer at Clear Bank.