Materialize

“We decided to look into Materialize, and by that evening we were up and running. And it wasn’t long before we started to see how it could be used in Production.”

““At Nanit, we didn’t have to reimplement our logic across all of our microservices,” Eddie said. “This streamlined our operations, and allowed us to avoid complex reimplementation.””

““Materialize really simplified our data architecture,” Eddie said. “Now our teams could just use SQL, instead of implementing complicated logic. This made things much easier and much faster.””

“In terms of saving developer time, one way to look at it is in comparison to some of our other choices for writing streaming data. It has allowed more people in the organization to participate in the development process, which has probably kept us from having to hire developers. There's big cost savings there.”

“The timing could not have been better with where we were with our architecture and app refresh cycle, and where you guys were with your initial release -- but more than that, it's been the great team that you guys have put together that really sold us.”

“Materialize has been very predictable. For us, the bigger challenge has been moving from MySQL syntax to Postgres syntax. That's probably been more of the learning curve than moving to Materialize itself. We have run into a few cases where a function doesn't exist yet, and you guys have been great about building what we've needed. That's been amazing.”

“Very quickly, we were starting to get meaningful answers, just downloading the code. That built a lot of enthusiasm for Materialize, obviously.”

“It's exceeded my expectations for where I thought the code quality would be for projects this stage.”

“Materialize is letting us use our existing knowledge. We have a small analytics team that works all day long in SQL. We have 10 years worth of SQL logic that has been built around the business already. From a very practical perspective, I need to balance our technical ambitions and what I think is going to be good for the business with what is practical and what we're going to be able to achieve without tripling the size of the engineering staff.”

“The way I think about the difference between interactive and non-interactive is: can you actually see and work with data as it exists right now, live, and feel like it's this sort of mutable thing you're touching in the interface? Instead of looking at a report of what the data was like recently.”

“Materialize is a flexible platform for expressing how you want to build live representations of what all the data you're storing actually means—in a way that matches how an agent or human would want to read it.”