If you're running a postgres instance, is it a bad...
# orm-help
o
If you're running a postgres instance, is it a bad idea to have multiple databases on the same instances for different environments (prod/staging)?
Or should you have completely separate instances? The downsides I guess are bugs in staging could cause prod outages? And then permissions for prod and staging get mixed up.
The attraction to me is the cost saving, since I'm paying alot for a managed instance
But perhaps no worth it, for all the side effects – why can you have multiple databases per an instance then, what's the use case?
r
Hey @ojschwa 👋 You can use the same instance and keep two separate databases for staging and production if you want to save costs. If you're going to implement it this way, then you can add separate users for staging and production so that one cannot access the other. So it should be fine in that way. The only downside is that when the instance is down, staging and production both go down so it's better to have at least 2 instances so that one can act as a backup if the primary fails.
👍 2