By the end
What you'll build
- Describe the planes of an internal developer platform and trace a request through them
- Design an application and environment model that supports promotion without duplication
- Design a provisioning flow that handles asynchronous work, partial failure and quotas
- Choose between command line, API, portal and pipeline interfaces for a given capability and justify the choice
- Select a tenancy and isolation model and state the blast radius it accepts
- Plan and measure the rollout of a breaking platform change across many teams
Curriculum
What's inside
7 modules · 35 lessons
- 01
Anatomy of an internal developer platform
5 lessons- The planes of a platform and how a request flows through them
- Abstractions that help compared with abstractions that hide
- Assembling capabilities rather than building everything
- Deciding what belongs in the platform at all
- Which plane owns it?match pairs
- 02
Application and environment modelling
5 lessons- Designing an application model that survives real services
- Workloads, resources and dependencies
- Environment topologies and promotion paths
- Naming, ownership and metadata that stays accurate
- Naming what you deployfill blank
- 03
Provisioning and orchestration
5 lessons- From a developer request to provisioned infrastructure
- Declarative requests and reconciliation
- Long-running and asynchronous provisioning
- Quotas, limits and guard rails
- Provisioning a slow resourcesequence order
- 04
Interfaces to the platform
5 lessons- Choosing between a command line, an API, a portal and a pipeline
- Designing a platform API that is hard to misuse
- Templates, scaffolds and repository bootstrapping
- Local development parity with platform-provisioned environments
- One capability, four front doorsscenario
- 05
Multi-tenancy and isolation
5 lessons- Tenancy models and the blast radius each one accepts
- Namespace, account and network boundaries
- Noisy neighbours and fair sharing
- Attributing cost by tenant
- What each boundary really buys youmatch pairs
- 06
Evolving the platform safely
5 lessons- Rolling out a breaking platform change across many teams
- Progressive delivery of platform capabilities
- Backwards compatibility windows and support commitments
- Measuring migration completion rather than migration effort
- Changing a platform forty teams depend onfill blank
- 07
Practice and check
5 lessons- Name the platform conceptmatch pairs
- Retiring a field forty teams usesequence order
- Platform decisions in one line eachfill blank
- Closing a permissive defaultscenario
- Course quizquiz
The shape of it
How this course works
Short lessons
35 lessons across 7 modules, each small enough to finish in one sitting.
Practice as you go
Every lesson ends with a small space for what you noticed — the doing is the learning.
Progress you can see
Your progress is saved lesson by lesson, ready whenever you come back.
Ready when you are.
Make an account and this course opens up — your progress is saved from the very first lesson.