Building Evolutionary Architectures: Support Constant Change"O'Reilly Media, Inc.", 18 de set. de 2017 - 190 páginas The software development ecosystem is constantly changing, providing a constant stream of new tools, frameworks, techniques, and paradigms. Over the past few years, incremental developments in core engineering practices for software development have created the foundations for rethinking how architecture changes over time, along with ways to protect important architectural characteristics as it evolves. This practical guide ties those parts together with a new way to think about architecture and time. |
Conteúdo
Chapter 1 Software Architecture | 1 |
Chapter 2 Fitness Functions | 15 |
Chapter 3 Engineering Incremental Change | 25 |
Chapter 4 Architectural Coupling | 47 |
Chapter 5 Evolutionary Data | 83 |
Chapter 6 Building Evolvable Architectures | 95 |
Chapter 7 Evolutionary Architecture Pitfalls and Antipatterns | 123 |
Chapter 8 Putting Evolutionary Architecture into Practice | 141 |
| 167 | |
About the Authors | 175 |
Colophon | 176 |
Outras edições - Ver todos
Building Evolutionary Architectures: Support Constant Change Neal Ford,Rebecca Parsons,Patrick Kua Visualização parcial - 2017 |
Termos e frases comuns
ability abstractions affected allows application approach appropriate architects aspects automation become behavior better bounded break build called Chapter characteristics companies complex component concerns consider context Continuous continuous integration coordination coupling create Customer cycle database DBAs decisions defined Delivery dependency deploy deployment pipeline developers difficult dimensions discussed domain easier ecosystem engineering practices enterprise environment event evolution evolutionary architecture evolve example existing factors Figure fitness functions framework goal handle impact implement important incremental change infrastructure integration isolation layers mechanism microservices architecture migration monolith Once operations organizations pattern PenultimateWidgets performance plug-ins points possible practices problem production quantum requirements scalability schemas shared shown in Figure solution stage structure technical architecture testing things tion transactional typically understand unit updates users