Managed database or self-managed: a total cost comparison

Running a database yourself looks cheaper on the invoice. Counting updates, backups and the expertise to run them usually reverses the answer.

2 min readMade-up stories, not client work

Cost Optimization: story 14 of 15

A made-up story

Picture a growing software company paying for a managed database. Someone notices that running the same database on a plain server would cost less each month.

What's going wrong

The comparison only counts the server. It leaves out the updates, backups, standby copies and the expert time it takes to run a database well.

What they have today

  • A managed database the product depends on
  • No database specialist on the team
  • A steady, predictable workload

What we can't ignore

  • Customer data can't be lost
  • Downtime hurts customers
  • Engineers are busy with the product

The choices

  • Worth a look

    Run the database on a plain server

    A lower invoice, but the team becomes responsible for everything.

  • Our pick

    Keep the managed database, sized correctly

    Pay for what's used, and let the provider handle the hard parts.

  • Worth a look

    Run it yourself with an outside support contract

    Possible, but the contract can cost more than the savings.

What we'd do

Keep the managed database. Check its size against real use, pick the right storage type, keep backups for as long as the business needs and no longer, and consider a discount for steady use. Revisit if the team gains database experts or the database grows very large.

Why

  • The hard parts stay with specialists
  • Right-sizing captures most of the savings
  • Engineers stay on the product

Where the money really goes

No prices here: this shows where the costs sit, not what they'd be for any real business.

The plain server wins on the invoice. Counting updates, backups, standby copies and expert time, the managed database usually costs less in total.

Invoice
Self-run: lower. Managed: higher, but includes the upkeep.
Expert time
Self-run: someone must know databases well.
Risk
A failed backup or long outage can cost far more than the difference.

Running, growing, and staying safe

If something breaks

The managed service handles failover and backups, and restores can be tested on demand.

When it grows

Resizing is a setting, not a project.

Keeping it safe

Updates are applied by the provider, and encryption is built in.

What the business gets

  • A lower bill without new risk
  • Fewer late nights for engineers
  • A clear rule for when to revisit

These are the kinds of results the approach aims for, not measured results.

When we'd look again

If the company hires database specialists, or the database gets big enough that the managed premium is large, we'd price running it ourselves again.

If you liked this, read

About these stories. These stories are made up to show how we think. They are not client projects, describe no real business, and contain no measured results.

Next: When Kubernetes costs more than it saves

A small team adopted a complex container platform for a handful of apps, and now spends much of its time running the platform. A simpler managed service can lower the total cost even if the bill barely changes.

Read the next story