Container databases vs Managed database services

Overview

You can create both container databases in your Docker environment, or managed database services, in MedStack. Each of which have their pros and cons. Please take a moment to review this article to help make an informed decision when deciding which method you'll choose to implement.

Container databases Managed database service
Types supported
Any containerized database
(e.g. postgres, mysql, mariadb, mongo, redis)

See database services on Docker Hub.
PostgreSQL
MySQL
Connectivity Docker service accessible using the host name (service name).
Cloud resource accessible using connection strings.
Compliance Yes – all Docker services ran on MedStack are configured for
operational privacy compliance.
Yes – all cloud resources provisioned via MedStack are configured
for operational privacy compliance.
Auto-scaling CPU/Memory: No – limited to the node on which the service is pinned.
Capacity: No – limited to disk size on node.

Contact support@medstack.co if more compute resources or capacity is required.
CPU/Memory: No – limited to the server size when creating the service.
Capacity: Yes – default configuration.

Contact support@medstack.co if more compute resources or capacity is required.
Backups Hourly, Daily, Weekly, Monthly

Retains monthly snapshots indefinitely.
Daily

Retains daily full backups for 35 days.
Transaction logs available in 5 minute intervals to bridge latest full backup and real-time.
Restoration Not database specific by default, see the backup/restore process
in MedStack Control.

Please contact support@medstack.co for database specific restorations.
Database specific, contact support@medstack.co.
Price Free, may depend on licensing. Hourly, set by cloud provider.

See Azure's managed database pricing for PostgreSQL and MySQL.
Recommendations Make use of:
  • Labels on nodes
  • Volume mapping for the Swarm
  • Volume mapping for the service
  • Configuring only one (1) replica of the service
  • Placement constraints for the service pinning it to a node

See more on our example of setting up a MongoDB service.

Make use of:
  • Secrets or Configs to handle the connection string
  • Replicas for General Purpose type services (allows for hot-swapping databases)
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Submit a request for support Submit a request for support