Skip to content
14 providers 54 configurations
Independent reseller · not affiliated with any provider Telegram

Infrastructure

Managed or self-hosted databases

The question is not which is cheaper. It is who is on call when replication breaks.

Managed or self-hosted databases

A managed database costs more per unit of compute than the same engine on a virtual machine. That comparison is incomplete, because it prices the server and ignores the operational responsibility.

What managed actually removes

  • Automated backups with tested point-in-time recovery.
  • Minor version patching on a schedule you choose.
  • Replication and failover configured and monitored.
  • Baseline metrics without assembling an exporter stack.
  • Storage growth handled without a maintenance window.

Each is achievable yourself. The question is whether your team wants to own them, and whether they will still be owned well in eighteen months when the person who set them up has moved on.

When self-hosting is the right call

Reasons to run it yourself
Reason Notes
Unsupported engine or extension The managed catalogue does not include it.
Deep configuration control You need parameters the service does not expose.
Cost at scale Large, steady workloads where the premium is material.
Existing operational expertise The team already runs databases competently.
Co-location requirement The database must sit on the same host as something else.

If you self-host, do these five things

  1. Automate backups off the instance, and restore one on a schedule to prove it works.
  2. Monitor replication lag, disk space and connection counts with alerts.
  3. Document and rehearse the failover procedure.
  4. Patch on a schedule, not on discovery of a vulnerability.
  5. Keep configuration in code so the instance can be rebuilt.

A pragmatic default

For most teams below a dedicated platform function, start managed. The premium buys back attention that is better spent on the product, and migrating to self-hosted later is a known, bounded exercise. Reverse migrations – from a struggling self-hosted database to a managed one during an incident – are considerably less pleasant.

Summary

Compare total responsibility rather than instance price. Self-host when you have a specific reason and the operational capacity; otherwise let the platform hold the pager and spend the time elsewhere.

Keep reading

More Cloud Insights

Next step

Find the account this article describes

Compare configurations by provider, with prices and full detail on every page.

Scroll to Top
Telegram