Project / Branch / Database best practices
Hey there π
I've been using neon's serverless pg for a while now for a rather narrow use-case: terraform state backend. Currently I'm looking if it can be of help for other more typical use-cases as a db for a small nodejs api.
Whilst reading through the docs I found it a bit hard to have a clear picture for my api setup with one production and one staging/test environment.
Shall each environment be its own project/branch/database?
If someone could point me to an article or a doc, I'd really appreciate it π
1 Reply
genetic-orangeβ’2y ago
@deteam assuming it's just one service/API, generally a branch per environment instead of separate projects is fine.
If you're running different APIs/services that have their own databases, then different projects might be beneficial as explained here: https://discord.com/channels/1176467419317940276/1213055527261831220