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.
