Re:Snowflake to Buy Crunchy Data for $250M
by compton93 on Monday June 02, 2025 @07:07PM
(#44164264)
> literally name themselves as "Postgresql Data Warehouse" but correct me if I'm wrong
That's not their primary product. Crunchy Postgres is their primary offering and they recently announced Crunchy Data Warehouse.
I thought Crunchy Data Warehouse was their main product, looking at most of their marketing posts. What's the advantage of using their managed PostgreSQL offering on the cloud, compared to native offerings such as AWS RDS and GCP Cloud SQL?
Re:Snowflake to Buy Crunchy Data for $250M
by samokhvalov on Monday June 02, 2025 @11:00PM
(#44165853)
1) built using an open source kubernetes operator, as I understand
2) Crunchy provides true superuser access and access to physical backups – that's huge
Re:Snowflake to Buy Crunchy Data for $250M
by anonymousDan on Tuesday June 03, 2025 @12:22AM
(#44166238)
Why is that huge out of interest?
Business continuity. If you don't have access to your backups, there's nothing you can do to work around a vendor issue.
Re:Snowflake to Buy Crunchy Data for $250M
by apexalpha on Tuesday June 03, 2025 @02:18AM
(#44166926)
Sounds like Stackgres?
Re:Snowflake to Buy Crunchy Data for $250M
by JacobThreeThree on Monday June 02, 2025 @08:36PM
(#44164972)
Neon acquisition was ~$1B.
We don't know that Snowflake didn't miss out on neon - seems plausible (and silly for neon to not run an acquisition by Snowflake)
In a way, Crunch Data was a competitor to Snowflake as they literally name themselves as "Postgresql Data Warehouse" but correct me if I'm wrong. Neon sounds more complementary to Snowflake as they were struggling with an OLTP backend, namely their Unistore product, which was announced 3 years ago but never went into general availability due to its scalability issues.
Maybe Neon was 4x more expensive, but this acquisition sounds more like an answer to Databricks than a strategic acquisition if I'm being honest. Apparently, they had $30M ARR, so it's 8x ARR, which is a cheaper answer to Databricks.