The next generation of Materialize
materialize.com
The next generation of Materialize
1–10 of 46 posts
Re: The next generation of Materialize
#2The downside is they pivoted away from supporting running it yourself. The technology is certainly exciting but also changes the target demographic. I'm curious to see how it plays out
Re: The next generation of Materialize
#3I've worked on specific instances of this problem at a few companies and its hard! The number of ways distributed systems can fail only serves to compound the complexity here as well. Each time I've built one of these systems its taken years to get it almost good enough to keep customers happy and to meet our performance goals. However, the resulting system were plagued by deep set correctness bugs that were the bi-products of early decisions made by engineers who didn't understand correctness.
It's really exciting to see a system getting built by people who know what they are doing and will be hopefully a more "correct" solution.
Re: The next generation of Materialize
#4From a technical point of view Materialize seems absolutely fantastic - everything that the Firebase databases are trying to be, except with full SQL support (well, minimal SQL support - there's no RETURNING, ON CONFLICT or json - but probably good enough, we at least get JOINs and CTEs).
But unfortunately they only seem to be interested in enterprise customers: Not only is it not open source, but there's no open sign up and pricing for compute nodes isn't publicly available!
Re: The next generation of Materialize
#5From a technical point of view Materialize seems absolutely fantastic - everything that the Firebase databases are trying to be, except with full SQL support (well, minimal SQL support - there's no RETURNING, ON CONFLICT or json - but probably good enough, we at least get JOINs and CTEs). But unfortunately they only seem to be interested in enterprise customers: Not only is it not open source, but there's no open sig…
> well, minimal SQL support - there's no RETURNING, ON CONFLICT or json
We support both `INSERT ... RETURNING` [0] and the `jsonb` data type [1]. The only feature in your list that we're actually missing is UPSERT (i.e., `INSERT ... ON CONFLICT`). We have a tracking issue [2] if you're interested in following along.
> But unfortunately they only seem to be interested in enterprise customers: Not only is it not open source, but there's no open sign up and pricing for compute nodes isn't publicly available!
Rest assured: we're working towards open sign up! We're at the very beginning of our early access period.
[0]: https://materialize.com/docs/sql/insert/#details
[1]: https://materialize.com/docs/sql/types/jsonb/
[2]: https://github.com/MaterializeInc/materialize/issues/6668
Re: The next generation of Materialize
#6No post body was provided.
Re: The next generation of Materialize
#7The downside is they pivoted away from supporting running it yourself. The technology is certainly exciting but also changes the target demographic. I'm curious to see how it plays out
Such a shame, I had an ideal use case for a product I'm working on, but there's no way I'm shackling it to cloud vendors. Just not a good fit for this product.
I really hope materialize eventually inspires something like it in the open source world.
Re: The next generation of Materialize
#8From a technical point of view Materialize seems absolutely fantastic - everything that the Firebase databases are trying to be, except with full SQL support (well, minimal SQL support - there's no RETURNING, ON CONFLICT or json - but probably good enough, we at least get JOINs and CTEs). But unfortunately they only seem to be interested in enterprise customers: Not only is it not open source, but there's no open sig…
[deleted]
Re: The next generation of Materialize
#9Wow that's sad, I was really excited by the promise of this project. But going cloud native means I won't be able to use it in any of my projects any time soon.
Re: The next generation of Materialize
#10Wow that's sad, I was really excited by the promise of this project. But going cloud native means I won't be able to use it in any of my projects any time soon.
[deleted]