It even gives you a flow chart to use as a starting point on choosing which pattern to use in different areas of your system.
AMAZON DOMAIN DRIVEN DESIGN HOW TO
when to use the patterns, when to avoid them, when and how to change your mind about your decision later as the business evolves which I think has been a real sticking point for many engineers and architects that have considered DDD in the past. It provides real-life, usable heuristics, i.e. It also really brings a lot of ideas together from the the most popular sources out there like Eric Evans, Martin Fowler, Chris Richardson, Greg Young, and many more, so this is coming from a very inspired place and will not giving that feeling like you're being preached at. actually including the business, in true DDD fashion. It really realigns the design thought process with the business while. I just got the kindle version of the book and I have to say, I absolutely loved it! By far the best I’ve read on the topic overall, and not a dry read like just about every other book on the topic. the influence of DDD on data, and the obvious value/ importance of Data Mesh, now that you are designing with context in mind. how Event Storming can speed up discovery, and design how patterns and approaches (such as Domain event publishing) have evolved over time field-tested heuristics and decision trees to speed-up decision making The inclusion of decision trees and design heuristics that account for the evolution of a system, and outline how the various patterns apply/ evolve, is incredibly useful - all with emphasis on using the right patterns for the right reasons, and not over complicating your solution.Ĭompared to the blue and red books, this is a much easier introduction to many of the core concepts and patterns from DDD (as your knowledge/ understanding grows you'll still want those books, but this book is a fantastic onramp to the depths of detail the blue and red books contain).įor those that have practiced DDD for some time, this book represents an up-to-date "pocket reference" (by DDD book standards!), reflecting: gives you "just enough" to make the right decisions, at the right time, without bombarding you with tons of detailed code, that depending on your implementation, may or may not be useful. explains key patterns and approaches in a human readable and (importantly) relatable format easy to digest, Vladik takes you on a journey that shows you the 'why' not just the 'how' Gradually introduce DDD to brownfield projectsĪ well structured, practical and experienced-based introduction to Domain Driven Design, with something for new comers and even 'seasoned' DDD practitioners.įor newcomers to DDD this *is* the book you've been looking for:.Decompose a system into bounded contexts.Build a shared understanding of the business domains you encounter.
AMAZON DOMAIN DRIVEN DESIGN SOFTWARE
Use DDD's strategic and tactical tools to architect effective software solutions that address business needs.Analyze a company's business domain to learn how the system you're building fits its competitive strategy.You'll also explore the real-life story of implementing DDD in a startup company. You'll examine the relationship between domain-driven design (DDD) and other methodologies to ensure you make architectural decisions that meet business requirements. This practical book provides you with a set of core patterns, principles, and practices for analyzing business domains, understanding business strategy, and, most importantly, aligning software design with its business needs.Īuthor Vlad Khononov shows you how these practices lead to robust implementation of business logic and help to future-proof software design and architecture. As a developer, you not only have to chase ever-changing technological trends but also need to understand the business domains behind the software.
0 kommentar(er)
