Vaughn Vernon couples guided approaches to implementation with modern architectures, highlighting the importance and value of focusing on the business domain while balancing technical considerations.Building on Eric Evans seminal book, Domain-Driven Design, the author presents practical DDD techniques through examples from familiar domains.Each principle is backed up by realistic Java examplesall applicable to C developersand all content is tied together by a single case study: the delivery of a large-scale Scrum-based SaaS system for a multitenant environment.
![]() ![]() The author takes you far beyond DDD-lite approaches that embrace DDD solely as a technical toolset, and shows you how to fully leverage DDDs strategic design patterns using Bounded Context, Context Maps, and the Ubiquitous Language. ![]() Coverage includes - Getting started the right way with DDD, so you can rapidly gain value from it - Using DDD within diverse architectures, including Hexagonal, SOA, REST, CQRS, Event-Driven, and FabricGrid-Based - Appropriately designing and applying Entitiesand learning when to use Value Objects instead - Mastering DDDs powerful new Domain Events technique - Designing Repositories for ORM, NoSQL, and other databases My Link. For one, the primary goal is to use the most prevalent style with regards to the target reader. The covered concepts are described in theory and illustrated with standalone examples and a sample application. Table of Contents This book is 95 complete Last updated on 2020-08-23 29.99 Minimum price 34.99 Suggested price Packages Details Book Code Book Code - 5 copies (20 discount) Book Code - 10 copies (30 discount) You pay (US) EU customers: Price excludes VAT. Add Ebook to Cart Add to Wish List About the Book Note: The book is 95 complete. While there is no fixed release date, the first version of the book should be 100 complete mid-September 2020. Abstract This book explains and illustrates how to implement Domain-Driven Design, Command Query Responsibility Segregation and Event Sourcing in Node.js. Implementing Domain Driven Design Software That IsThe reader is taught to build software that is problem centered, well designed, event-based, reactive and scalable. Domain-Driven Design (DDD) is a methodology that focuses on the actual problem to solve and its involved knowledge areas. Command Query Responsibility Segregation (CQRS) promotes to separate a software into a write side and a read side. Implementing Domain Driven Design Series Of ImmutableEvent Sourcing is an architectural pattern where state is represented as a series of immutable events. All concepts are described in theory and put into practice with standalone examples and a fully functional sample application. Implementing Domain Driven Design Code Is WrittenThe code is written in JavaScript and uses Node.js as runtime. This book includes a source code bundle with all standalone examples and the sample application implementation. Target audience The target reader is experienced with Node.js and wants to implement DDD, CQRS and Event Sourcing without deep-diving into theory. The second potential reader has theoretical knowledge about the mentioned concepts, but struggles with translating them into actual code. For such a person, it might be required to build up the respective JavaScript and Node.js knowledge. Apart from the first four chapters, which cover the more conceptual parts, this book heavily focuses on code and implementation. Also, some of the covered topics are not explained to their full extent, but rather as far as needed. As a consequence, the book is not recommended to be used as a reference. Chapter order and structure The chapter order in this book is determined by what makes most sense in terms of building the sample application. As a consequence, the topics are laid out in a way so they can build upon each other. This also reduces the likelihood of referring to terms before they are explained. Then, they are described in detail and illustrated either with drawings or code examples. At the end of each chapter, the discussed concepts are applied to the sample application. This is done by describing the working steps to take and by showing the according drawings or code. An exception is chapter 5, where there is no sample application section. Programming paradigms The content and the code examples in this book compromise an overall combination of imperative, declarative, object-oriented and functional programming. However, most parts apply the object-oriented paradigm and therefore partially contradict with a functional approach.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |