In the last two years, platform engineering has emerged as a distinct discipline from DevOps and SRE. The core idea: instead of every team building and operating its own infrastructure, a dedicated team offers an internal platform (IDP — Internal Developer Platform) as a product. The goal is for product teams to deliver value quickly without becoming experts in Kubernetes, Terraform, or the CI system.
The Problem It Solves
Past a certain scale (20+ services, 50+ developers), the “each team manages its own stack” pattern becomes expensive:
- Duplication. Each team independently solves deployment, observability, secrets, auth.
- Cognitive friction. A backend developer spends 30-40% of time on infrastructure tasks outside their specialty.
- Operational inconsistency. Similar problems solved in different ways complicate incidents and audits.
- Reduced mobility. Moving an engineer between teams requires relearning their toolchain.
IDPs address this by consolidating the common behind a unified interface, without limiting flexibility where it matters.
What Composes an IDP
A mature IDP typically includes:
- Developer portal: unified UI to see, create, and manage services. Spotify’s Backstage is the open-source reference.
- Service catalog: inventory with metadata (responsible team, dependencies, SLOs, docs). It’s the IDP’s “database”.
- Golden paths: pre-built paths for common cases (create a new microservice, deploy to staging, set up observability). More than tutorials — templates that reduce creation to a single command.
- Self-service: product teams can provision resources without manual tickets to the platform team.
- Observability by default: every new service starts with metrics, logs, and traces.
- Guardrails, not gates: policies that allow progress but warn or prevent known mistakes.
Backstage as Reference
Backstage, open-sourced by Spotify in 2020, is the most visible ecosystem component. Functions:
- Software catalog: YAML describes services, their ownership, docs, and relations. One entry per entity (service, library, website, infrastructure).
- Plugins: ~100+ plugin ecosystem (CI/CD status, Kubernetes, monitoring, docs) living in the same portal.
- TechDocs: documentation-as-code, rendered inside the portal.
- Scaffolder: new-component generator from templates (create a Spring Boot service with observability and CI in one click).
In 2023, Backstage is the base of dozens of internal IDPs at large companies, though it requires substantial investment to adapt to one’s own context.
Golden Paths: The Core Value
A golden path answers: “I want to create a new microservice — what’s the recommended way here?”. The answer should be a template generating:
- Repository with standard structure.
- Configured Dockerfile and CI.
- Kubernetes manifests with resource limits and health checks.
- Pre-created Grafana dashboard.
- Basic error-rate alert on SLO.
- Integration with the company’s auth system.
The key: the golden path isn’t mandatory. Teams can deviate when they need to. But the “happy path” is clear and so subsidised that most follow it by default.
When to Invest in Platform Engineering
Not every team needs an IDP. Signs it’s time:
- More than 30-50 developers working on interconnected services.
- Visible duplication between teams in configuration, deployment, observability.
- Incidents whose root cause is “each team does it differently”.
- Slow onboarding — more than 2 weeks for a new engineer to deploy something useful.
For smaller teams, IDP investment is usually premature. Better to start with good practices and shared scripts, formalising a platform when scale justifies.
Antipatterns to Avoid
Three errors seen repeatedly:
- Platform team = “renamed DevOps team”. If you only do infrastructure without treating the developer as customer, you haven’t done platform engineering.
- IDP as gate, not path. Forcing the product team through the IDP blocks innovation. Offering it as a clearly better option is different.
- Build everything custom. Backstage + plugins + some integrations is enough for most. Reinventing the wheel rarely justifies the cost.
Also see how to apply SRE without being Google — platform engineering complements SRE: SRE operates what platform builds.
Conclusion
Platform engineering in 2023 is a mature discipline for organisations of a certain scale. A well-designed IDP frees product-team time, consolidates practices, and reduces operational incidents. But only if treated as a real product with real users (internal engineers), not as yet another infrastructure project.
Follow us on jacar.es for more on platform engineering, SRE, and development productivity.
