Goal
Choose between MySQL and MariaDB, connect over TLS and know how restores work.Prerequisites
- A StackShift account
- A MySQL or MariaDB driver in your app
Workflow
1
Create a database and choose MySQL 8.4 or MariaDB 12.3.
2
Copy the connection details from the database page and connect with TLS turned on.
3
Point your app at the database through its project binding so the connection variables are set for you.
Versions
- MySQL 8.4 is the long-term support release and the default for new MySQL databases.
- MariaDB 12.3 is a long-term support release.
- Pick the engine your app or framework was built for. They share most SQL, but replication and some functions differ.
Restores
Backups run automatically. A restore always creates a new database and leaves the original unchanged. On Starter databases you restore to one of the recorded restore points; restoring to an exact second is not available for MySQL or MariaDB on Starter.Existing MySQL databases
Databases created before this release move to StackShift’s own MySQL 8.4 image in an announced window, and we email you on the day. For 1 to 5 minutes the database accepts reads but not writes. Your version, connection string and password stay the same, and every table is checked before the switch. We keep the previous copy read-only for 7 days.Expected result
Your app connects over TLS and reads and writes data.
Common failures
Related guides
Create a database
Create a hosted or connected-node database with private, direct public, or StackShift tunnel access.
Database connections and tunneling
Use private, direct public, or StackShift tunnel endpoints with TLS and explicit client IP policy.
Back up and restore a database
Use durable recovery storage correctly and understand why backups are independent from portable SQL transfers.