Our great sponsors
-
Running a database container per service that needs it, would probably be the best option. More secure, easier backups, migration, updates, etc (especially if you use something like Docker Compose ). Of course different services may also require different MariaDB versions, another advantage. As others have mentioned, if your services don't do much, the database containers will idle and not consume a lot of resources. One case where you might want to use the same database container is if you have multiple services that work often (like web data scrapers, RSS feed aggregators, Usenet-related services).
-
I was using MariaDB exclusively, but one of the software I use, Ghost, had compatibility issues with MariaDB and they announced that they would only support MySQL from now on... So I migrated some databases to MySQL, but I didn't migrate them all because I find MySQL to be resource intensive. 😕
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Related posts
- Hosting a simple docker-compose app with Nginx and generate a SSL with certbot on digitalocean droplet
- One Minute: Compose
- How to Set Up a Docker Container
- Use same Dockerfile for Dev & Production
- How to Dockerise a NodeJS - TypeScript API || A Comprehensive Guide from Environment Setup to Deployment with a CI/CD Pipeline