"Just Enough Software Architecture book, by author George Fairbanks, focuses on a risk-driven approach to software architecture development.
RelatedVendorContent
Got fires in production? Find root cause in minutes. FREE Java performance tool
The Agile Business Analyst
Experience Java EE! 600 page Redbook
Testing Platforms Analyst Comparison: IBM, Microsoft, Coverity, MKS, and more
Transform IT Complexity to Achieve IT System Vitality
George explains the Architecture Modeling process from different perspectives such as Engineering Use Models, Conceptual Model, Domain Model, Design Model and the Code Model. He also discusses the various architecture styles including Big ball of mud, Pipe-and-filter, Batch-sequential, Map-Reduce and talks about the distinction between architectural patterns and architectural styles. The discussion also includes topics like evolutionary design, architecture refactoring and how to analyze, test and validate the architecture models."
"Domain Driven Design (DDD) is an approach of how to model the core logic of an application. The term itself was coined by Eric Evans in his book "Domain Driven Design". The basic idea is that the design of your software should directly reflect the Domain and the Domain-Logic of the (business-) problem you want to solve with your application. That helps understanding the problem as well as the implementation and increases maintainability of the software."
" Performance is a topic of increasing importance in the software industry. Today performance engineers and architects as well as operations people have to ensure that complex application landscapes works seemlessly and problems are resolved fast and with minimal effort. "
"I'm passionate about Domain Driven Design (DDD). Like many experienced object modellers, I was practicing this long before Eric Evans coined that specific term, though I have sinced learned some useful specific patterns from his book. To me, DDD is about two things: focussing on the business functionality rather than on the technical implementation; and focussing on building a good model of the business domain rather than just on the specific immediate requirements. Like many others, I perceived that the key to this was to model the domain as behaviourally-complete domain objects: to actively resist the tendency to separate business functionality from the persistent domain entities."
"Patterns-Based Engineering: Successfully Delivering Solutions via Patterns book, by Lee Ackerman and Celso Gonzalez, focuses on how to improve efforts in identifying, producing, managing and consuming patterns - leading to better software delivered more quickly with fewer resources."
"As a book and methodology, DDD is an excellent way to approach complex software problems, and make them far more understandable and manageable. As a buzzword, DDD is in danger of being corrupted like many other good software practices."
" This guide is focused on building highly scalable, highly available, and maintainable applications with the Command & Query Responsibility Segregation and the Event Sourcing architectural patterns. It presents a learning journey, not definitive guidance. It describes the experiences of a development team with no prior CQRS proficiency in building, deploying (to Windows Azure), and maintaining a sample real-world, complex, enterprise system to showcase various CQRS and ES concepts, challenges, and techniques. The development team did not work in isolation; we actively sought input from industry experts and from a wide group of advisors to ensure that the guidance is both detailed and practical. "