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):
Ephemeral Cloud
The following diagram shows how data and requests flow within Ephemeral Cloud. On Ephemeral Cloud, all connections to Ephemeral databases go through an SSH Bastion.
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
A self-hosted instance can enable either direct connections to databases through DNS, or connections through an SSH Bastion.
On Ephemeral Cloud, all database connections must go through an SSH Bastion.
Last updated
