Every team has concerns about using domain-driven design (DDD). What kind of benefits does it offer? Why is it better than everything they used before? What if we want to use microservices architecture right now or we plan to migrate to microservices architecture any time soon? How Domain Driven Design can help to find answers on all of these questions? Does DDD have anything available out of the box that helps us to deal with microservices and components in our architecture? What about bounded contexts and aggregates and some other options available in DDD? And finally if we are well prepared right now and use all of the best practices from DDD, how can I migrate to microservices architecture when it is needed? What kind of anti-pattern all teams can face in their journey to Domain Driven Design?
As one of the key drivers of this process, an architect must be able to answer to any questions coming from developers, business analysts, and even Scrum Masters. Architects must be ready and well prepared for any type of questions.
Anuar Nurmakanov helps you find the best answer to all these questions. Anuar shares his team’s journey with DDD from the very beginning of a project and outlines the many problems they faced. He then details some anti-patterns to be afraid of and how to deal with them, DDD best practices, and how DDD and microservices ideas can leave together.
Anuar Nurmakanov is a software craftsmanship practitioner with more than nine years of experience in mobile, web, enterprise development, architecture, Scrum, and XP approaches and who likes public speaking and knowledge sharing.
For exhibition and sponsorship opportunities, email SAconf@oreilly.com
For information on trade opportunities with O'Reilly conferences, email firstname.lastname@example.org
View a complete list of O'Reilly Software Architecture contacts
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com