A PaaS for Government
summary
Team prototypes a PaaS for UK government, evaluates Deis, Cloud Foundry and Suru prototype and uses Suru to stand up an initial platform; Suru runs about 400 apps in ~800 containers upstream. User research yields concrete specs: self‑service deployments, granular multi‑tenancy required (team admins, per‑team isolation, resource contention handling) and an ops model where application teams support their own apps. Surprisingly, users reject running across multiple public clouds — no multi‑cloud demand — so vendor‑lock concerns require different procurement solutions.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:39The Government Digital Service
- 1:50And the most common problem is hosting
- 6:19Multi-tenancy Granularity of user permissions Handling resource contention Isolation from other tenants
- 7:29What we've done
- 10:10Meanwhile building same functionality in Cloud Foundry to compare
- 11:23Lowest common denominator
- 11:36Google Compute Engine doesn't have internal load balancers
- 12:00Can't take advantage of cool features of all the providers
- 13:13For example, virtualisation vs hardware
related talks
04mBuilding an open platform for government innovation
15mPaaS isn’t enough: your internal platform in Multi Cloud
18mSunrise of Platforms as Services (PaaS)
13mThe Future of the Government Platform
20mKeynote: Delivering Simpler, Clearer, Faster Government Services
25mMaking the Leap: Transitioning Enterprises to a PaaS Mindset
30mEnabling Public Cloud For Clients in a Public Sector
40mSupercharge App Development with