The next level pipelines delivering Net Zero
summary
Res restructures a decade-old monolith into small flow-aligned teams and a platform (Uno) providing multi-tenant auth and clear API boundaries, which speeds feature delivery and lowers cognitive load. Edge boxes run Docker with Azure Edge and iot and C# to push continuous deployments to remote turbines. Initial pipeline uses a DAG runner (Bagster) and queues, then simplifies to a shared core analytics API so analytics are easy to call; the changes improve release velocity and operability.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:08Climate change urgency explained
- 3:34Speaker introductions
- 4:16About RES and Uno platform
- 5:20Net Zero challenges in renewables
- 7:06Team restructuring for growth
- 9:56From monolith to team topologies
- 13:45Reflections on team changes
- 14:47Flow-aligned team structure
- 16:29Data pipeline from turbines
- 19:15Continuous delivery in remote systems
- 20:58Improving analytics with feedback
- 23:48Simplifying microservices architecture
- 25:55Key takeaways and conclusion
related talks
34mBeyond Continuous Delivery
16mBuilding ans scaling Angular apps on Azure
28mWhat's Next in Platform Engineering
47mModern continous delivery on Azure Kubernetes Service
46mAdaptive cloud approach: Build and scale apps from cloud to edge
46mReal World DevOps
25mCloud for Frontend
49mThe road to continuous deployment: a case study
