Platform engineering maturity - Your key to competitive differentiation
summary
Aeon claims platform engineering cuts developer cognitive load by standardizing with reusable Terraform modules, a Confluence + GitHub wiki, internal workshops, and a push toward an IDP GUI, and runs core state and secrets on HCP Terraform and HCP Vault. Results show team count up ~6x, product count up ~5x, 10 million downloads, and critical incidents down to one quarter. Roadmap keeps evolving team structure and adds specialized template and platform teams.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:26Eon Group overview and philosophy
- 3:14Digital transformation challenges
- 5:06Journey to platform engineering maturity
- 7:41Step 1: Team building and reliability
- 11:02Step 2: Wiki and inventory
- 13:55Step 3: Standardization and reusability
- 16:05Step 4: Self-service and IDP
- 17:29Team design evolution
- 23:18Business outcomes and results
- 24:19HashiCorp products integration
- 27:45Conclusion and Q&A
related talks
29mIaC Next Steps in Platform Engineering
25mPlatform Engineering: Evolution or a Fancy Rename?
42mPlatform Engineering in practice — Why and How to start
41mPlatform Engineering for Developers, Architects & the Rest of Us
15mThe Art of Platform Engineering
33mPlatform engineering: Build your own PaaS
45mPlatform Engineering: A Deep Dive Conversation
26mCompliance-Aware Platform Engineering