3 ms·
https://neon.tech/docs/introduction/branching https://neon.tech/docs/introduction/branching is exactly what the author is looking for and is the best way to do
by devaiops9001 3y ago
https://neon.tech/docs/introduction/branching https://neon.tech/docs/introduction/branching is exactly what the author is looking for and is the best way to do highly efficient point-in-time versioning of Postgres data I have seen so far.
I deployed NeonDB in a large enterprise client in Q2 of this year and, yes, the initial data migration is the hard part. We added 2x100gbe network cards directly on the VMware hosts where the data was so the migration to the Kubernetes cluster running NeonDB took hours instead of weeks.
- nikita 3y agoNeon CEO here. Did you deploy Neon on prem?
- zerbinxx 3y agoHi Neon CEO. I’m curious if users have deployed Neon as a (selective) audit-logging tool for configuration which might need to be edited or rolled back from time to time. Think configuration-driven/event-driven systems where an update to a single database-stored config can cause other downstream applications to start behaving mysteriously. Going to scour the website some more!
- nikita 3y agoWe have customers using Neon as a time machine b/c you can create a branch at a point in time. Is this what you need?
- zerbinxx 3y agoEssentially, yes. Between a few times per day and a few times per month I would like to create branches to store the “backup” copies of table-stored confs to compare against logs/events and see if configuration changes caused certain conditions to arise. In the case of a configuration error, rolling back to a prior state would be awesome.
- h1fra 3y agoThanks for sharing, adding that to the article.