What actually transfers from 14 years on a cloud control plane

Tenant provisioning APIs, identity, notifications, and audit on Oracle Public Cloud taught a particular kind of discipline: contracts, blast radius, and the difference between a platform and an application.

Some of that maps cleanly onto today’s Spring Boot / Kubernetes / Terraform work. Some of it — SOAP-era coupling, shared databases, heavyweight middleware — is exactly what we now spend programs unwinding.

If you hire principal engineers from long vendor tenures, what evidence do you look for that someone can leave the old platform behind? If you are that engineer, what did you have to unlearn? The comment thread is open.