MultiConnectCloud › Database Deployments
1. What you get
| Part | What it is |
|---|---|
| Engine | MySQL 8.0 or 8.4, or PostgreSQL 16 or 17 |
| Two copies | A primary that takes your writes, and a second copy on a different machine that is kept in step with it |
| Writer endpoint | A hostname and port for everything that changes data |
| Reader endpoint | A second hostname and port that only accepts reads |
| Backups | Taken on a schedule you choose, plus whenever you ask |
| Cache add-on | Optional. A separate Redis on a third address |
Your application never connects to a machine directly. It connects to the writer or reader endpoint, and that endpoint is passed through to whichever copy is serving it. The hostnames and ports belong to the deployment for its whole life, so they do not change when the database moves to another machine or fails over.
Every connection is encrypted with TLS. To prove the server is really yours, your client checks it against a certificate file you download once (Section 6).
These endpoints are for your own backend. Never put them, or the password, in a game client, mobile app or anything else a user can read.

