Does this fix how much of an insane memory hog materialize is? Some queries are just impossible if you can’t use disk. This is why I was forced to stick with Flink. Even though materialize makes things appear stupid simple and easy with SQL, I found that you can only do the most simple streaming views with it. You can’t even do unique counts with this for very long without breaking—and there’s no probabilistic alternatives.
Bad for big data. Great for small and simple data sets. But who is using Kafka with small data?
Also they do not integrate at all with custom data types in Postgres IME. E.g. an enumeration in your table will mean materialize can’t read the table as a source. Lame.
DNA is not digital though. It has a geometrical structure (independent of epigenetic modifications) that is dependent on a slew of environmental factors that alters it’s meaning. The computer programmer’s incessant need to reduce complexity to bits needs to stop.
Bad for big data. Great for small and simple data sets. But who is using Kafka with small data?
Also they do not integrate at all with custom data types in Postgres IME. E.g. an enumeration in your table will mean materialize can’t read the table as a source. Lame.