database

“My belief, I'm a little biased, but my belief is that if we kind of project out Say five years, 10 years, is that what we're gonna see is you'll have a few tools in your toolbox for databases.”

“So, I think for large enterprises, they'll probably want one of everything.”

“80, 90% of our infrastructure is databases because we're storing all this data.”

“So the reason why you switched from spreadsheets to databases, which is a completely different kind of thing, right, is because of spreadsheets couldn't handle the larger amounts.”

“Nobody can answer on Wikipedia the way that you would answer with a database or anything like this, doing reading.”

“Like, I don't think the popularity of Kafka means that, that, that databases, you know, go away.”

“You can make a whole company just out of syncing one database”

“So these collections are, can, you know, can be repeatedly used for different downstream kind of data processing tasks without ever impacting or touching that database again.”

“But a key thing to understand about Flow is that it is not a database. It is not storing copies of your data. It is really concerned just with coordinating your existing data systems and how data is moving between them.”

“We think the database will be, like, much thicker than it's been before.”

“There'll be language models running inside the application code, obviously, language models running inside the database as well or large models more broadly, multimodal models will run, you know, everywhere as well.”

“There's not a single, really a single database out there designed in that specific way to be able to do that”

“What you'll see with other databases is they then design parts of it in Rust, and then gradually more and more that becomes Rust over time, and maybe some of it doesn't, but it's much easier when you go forward from the basis of everything is built in Rust.”