Exploring the platform landscape
The team at Syntasso has many years' experience building and running platforms across different organisations. Through this work we have observed four common platform patterns that each offer benefits but also come with drawbacks. We see these platform patterns as part of a journey: an intermediate step between where you are now and where you want to be in the future.
Below we explore the pains of each platform pattern and suggest a feasible next step that platform engineers can take to improve. Our hope is to learn more about how teams are delivering platforms today, and provide guidance on how they can take steps on the journey towards a better platform. This is not a comprehensive list, and your platform may have more than one pattern. If you can’t find your platform challenges described here (or if you'd like to give us feedback), let us know using the form below or by scheduling some time to chat. We’d love to hear from you!
What kind of platform do you have?
Tickets, tickets, tickets
Ticket driven workflow. App teams submit tickets to the platform team who then manually respond and fulfil the request.
Self-service workflow. App teams have access to cloud accounts and are responsible for the creation and operation of services.
App teams need to be cloud experts
Duplication of resources across teams
Not bespoke to organisations
Platform team offers the Kubernetes API as the platform. App teams use Kubernetes to deploy and manage the software they need.
App teams run their own platforms
Duplication of work across teams
Increased cognitive load
Platform teams provide curated scripts and templates that app teams use to spin up desired resources.
App teams must learn low-level infrastructure
This content was created by the team at Syntasso as a way to learn and share what we are learning about how platform engineering teams operate today. See our website to learn more.