Re:The Notifier Pattern for Applications That Use Postgres
by jjovan1 on Tuesday May 14, 2024 @12:56PM
(#40357291)
Hey Benesch, is Materialize used by TimescaleDB to create Materialized View? I noticed a similar approach.
[ Parent
| on HN ]
Re:The Notifier Pattern for Applications That Use Postgres
by benesch on Tuesday May 14, 2024 @03:22PM
(#40359069)
Not to my knowledge. I believe TimescaleDB has their own incremental view maintenance engine.
Re:The Notifier Pattern for Applications That Use Postgres
by jjovan1 on Tuesday May 14, 2024 @04:52PM
(#40360025)
Ok so I was wondering if your solution is faster. I noticed their materialized views are not as fast for real time data.
Re:The Notifier Pattern for Applications That Use Postgres
by benesch on Tuesday May 14, 2024 @05:29PM
(#40360366)
We haven't benchmarked TimescaleDB, so I can't say. Results tend to vary heavily by workload, too.
What I can say is that the research at the heart of Materialize (https://dl.acm.org/doi/10.1145/2517349.2522738) allows us to efficiently maintain computations that are more complex than what a lot of other IVM systems can handle.
Your best bet is to run your own benchmark of both systems using data that's representative of your workload. We offer a free seven day playground if you'd like to run such a benchmark: https://console.materialize.com/account/sign-up
We also have a community Slack where a number of Materialize employees hang out and answer questions: http://materialize.com/s/chat