Create a Backstage software template that scaffolds a service with CI, Helm and docs.
Developers want a "golden path" that gives them a working service with best practices built in.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
SaaS: New service in an hour, not a month. Creating a new microservice took weeks of tickets for repositories, pipelines and environments. An internal developer platform with Backstage templates creates the repository, pipeline and Kubernetes namespace in one step. Teams launch new services in under an hour, all following the same standards.
Banking: Guardrails instead of gatekeepers. Security reviews blocked every release. Policies as code (Kyverno, OPA) and pre-approved Terraform modules are built into the platform. Most releases go out without manual review, and violations are blocked automatically.
E-commerce: Clear ownership and costs. Nobody knew which team owned which service or how much it cost. A service catalogue with owners, docs and cost labels per namespace. Every service has an owner and teams see their own cloud costs.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 14 hours of hands-on work, and it fits best after week 7 of the Platform Engineering with Kubernetes & Terraform course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.