In Materialize, responsiveness is about minimizing the time between an issued command and Materialize’s consistent, fresh responses. See how we built the Operational Data Warehouse to deliver Responsiveness along with Freshness and Consistency: https://t.co/zCvi7ItFgp
Join us at the first #PostgresNYC Meetup of 2024! Register today to join us in-person at the @MaterializeInc office with @PostgreSQL and hear @loiselleatwork discuss "Better materialized views in 1 million LOC: Inside Materialize's #PostgresSQL source." https://t.co/aAySHJWqXv
A large part of my role @MaterializeInc is building a real-time data warehouse *without* the typical complexities of streaming.
I'm excited to share how easy it is at #datacouncil24 with a talk titled "Real-Time Analytics for Small Data Teams".
https://t.co/TUzgGQFpm2
I’ll never get over how cool WITH MUTUALLY RECURSIVE is.
For many years I thought recursion in SQL was hard. Weirdly hard. Turns out the problem was actually that normal WITH RECURSIVE has sorta bonkers semantics. WITH MUTUALLY RECURSIVE fixes all that.
📚 Logical replication with Neon and Materialize
Learn how you can replicate Neon data in real-time with @MaterializeInc to build better, faster products ✨
by @morsapaes
https://t.co/zMqBnckiOe
Recently, I’ve had a chat with @nikhilbenesch, CTO of @MaterializeInc. We talked about operational data warehouse positioning, consistency and correctness, the evolution of Materialize, and even BYOC.
https://t.co/5sWkIlcwPz