Currently at Snowflake building managed Postgres. Formerly Crunchy Data and AWS.
www.crunchydata.com/blog/crunchy...
www.crunchydata.com/blog/crunchy...
Now you can seamlessly move data and stream changes from your operational database into an analytical system.
www.crunchydata.com/blog/logical...
16 grams of coffee
16:1 water to coffee ratio
Slowly pour 48mL (the pointer size on 64-bit platforms) of water every 45 seconds until you reach 256 total mL
16 grams of coffee
16:1 water to coffee ratio
Slowly pour 48mL (the pointer size on 64-bit platforms) of water every 45 seconds until you reach 256 total mL
For object storage AWS has S3 and CloudFlare has R2
For distributed SQL CloudFlare has D2 and AWS has D
For object storage AWS has S3 and CloudFlare has R2
For distributed SQL CloudFlare has D2 and AWS has D
- No views/triggers/sequences
- No foreign key constraints
- No extensions
- No NOTIFY ("ERROR: Function pg_notify not supported")
- No nested transactions
- No JSONB
What, what IS it compatible with?
- No views/triggers/sequences
- No foreign key constraints
- No extensions
- No NOTIFY ("ERROR: Function pg_notify not supported")
- No nested transactions
- No JSONB
What, what IS it compatible with?
Ingredients: Paxos, NVMe drives, RDMA, epoll, blood, sweat, tears.
Packaged in a facility that contains clock skew and inter-zone networking charges.
Ingredients: Paxos, NVMe drives, RDMA, epoll, blood, sweat, tears.
Packaged in a facility that contains clock skew and inter-zone networking charges.
"PostgreSQL compatible, offering a subset of PostgreSQL" != PostgreSQL compatible. YugaByte and Cockroach already made this mistake.
"PostgreSQL compatible, offering a subset of PostgreSQL" != PostgreSQL compatible. YugaByte and Cockroach already made this mistake.
The concern is really about write latency and the consequences of eschewing coordination to achieve latency goals.
The concern is really about write latency and the consequences of eschewing coordination to achieve latency goals.
Our principles were:
- Most data lives in S3
- @duckdb.org has the best query engine
- Iceberg will be the dominant table format
- No compromise on Postgres features
So, we built Crunchy Data Warehouse.
1/n
Our principles were:
- Most data lives in S3
- @duckdb.org has the best query engine
- Iceberg will be the dominant table format
- No compromise on Postgres features
So, we built Crunchy Data Warehouse.
1/n