Evan Weaver: to me, the biggest gap is really that the server lists edge experience, like we're pushing the granularity of application building down to literally nothing like you had kind of a series of incremental paradigm shifts from physical servers to co located or leased servers to virtualized servers to containers, they're still all little servers. It's like, if you like every thought you had, you had to mentally conceptualize it as being in a book and in doesn't make sense from a productivity perspective to think about software, especially distributed software this way, like, who cares, like how many functions can run within one container, I don't, I just want to know if I have the aggregate capacity to execute the workloads my users are generating. And it requires a complete inversion of that abstraction, which we finally have now, for the most part, with server list frameworks and the compute side, we've had it for a long time with CDN and the caching side. But data, especially operational data is always the last thing to move, because it's the riskiest, so you can now get, you know, some server lists analytics capability with things like snowflake, but your canonical, operational user generated mission critical, you know, data, which is the existential underpinning of the business still lives and essentially, you know, a mainframe and what we're trying to push with thought, and what the entire industry needs to push is, you know, bringing this paradigm to its logical conclusion, which is you shouldn't have to care. Or even though as an application developer, how your data tier is operating, it should be completely orthogonal. And at the same time, as an operator, you shouldn't have to care what your applications are doing, like the the model of a DDA who has to like go in and like tune queries and make sure everything is safe to execute and fail over nodes to huts, barriers and stuff is an 80s model, we need to move past that to an arm's length utility computing service model where something's behaving badly. You know, in Florida, for example, if the application is consuming too many resources, lower its priority, you don't have to know what it's doing as an operator. And if you want global resources, as a developer, just provision a new database, you don't have even have to think about where this data centers are located. That's the experience we're closer to a server less and we're already there with CDN, but data is just harder, because the the, the quality bar is so astronomically high, because you know, I mean, the NO SEQUEL man was notorious for for essentially killing businesses, like dig comes to mind with their experience with Cassandra and people are smarter now. And they demand that their database vendors really do the work. But until until the vendors do like we're doing it for, we're still going to be stuck in that mainframe mindset.