The DevOps HandbookARCHITECTURE THAT ENABLES PRODUCTIVITY, TESTABILITY, AND SAFETY i. Loosely-coupled ii. Well-defined interfaces that enforce how modules connect with each other c. ARCHITECTURAL ARCHETYPES: MONOLITHS VS. MICROSERVICES Coined by Martin Fowler in 2004 ii. Strangler Application 1. Put existing functionality behind an API 2. New functionality implemented in new services with new architecture 3. Make calls to old system0 码力 | 8 页 | 23.08 KB | 5 月前3
MITRE Defense Agile Acquisition Guide - Mar 2014externally? Does the plan align to existing enterprise architectures, frameworks, standards, or interfaces? Can the development team access architecture documents and systems? Are owners/representatives user stories to cover underlying characteristics of security, technical performance, or quality. Interfaces with other systems are usually captured as user stories. User stories require little maintenance; content and priority. For example, the team may add integration items to the backlog as the program interfaces with other systems. Systems engineers and enterprise architects may add items that support the0 码力 | 74 页 | 3.57 MB | 5 月前3
The DevOps Handbookshared infrastructure – shared databases iv. Bounded context – compartmentalized and well-defined interfaces k. KEEP TEAM SIZES SMALL (THE “2-PIZZA TEAM” RULE) 10. Ch. 8 How to Get Great Outcomes by Integrating0 码力 | 8 页 | 22.57 KB | 5 月前3
The DevOps Handbookthat could become an error and will likely trigger an alert 4. Error – error conditions such as API failures, internal issues 5. Fatal – forces a termination iv. Examples of potentially significant Use telemetry to measure outcomes iv. Etsy open-sourced their experimentation framework – Feature API e. INTEGRATE A/B TESTING INTO OUR FEATURE PLANNING i. Product owners should consider each feature0 码力 | 8 页 | 24.02 KB | 5 月前3
The DevOps Handbooksuite becomes the living documentation of the system specification and represent working examples of API use e. DESIGN FOR OPERATIONS THROUGH CODIFIED NON-FUNCTIONAL REQUIREMENTS i. Designing for fast changes through pair programming or code review 3. Instrument the repository to detect suspicious code (API calls from certain types of test code) 4. Ensure every CI process is in an isolated container 50 码力 | 9 页 | 25.13 KB | 5 月前3
共 5 条
- 1













