If Government can do it...
summary
GOV.UK is built and run by small multidisciplinary teams that scale from 14 to 140 and the organisation reaches ~250 people, replaces hundreds of sites in one day by redirecting ~300,000 URLs, and averages about six code releases per working day (88 updates in eight days after launch). Automation uses one-click deployment via Jenkins, configuration managed with Puppet/Chef/Ansible and infrastructure as code, source in Git/GitHub, tests on TravisCI, public analytics, and many small disposable services; deployments roll forward, not back.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:40Tools for citizens
- 4:01Tools for internal users
- 8:55An example project
- 32:11Higher level abstractions
- 33:43Smoke tests and monitoring
- 33:53Change who responds to issue
- 36:29App showing deploys
- 40:01Publishing tools
- 40:18Developer environment
- 40:57Published content
- 41:33Testing in the open
- 42:24Performance data
related talks
27mWhen DevOps Meets Security
20mKeynote: Delivering Simpler, Clearer, Faster Government Services
15mOne Million Builds per Year, Only One Page - Operating Internal Services...
29mA history of GOV.UK's infrastructure: the long voyage to Kubernetes
01h 00mReliability and speed by 'push to main' mentality
30mHow Go Helped Accelerate Software Delivery at the BBC
52mThe Future of Continuous Delivery
46m10+ Deploys Pe