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)
- Jenny Martin's BDD From Start to Finish - Successful Delivery through Continuous Collaboration (in London on 4th - 6th November 2019)
- Fast Track to RESTful Microservices (in London on 11th - 13th November 2019)
- F# eXchange 2020 (in London on 2nd - 3rd April 2020)
- µCon London 2020 - The Conference on Microservices, DDD & Software Architecture (in London on 27th - 29th May 2020)
- 2 Presentations: Kubernetes Ingress & DevOps and Microservices Better Together (in London on 17th October 2019)
- Clean Architecture using BLoC & Voyager: DI & the Widget Router (in London on 21st October 2019)
- Lightning Talk: The Elm Architecture in Haskell: Managing state with multiple threads (SkillsCast recorded in October 2019)
- Pragmatic Memory Management (SkillsCast recorded in October 2019)
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.