Building a Start-Up to Compete with Ourselves
summary
Pearson spins up an internal start-up (founded August 2015, funding April/May) and ships a production app last week running a fully containerized Kubernetes platform on public cloud, aimed at 2,000 apps and 400 dev teams. Platform uses mostly open source, exposes an API and docs, and relies on a three-file bite-size manifest for portable deployments. Governance and maturity remain blockers, so orchestration uses StackStorm-driven self-healing workflows and git-based test payloads to get security, QA and ops into the delivery pipeline.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:58Chris Jacksons background
- 1:55History of Pearson
- 3:32Organizational Context
- 4:56Shadow IT
- 7:44Bite Size
- 8:43Our Story
- 10:12Key Problems
- 10:28How to fix DevOps
- 12:33What is our product
- 14:05Governance
- 15:38Cloud
- 16:42Open Source
- 17:31Portability
- 19:01Serverless
- 20:09Technology Operations
- 21:18Community Engagement
- 23:14Operations
- 24:32Metadata
- 25:57Learning
related talks
41mITNW (If This Now What) - Orchestrating an Enterprise
25mBreaking the 2 Pizza Paradox with Platform Applications
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
40mLessons Learned Building Developer Platforms
44mIs Platform Engineering a hype? Let's build a platform together!
33mBuilding Shopify's PaaS on Kubernetes
26mTwo sides of the platform coin with operator's and customer's voices
42mPlatform Engineering in practice — Why and How to start