The document discusses the role and purpose of platform engineering in managing complex systems, emphasizing the need for self-service capabilities and improved developer experience. It outlines the organization of platform teams, the lifecycle of service management, and challenges related to project management and technology adoption. Key takeaways include a focus on feedback loops, effective communication, and the necessity for alignment within teams.

1. Platform Engineering
BATbern54
08/11/2025
Michele Monforte / Fabian Nicollier
1

2. Introduction
Self-service
Use case (Support process)
Landing Zones / Modules
Accelerators
Q/A
Michele
Michele
Michele
Fabian
Fabian
10’
5’
5’
5’
5’

3. 3
Purpose of Platform engineering
3
The future of Ops is platform engineering | PlatformCon 2023
Systems are becoming rapidly more complex
They can only really be operated by the people who
write them
And you can’t do a good job of writing them unless
you are regularly exposed to the feedback loops of
operating them
Is the Platform Engineering team responsible for
SLOs, service uptime, and a reliable customer
experience ?
Is Time to spin up new service or db or
other developer workflow 1st priority ?
NO
YES
Improve Developer Experience by providing :
- All information possible to improve code.
- All information to make better technical choices.
- Reduce time to bootstrap technologies.
- Implement DevOps – Developer ownership

4. 4
Platform as a product
Support
Platform team
• Product Manager
• Security expert
• Azure/AWS Experts
• Platform DevOps
• Architects
Impl.
Project team
• Project Manager
• Lead Dev
• Developers
• DevOps
• Architect
use
feedback
Platform backlog
Platform
Self Service
(prov.+ access)
Billing
Indicators
Practices – Sec Checks
Accelerators
Monitoring / Alerting
Support / Invoicing
Guide – Template -
Self training - example
Dev Portal
Dev Environ.
Architecture
Security
Production
Architecture Architecture
Dev Environ. Dev Environ.
Security Security
Production
Production
Software Factory

5. 5
Asset Lifecycle
Example
1. Order an Azure Subscription
2. Create/Renew a Service Principal
3. Check your Azure consumption
4. Archive your Account
1.Creation 2.Configure
3.Use
4.Archive

6. 6
Self-Service
Self-Service : Integration with ERP, Entity location, Project Organisation mapping

7. 7
Cost Allocation and Consumption

8. 8
Communication – Dashboard

9. 9
Use Case – Support Process
Project team is the solution owner

10. 10
Landing Zone Building Blocks

11. 11
Project lands on Platform

12. 12
Golden Sample – A demonstrator for usage

13. 13
Golden Sample – A real running app

14. 14
Landing Zone Modules as Software Templates

15. 15
It works !
4059

16. 16
• Status
• 95% transition from VM to container for on-prem’s
• 90% of project CI/CD adoption
• Project SonarQube adoption with KPI reporting up to the management
• Challenges
• Impossible to cover all needs -> 80% / 20% rule -> product management
• Need skills, Platform Eng. team do everything (Build + Run + Support)
• Highly transversal , need alignment on goals, terminology, communication
• Testing is hard, nothing is similar to prod (WireMock is a friend)
Key Takeaways

17. 17
Thank you
Q&A