3 ms·
Right, but using Lightsail as an example to keep things simple, you're picking between scaling at 3x the cost of the server vs db service or a set $5 per databa
by gexla 5y ago
Right, but using Lightsail as an example to keep things simple, you're picking between scaling at 3x the cost of the server vs db service or a set $5 per database.
I would still trust the AWS service with something mission critical though. Hippobase might be good for stuff which isn't mission critical but otherwise wouldn't have anything the service offers because you don't want to throw the resources at.
- igorzij 5y agoThe use case we had in mind initially was that teams often set up their production using Heroku db or RDS (naturally, because it's easy and reliable), and then when they need more environments they naturally do the same. But reliability often isn't that critical for dev environments. You lose your DB, so what? Just make a new one. Then we realised that we could actually near production-grade reliability by doing backups, snapshots etc. So the choice is up to the user