3 ms·
We're self-hosting Neon with an internal Kubernetes operator (keep your eyes out for more info) and we're incredibly happy with Neon's technical solutions. I'm
by bittermandel 2y ago
We're self-hosting Neon with an internal Kubernetes operator (keep your eyes out for more info) and we're incredibly happy with Neon's technical solutions. I'm not sure we'd be able to build our company without it :o
- clarkbw 2y agoi'd love to learn more about what you're doing! if you haven't already, please send a message. definitely want to hear lessons learned with your k8s operator.
- deleted 2y ago[deleted]
- andix 2y agoWhat's your added value in comparison to using plain Postgres, for example with the CloudnativePG operator for k8s?
- bittermandel 2y agoThe by far biggest is being able to scale it on top of Ceph, while getting performance from NVMe disks on Pageservers. This enables us to increase efficiency (aka cut costs) by 90%+ in a multi-tenant environment. Of course we don't get the same out of the box experience as CNPG, but considering we have the engineering capacity to build those parts ourselves, it was a no-brainer!
- andix 2y agoThanks for the explanation! This sounds like the right use case to use something more complex. I’m always hesitant to add additional technology to the stack if it doesn’t provide a bullet proof benefit. A lot of use cases are perfectly fine with plain postgres, and I’m always fighting against polluting the stack with additional unneeded complexity.
- leftcenterright 2y agoSounds like a good use case. Do you have any benchmarks or numbers which you could share regarding the performance of database? (especially disk writes and reads)
- jpdb 2y agoWould love to see this! Are you able to handle branching as well?
- tristan957 2y agoAre you writing your own control plane or using neon_local?