Team Topologies and adoption of Platform Engineering - Lessons Learned from Cloud Modernization and Path Forward
Our Cloud Modernization journey started 6 years ago with Private cloud using PCF which is a Platform as a Service and in the last 2 years, our team started the Public Cloud journey where we migrated all our microservices and web applications to AWS, Lambda, Kubernetes.
Both business and the team were prepared for the substantial cloud migration work and effort it would take to migrate to AWS in the first year and business deliverables were reduced so that the team could concentrate on the migration. But gradually, we realized that moving to Public Cloud entailed a lot of ongoing work in the subsequent years as well, and not just in the first year.
We realized that we had team members with different strengths and interests and not all of them could adapt to the ever increasing demands of maintaining our infrastructure.
We decided to restructure our team and formed a platform team with team members who expressed interest in performing a Platform role and this team is responsible for maintaining and upgrading the infrastructure and working with the central platform team.
By having a dedicated platform team, our goal is to reduce the cognitive load of other developers who can then concentrate on their value streams.