/Glossary · DevOps
What is Platform engineering?
Platform engineering is the discipline of designing and running a self-service internal platform so development teams can build, deploy and operate software without filing tickets. The platform is treated as a product with internal users.
How an internal platform works
An internal developer platform packages recurring decisions into golden paths: service templates, standard pipelines, Terraform modules, and observability and security preconfigured. A developer picks a template, fills in a few parameters and gets a production-ready service with best practices built in.
On AWS, the foundation is usually a multi-account landing zone, EKS clusters or ECS services, GitHub Actions pipelines with OIDC, versioned Terraform modules and a portal such as Backstage. The platform exposes capabilities, not loose resources: a web service, a queue or a database with its controls attached.
When to invest in platform engineering
It makes sense when several product teams keep repeating the same infrastructure work, when the DevOps team spends its days closing tickets, or when every service has a different pipeline. With two or three teams that friction usually shows up, and the lack of standards starts costing time.
If you have a single development team and just a couple of services, solid DevOps practices and shared modules are probably enough. A platform makes sense when the cost of coordination exceeds the cost of building it and maintaining it as a product.
Best practices and common mistakes
Treat the platform as a product: interview developers, prioritize by real friction and measure adoption, time to first deployment and satisfaction. Start with a golden path for your most common service type and expand from there, always with documentation and examples.
The classic mistake is building a massive platform nobody asked for, with abstractions that hide too much and block legitimate use cases. Another is making it mandatory without making it better than the alternative. A good platform gets adopted on its own because it saves work.
/FAQ
Questions about Platform engineering
Another question? Write to hello@nubent.com and an engineer will answer.
What is the difference between DevOps and platform engineering?
DevOps is the culture and the set of practices. Platform engineering is one way to scale those practices: one team builds self-service tooling so every other team can apply DevOps without becoming infrastructure experts.
What is a golden path?
It is a recommended, supported way to handle a common task, such as creating a microservice or an API. It comes with a template, pipeline, observability and security ready to go. It isn't mandatory, but it is the fastest and safest option for the team.
Do you need Backstage to have an internal platform?
No. Backstage is a useful portal for a service catalog and templates, but a platform can start with a repository of Terraform modules, reusable pipelines and good documentation. The portal adds value once there are several teams and services to catalog.
How we help with Platform engineering
Platform Engineering
An internal developer platform on AWS with golden paths, Backstage and Terraform self-service, for autonomous teams that ship quickly and safely.
Learn moreKubernetes on Amazon EKS
Amazon EKS clusters with Karpenter, Helm and Argo CD, pod-level security and zero-downtime upgrades, run through Terraform and GitOps.
Learn moreDevOps as a Service
An ongoing external DevOps team for your AWS infrastructure: Terraform, CI/CD, security, costs and on-call coverage, on a monthly subscription.
Learn moreNext step
What should we build next on AWS?
30 minutes with an engineer. Concrete next steps, whether or not you work with us.