Doing more with internal developer portals
summary
Claims concrete wins: reduces lead time from weeks to days by automating cloud enablement with a 30‑second event‑driven workflow; practical stacks shown: ReactJS + ASP NET + Azure Functions and integration with Backstage, Keycloak, GitHub and MCP agents; measured outcomes cited — 97% report lost developer time and DX can boost productivity ~50%; demos include a weekend‑built portal with entity ingestion, badges, onboarding automation and a partly flaky login during the live demo.
AI-written summary · about
chapters (13)
- 0:00Internal developer portals intro
- 2:56Need an internal portal?
- 7:07Roll out a developer portal
- 9:28Domain model for portal
- 11:27Teams for portal success
- 13:21Features with measurable outcomes
- 15:43Scaling with inner sourcing
- 17:59Adoption with metrics and change
- 20:41Reference architectures for portals
- 27:00Custom vs product-based portals
- 31:15Demo: Real portal in action
- 32:50Build portal in weekend with AI
- 38:24Key actions and closing
related talks
37mTransforming DevEx with Internal Developer Portals
06mPlatform Engineering with a Product Management Mindset: 10x Your De...
38mEmbracing Developer Portals in Software Development
25mThe Developer Portal: Open the Gate to Productivity 🚀
15mDeveloper portal
24mElevating Developer Efficiency with Developer Portal
24mFrom 165 Days To 30 Minutes: Breaking Enterprise Silos With…
27mWhy your API portal is so bad and what you can do about it