Continuous Delivery

  • objective is to get around the OODA loop (Observe – Orient - Decide – Act) faster
  • teams should be organised around microservices with a separate platform team exposing an API that all other teams use
  • DevOps should be a reorganization of teams, contrary to the tendency that companies are organized in teams, product managers, developers, QA, etc., and getting something done requires a lot of meetings, a kind of waterfall approach that takes too long.
  • end-to-end process of developing and releasing software is often long and cumbersome, it involves many people, departments and obstacles
  • white paper continuous-delivery-maturity-model 1, 2014

maturity model

Deployment Strategies

Canary Release 2: route a small percentage of traffic to the new version before full rollout
Blue-Green Deployment 3: maintain two identical environments; blue is the easily switchable hot-standby
Evolutionary Database Design 4

Engineering Fundamentals Playbook on Continuous Delivery 5
App Service auto swap 6
Deployment rings 7
Kubernetes rolling update 8

Travis CI

Travis CI C# language support 9
.travis.yml example (FLACLibSharp) 10

< «