CNP: Cloud‑Native Platform

CNP is an internal cloud platform built by a team of six in the SIGL major at EPITA. I owned the layer that turns what a team asks for into real infrastructure: the data model, the API and the interface teams use, kept simple enough that nobody needs to know the cloud resources underneath to ask for something.

In most companies, an application team that needs a new database files a request and waits for a platform team to set it up by hand, or learns enough cloud configuration to do it themselves. Either way it's slow, and the result is hard to keep track of once it exists. With CNP, a team creates a project, describes the infrastructure it needs, and the platform provisions it on the cloud. Each team only ever sees and changes its own resources.

My part

The change I'd point to first is how a project describes its infrastructure. It used to be a list of resources, and a list can't tell you when one is no longer used, so forgotten ones keep costing money. I proposed describing it as a graph of what depends on what, so the platform could find what nothing uses anymore. The interface for it exists; the part that walks the graph isn't built yet.

Safe, reviewable changes

Every resource has its own history of changes, so each one can be reviewed, deployed or rolled back without touching the others. I worked on this part with the rest of the team.