|
|
|
|
|
by vaughan
1890 days ago
|
|
> If you cannot refresh all of the views, at a single point in time, then there will be internal inconsistencies in your dataset. In the simplest case, I'm talking about regular SQL non-materialized views which are essentially inlined. > incremental computation will provide both lower latency and greater resource efficiency. Wish we had some better database primitives to assemble rather than building everything on Postgres - its not ideal for a lot of things. |
|
I see that now -- makes sense!
> Wish we had some better database primitives to assemble rather than building everything on Postgres - its not ideal for a lot of things.
I'm curious to hear more about this! We agree that better primitives are required and that's why Materialize is written in Rust using using TimelyDataflow[1] and DifferentialDataflow[2] (both developed by Materialize co-founder Frank McSherry). The only relationship between Materialize and Postgres is that we are wire-compatible with Postgres and we don't share any code with Postgres nor do we have a dependence on it.
[1] https://github.com/TimelyDataflow/timely-dataflow [2] https://github.com/TimelyDataflow/differential-dataflow