Database

“Where we are is not in the build space. We're in the operate space. We operate the databases. So it's not just enough to launch something. You have to prove that you can operate it over, over many years and do it at scale. So there's this kind of moat that was…”

“And on Neon, it's actually pretty interesting too. It's launching, I think, thirteen million databases a day now.”

“Agents will probably continue to delete databases as long as you allow them to because they're goal seeking.”

“Database is a world where already the agents are creating more databases than humans. We've already crossed that line”

“Our approach to that was for the IPO was very much like, okay, databases, data at rest. But now all the parts of the company are connected. There's going to be an equally important problem of data in motion. And so, you know, the goal was to convey, Hey, these…”

“And this is certainly the true, certainly what we've seen with databases. Like certain databases have just skyrocketed in demand because they're the ones that the agents are pulling off the shelf.”

“Personally, I think still understanding systems is very important and just having some conception of, like, how, like, Git works, you know, or, like, HTTP, or databases, like, queues, like, all of these different systems. I think that those fundamentals are st…”

“Next thing is authentication. Honestly, isn't even needed for modern apps. Like mine doesn't have authentication or a database and I'm printing money.”

“Planning is really important when you're implementing something technical and let's say you're implementing payments or something that's going to be a change to your database. If the coding agent is just like, all right, I got it and just starts writing code. …”

“I think that could change, you know, like, as agents actually become kind of, like, more prevalent and are interfacing with each other, and therefore, like, perhaps, like, the number of transactions explodes.”

“Databases are a hard problem. Like you can only lose so much data. You can only have so many issues. You have to figure this out. And five years of investing in a database that everybody uses, it's, it ain't so easy to turn and leave your database.”

“The majority of what you spend your time on if you're scaling infrastructure are the databases and the database layer.”

“Data preparations for Rack is extremely important. And I would say that's like in the, a lot of the companies that I have seen, that's like the biggest performance in their Rack solutions coming from like better data, data preparations, not agonizing over like…”

“You really deal with log contention, and log contention is difficult. You, it's very, very hard to scale if everyone at the same time wants to decrement an integer in the database just actually then also the transaction involves Having to go to interchange and…”

“It is true that Epic's core database, the core single database, and this is Epic's big differentiation. There's only one database that every application pulls from.”

“No, I'm not. I'm sorry. I, I'm not. I think this is, yeah, we also seen other players that tries to, you know, move a lot of the logic into the database, agentic embedding inference and whatnot. I think if the right direction is to Keep infrastructure a little…”

“People who think of models as repositories of factual information, and they're treating them like the world's worst and most expensive databases. Like it's not, not super useful.”

“We've seen a lot of companies now start adopting similar flows, right? Like in the authentication space, in the database space and so on to make the tools available to agents without an explicit user's sign up and set up step first and delaying that step to af…”

“There will never be a Really popular database that isn't open source ever again. That just can't happen.”

“A new database would need to be open source or an API connecting with sensitive data in a CRM or maybe an EHR needs to be open source.”

“It almost feels a little bit like AI will be as common as the database to some degree for SAS applications.”

“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.”

“No large enterprise buys a database without talking to Gartner Group first.”

“And a lot of use cases of spreadsheets really should be databases or apps, right? Anytime you're dealing with something that's not like number crunching and instead is some kind of tabular data, a workflow, like a database like thing of customers, or it could …”

“Every software that's built, and even like any third party software you use, has a database. And the database contains all the valuable information. And that's your source of truth. Because if the database is wrong, I mean, the whole application is wrong.”

“Many folks might still be in the Excel world where you use Excel as a database, but Excel is actually a calculation engine. It's not supposed to be a database.”

“And I think it won't matter that much which database you use, just like it won't matter that much, which LM you use, but it matters what you do with it, how you tune it what kind of training data you add onto it to fine tune it.”

“They had spent over thirty billion dollars on databases and gathering data.”

“So I expect that some of the innovations that came from there like wallets, like identity, like verified credentials will just make its way into normal databases and already are.”

“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.”

“In five years from now, this is all gonna be in the background. Like, this is just going to be something that operates in the background, just like a database.”

“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.”

“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.”

“In 2000, if you aggregate the total enterprise value of companies that were principally driving their revenue from databases, it's about a trillion dollars in market cap in 2000.”

“And crypto is basically sort of SaaS meets open source. So it's all sort of running publicly in the cloud. And so you can make different applications with this. You can do these incentive structures and open governance structures and portability that you can't…”

“And you know, there will be hundreds of drug companies that will now start because of what's in that database.”

“An awful lot of the Walmart story is actually about computers because they use databases to have much more efficient supply chain and much more efficient inventory than a traditional supermarket did.”

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

“And we have grown our own proprietary database system over the past seven and a half, eight years. We have over 400,000 records in that system, right? Over 95% of the records that we have in our system actually have clearances, right?”

“We're establishing a new pillar in the enterprise software stack. And this is as meaningful a transformation as databases presented in the nineties, our cloud-based infrastructure in the early 2000.”

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

“We have ten million companies, three and a half million decision makers.”

“Most people that are talking about blockchain, they're really looking for a database.”

“So fundamentally, I believe that AI is going to get into every piece of software that we write in almost exactly the same way that databases got inside all the software.”

“Databases actually suck for the most part. They never let you do what you really want to do for your business use cases, and that's, it's always been a game of sort of leapfrog.”

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

“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.”

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

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

“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.”