look like?  It has little technical debt.  It is built according to good, extensible design patterns and uses well-accepted standards.  It is loosely coupled—pieces of it can be easily exchanged good monitoring tools in place.  It is coded in a way that resists hard-to-find defects like concurrency errors. Build Versus Buy Everyone knows that in every case under the sun, in any example one custom development is falling: More and more logic is abstracted away by frameworks and design patterns. Incremental delivery and staged investments reduce cost and risk.  Custom code is almost not

functionality by small configuration changes. Feature flags, dark launching h. ENVIRONMENT-BASED RELEASE PATTERNS i. Enables deployments during normal business hours ii. Blue-Green Deployment 1. Strategy a Remove application assumptions about DB version iii. The Canary & Cluster Immune System Release Patterns 1. Canary Strategy a. Automates the release process of promoting to larger and more critical roll back when metrics deviations, outside of expected ranges, are detected i. APPLICATION-BASED PATTERNS TO ENABLE SAFER RELEASES i. Implement Feature Toggles 1. Selectively enable/disable features without

negative results, ideally feature toggle off and fix-forward or use other Blue- Green, Canary release patterns b. DEV SHARES PAGER ROTATION DUTIES WITH OPS i. Complex systems will inevitably have unexpected