Ephemeral architecture

Architecture diagrams

Self-hosted Ephemeral instance

The following diagram shows how data and requests flow within a self-hosted instance of Tonic Ephemeral. Ephemeral can be deployed on AWS, Azure, or Google Cloud Platform (GCP):

Architecture diagram for a self-hosted Ephemeral instance

Ephemeral Cloud

The following diagram shows how data and requests flow within Ephemeral Cloud. Ephemeral Cloud specifically uses Amazon EBS for storage.

Architecture diagram for Ephemeral Cloud

Components

Application database

The Ephemeral application database is a PostgreSQL database that stores the Ephemeral database, snapshot, and application configuration, including:

• Ephemeral users

• Registry location

• Disk space alert threshold

• Database configuration, including:

  • Name and description

  • Database type

  • Required resources

  • Expiration configuration

  • Associated auto snapshots

  • Activity history

• User snapshots list

Container registry

The container registry stores any data volumes that you use to create databases.

Ephemeral web server

The Ephemeral web server runs the Ephemeral user interface, and processes requests and calls from the Ephemeral API.

Disk storage for databases

Ephemeral databases are stored in either:

• For AWS, in Amazon EBS

• For Azure, in Azure Disk Storage

• For GCP, in Persistent Disk

Components for database connections

Database connections to databases go through DNS.