4 ms·
> Deployment includes setting up and upgrading and potentially backing up Postgres. But I find this rather trivial to do with cloud database services like RDS.
by hn_throwaway_99 8y ago
> Deployment includes setting up and upgrading and potentially backing up Postgres.
But I find this rather trivial to do with cloud database services like RDS. Why not just use that? At the end of the day it gives you tons of benefits (e.g. easy backups) with no real lock-in because you'd still just be using a normal postgres driver.
- kodablah 8y ago> Why not just use that? No particular reason, depends on the use case. Every choice has tradeoffs, and there are cloud-specific ones that can hinder mobility even if it uses a common tech. Lock in is about more than code reuse especially as dependence grows. Granted, for many use cases it might be the best option, but we shouldn't pretend like it's the exact same mobility profile as copying a DB file.
- qznc 8y agoWhat about local development? With sqlite I can clone my repo, execute something like "make run" and my server runs.
- hn_throwaway_99 8y agoIt's quite simple to do the exact same thing with postgres, you just configure a separate connection string for prod vs local deployments.