What problems is Crunchy PostgreSQL for Kubernetes solving and how is that benefiting you?
Render has been using Crunchy’s PostgreSQL Operator to power our PostgreSQL database as a service product for over 2 years and we've been very happy with its performance so far.
There's a few competing offerings but we decided to go with Crunchy as they met all our feature requirements, had very good documentation, and their commercial interests aligned well with their open source offerings.
I also really like the fact that we haven't been forced into any sort of vendor lock in. It’s been quite easy to use the components we want and ignore the ones that don’t fit our use case. We've found it straightforward to hook into the operator and extend its functionality when required.
Finally, the operator is quite resilient and portable across clouds. We haven’t run into any major issues in production that stemmed from the operator's codebase. As Render has expanded its services across multiple regions and clouds we haven’t had to tailor our use of Crunchy's PostgreSQL operator to any particular region or cloud. Review collected by and hosted on G2.com.