When to use it
Use MySQL for structured business data in a SaaS product, dashboard, CMS or internal tool. Flash Deploy runs the application while MySQL stores its primary data across app releases.
Connection details
Connection provides host, port, username, password and database/schema. Metrics show query, storage, bandwidth, timeout and connection usage. Terminal and Dashboard help inspect the service from Console.
Products in the same DLEZ organization communicate through private endpoints, including products in different projects. Use the destination service's private host and port. Your laptop and browser are external clients even when you are signed in to Console; use a public endpoint for external access. Keep credentials on the server and follow the service's TLS requirements.
Operating the database
Use the service's current plan and metrics to understand capacity. Test schema changes before production and confirm backup/restore procedures. Persistent storage alone does not replace a backup.
Step by step
- Open Database > MySQL, choose a recognizable name and review a plan's storage, query, connection limits and cost.
- Create the database and wait until ready. Resolve balance or creation errors before retrying to avoid duplicate resources.
- Use the private endpoint for an app in the same org. Copy host, port, user, password and schema into server-side env; never into frontend code.
- Install the app's driver/ORM and run SELECT 1. If it fails, check Connection, the endpoint and TLS requirements.
- Run migrations through your app's tooling, then write and read a test record. Redeploy the app and verify the record remains.
- Monitor queries, storage and connections. Confirm backup/restore before storing customer data; do not delete the database to redeploy the app.