26:38 Evan Weaver: yeah, there there are a lot. And you need to kind of adjust the way you view the database, like the traditional view of a database, even if it's a distributed system is a, you know, a single workload kind of Britt all operationally heavy system that you just don't want to touch. And fun, it just isn't like that. It's it's entirely so managed, whether you're operating at yourself, or using our service cloud, you can scale it in and out, up and down. Everything happens online, everything happens without data corruption without service interruption with us management built in automatically. And you can adopt kind of a platform approach similar to the way you know, in a large enterprise, like some of our customers, they'll have an internal compute platform that uses Kubernetes, or what have you, D CEOs are some of the older you know, orchestration and cluster management paradigms. But databases are still special snowflakes. And you have to you have to kind of bring your bring your thinking forward and think you know, what, if the database didn't have to be treated differently, then my stateless capabilities, what if, you know, I could provision a database for every developer for every staging environment for every build? What if I could, you know, run analytics workloads against the production data database by giving them a low priority, read on the key, that kind of thing. So really adopting that cloud native mentality, for the data tier, especially the operational data tier, it's just not something people are accustomed to doing. So we can do a lot of education there a lot of demo and a lot of communication to show that. No, it really is safe, it really does work. And at the same time, having global transparent access to all your data with low latency also leads you into different series of design choices for your applications. Because if you have, you know, an app, which only lives and in US East, you know, in AWS or what have you like to say it's been in the original data center for a decade, and there's weeds growing up and rain is dripping on the roof, and all that kind of thing. Like, you don't really see the benefit of global scale out unless you start refactoring your app to also manage, you know, data center, like level fail over. So if you're building a Greenfield app, and you build it totally stateless, for example, you're using server lyst framework, then even experience, which is much more like running a CDN. But it magically has access to transactional correct data under the hood instead of just cashing. But it's a little difficult to kind of enter that world, from a legacy mindset or from a legacy app.