Domain-Driven Design (DDD) is one of the best thing to happen to software development in decades. It has within it the key to our hardest software architecture problems: how to slice up our software, how to write maintainable software, how to name things … and most importantly of all, how to meet the needs of […]
The Heart of Domain-Driven Design (DDD) Read More »
The first thing that I liked about this book on documenting software architectures is that the authors know how to write. It is both easy to read and well-structured. The book provides a reading guide for the different categories of readers (architect, novice and stakeholders). There are also many pointers and quotes in the margins
Documenting Software Architectures Read More »
Here are some of the common mistakes when moving to microservices that are discussed in this presentation, with provided solutions for:* No realistic architecture process (architecture decisions too rigid, or not taken; infra vs domain; architecture guild vs no cooperation, knowledge sharing ); * QA thinks testing end-to-end is possible; Management wants to control deployment;
Common Mistakes When Moving to Microservices Read More »
Expanding on Eric Evans’ original book, Domain-Driven Design (DDD), Vaughn Vernon presents in his book “Implementing Domain-Driven Design” common sense DDD procedures through models from recognizable areas. Each principle is backed up by realistic Java examples-all applicable to C# developers and all content is supported by a single case study: the delivery of a large-scale
Implementing Domain-Driven Design Read More »
How much architectural work needs to be done before you actually start coding? Should you know what software architecture is and how to use it even if you don’t have the “software architect” title? And finally, how can you use diagrams to shape your software architecture?
Why Architectural Work Comes Before Coding Read More »