Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
31 results for “Platform Teams”
Data Mesh
An organisational approach that gives domain teams ownership of their analytical data as a product, with a self-serve platform and federated governance.
Paved Road
A supported, opinionated default way to build and run a service, made easy enough that teams choose it rather than being required to.
Booking.com's Experimentation Platform
Booking.com runs over a thousand concurrent experiments and treats the ability to test any change safely as a platform capability rather than a product feature.
Chargeback and Showback
Attributing cloud cost to the teams that generate it — either informationally (showback) or by moving it onto their budget (chargeback).
Cognitive Load
The total amount a team must hold in its head to work effectively, and a real constraint on how many services or domains one team can own.
FinOps
The practice of giving engineering teams visibility into and accountability for the cost of what they build and run.
Health Check
An endpoint the platform polls to decide whether an instance should be restarted or should receive traffic — two different questions needing two different checks.
Kubernetes
A container orchestrator that continuously reconciles the running state of a cluster towards a declared desired state.
Microservices
An architectural style where an application is a set of independently deployable services, each owning its data and aligned to a business capability.
Monzo's Microservice Estate
Monzo runs a bank on well over a thousand microservices, and the interesting engineering is in the platform and network isolation that makes that number survivable.
Product Thinking
Treating what you build as something with users, a value proposition and a lifecycle, rather than as a project that completes.
Replatform
Migrating an application largely as-is while making targeted changes to exploit the target platform — usually the best return per unit of effort.
Service Mesh
An infrastructure layer of sidecar proxies that handles service-to-service networking — mTLS, retries, timeouts, routing, telemetry — outside the application.
Two-Pizza Team
Amazon's heuristic that a team should be small enough to be fed by two pizzas, and — the substantive part — should own its service end to end.
Workload Identity
Giving a running workload a cryptographically verifiable identity issued by the platform, so it obtains short-lived credentials without a stored secret.
eBay's Architectural Generations
eBay rewrote its core platform several times across its first decade, each time because the previous generation had hit a limit that could not be tuned away.
A design review presents a new event-driven platform. What cost questions do you ask before approving it?
What the interviewer is testing Whether cost is part of your architecture review or an afterthought handled by finance later, and whether you know the specific
A document collaboration product needs sharing with individuals, teams, and inherited folder permissions. Which authorization model?
The requirement is relationship shaped The questions this product must answer are: is this user a member of a team that has access to a folder that contains thi
An organisation is starting cloud adoption. Three teams want to deploy next month. What must exist first, and what can wait?
What must exist before anything reaches production Account structure. Separation by environment and by workload, because an account is the strongest isolation b
You are asked to choose between a cloud data warehouse and a lakehouse for a new analytics platform. How do you decide?
What actually differs The gap has narrowed considerably, so the decision turns on fewer things than the marketing suggests. Format ownership. In a lakehouse, da
You are designing APIs for a platform with a web app, a mobile app, internal service-to-service traffic and third-party partners. What do you expose, and where?
What the interviewer is testing Whether you choose per constraint or adopt one technology as an identity. The wrong answers here are all defensible sounding and
Platform Teams
Reducing other teams' cognitive load, measured by adoption.
Team Topologies
Stream-aligned, platform, enabling and complicated-subsystem teams.
ML Platform
Feature stores, training pipelines, registries and deployment.
Platform as a Product
Adoption earned rather than mandated, with an owner and a roadmap.
Architecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.
Centralised vs Distributed
Shared platform leverage against team autonomy.
Operating Models
How delivery, platform and governance functions fit together.
Showback & Chargeback
Making teams see, or own, the cost of what they run.
Subnetting
Tiering, zone binding, and sizing for an address-hungry platform.
Technology Standards
Guidance that teams follow because it helps, not because it is mandated.