#Where data leaves the project

Application Services is where a project's data is exposed to the outside world: as APIs that other systems call, and as apps that people open in a browser. The two share one lifecycle, one resource model and one identity layer, so they present as a single service.

That lifecycle is build, then deploy. Editing an API or an app changes its source, and nothing reaches production until an artifact is built, which is a container image prepared automatically for that component, and then deployed, which runs a container from that image.

Figure 1: building an artifact on Data Platform

Deployment is blue/green. Two identical production environments exist, only one is live at a time, and the live one serves all traffic. Switching between them keeps downtime and rollback risk low.

Figure 2: diagram of a blue/green deployment

Once a component is deployed, nodes can be added or removed, each node an instance of the artifact. That is how an API or an app scales horizontally.

Every app is linked to a deployed API, and every API can serve any query saved in the Analytics Manager under IAM authentication, so data leaves the platform through one authenticated path rather than through direct database access.

#Go further

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.

Ask questions, give your feedback and interact directly with the team building the Data Platform on the dedicated Discord channel.

If you need support with your OVHcloud services, create a request in our Help Centre.

Join our community of users.