Index
A
- A/B testing, Culture of Experimentation
- abstraction distraction antipattern, Build Anticorruption Layers
- abstractions, leaky, Pitfall: Leaky Abstractions-Pitfall: Leaky Abstractions
- accidental (unintentional) coupling, Microservices, Antipattern: Inappropriate Governance, Antipattern: Reporting
- Ackoff, Russel, Fitness Functions
- adaptation, evolution vs., Why Evolutionary?, Adaptation versus evolution
- Amazon
- scaling problems, Scale
- two-pizza teams, Product over Project
- Amazon Cloud, Combining Fitness Function Categories
- Ambler, Scott, Evolutionary Data
- anticorruption layers, “Serverless” Architectures, Build Anticorruption Layers
- antipatterns, Evolutionary Architecture Pitfalls and Antipatterns-Pitfall: Planning Horizons
- abstraction distraction, Build Anticorruption Layers
- Big Ball of Mud, Big Ball of Mud, Can’t evolve a ball of mud
- coupling (see inappropriate coupling)
- inappropriate governance, Antipattern: Inappropriate Governance
- incremental change, Incremental Change-Antipattern: Inappropriate Governance
- reporting, Antipattern: Reporting
- Vendor King, “Serverless” Architectures, Antipattern: Vendor King
- application programming interfaces (APIs), How Is Long-term Planning Possible When Everything Changes All the Time?
- application services, ESB-driven SOA
- appropriate coupling
- in Big Ball of Mud, Big Ball of Mud
- in broker EDAs, Brokers
- in COTS software, COTS Implications
- in ESB-driven SOA, ESB-driven SOA
- in layered monolithic architecture, Layered architecture
- in mediator EDAs, Mediators
- in microkernels ...
Get Building Evolutionary Architectures now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.