 Hi, this is your host of the party and welcome to brand new episode here for newsroom and today we have with us once again You'll in Fisher. See you and founder of any nice. You'll in state to have your show. That's great to be here You know can you talk about you know any new additions? Features addition that were made to the any nine platform recently. We've been working on Kubernetes in context of data service automation for a few years and We've done we've created our own postgres operator We will create more operators in the in the near future But what we've seen is that a lot of our existing clients They they also now use kubernetes and they said look We love the any nice data services. We want to use them from kubernetes and Pretty much as we've predicted we have a lot of kubernetes clusters and we we need to Provide a database as a service to developers using kubernetes clusters. How can we do that with the any nice data services? so Now the situation is that we are going to add more data services also based on kubernetes So you have kubernetes based data services You have virtual machine based any nice data services and how would they coexist and how make you? How do you make them use or how can make do you make them consumable by application developers? When application developer groups will own different kubernetes clusters that that is basically the subject of the new kubernetes integration And it's not only about integrating the virtual machine based any nice data services in kubernetes But it's about central data service management in kubernetes as its own topic so The story behind that is the following so even customers Who who don't care or whether there's a virtual machine or a pod behind it because in the end for the application developer? It shouldn't matter so what they say is We know from the platform the platform operator teams They know providing application developers with the operational responsibility for databases could be problematic For various reasons for example because they are technological dependencies on run the data service, let's say there's a Component a kubernetes extension that stays in conflict with another cluster scope kubernetes extension or something like that Or because you just want to have certain amount of control as the platform team over the data service Instances because you want to be that second line of defense after application developers messed up So we have in this requirement was recurring to us And and basically meant we need to solve central data service management for kubernetes So we came up with an integration framework We had a kubernetes integration in the past and we created a second-generation framework for Allowing application developers to create their own service instances Introducing a concept for service bindings, which is nothing quite common in kubernetes the ability to create You know credentials for accessing a data service let's say a postgres user and also a kubernetes secret in the application cluster systematically so that if you have multiple apps Accessing the same database each app has its own dedicated user and this is all automatically handled for you so service bindings for kubernetes is a thing we've added and Also Integrating our famous backup and restore framework so that you can declaratively create backup plans and and an individual backups and recover them Where all the actual heavy lifting? Happens somewhere else So it's it's basically you you control your data services through your application cluster but the data service instances they run either as virtual machines or as port somewhere else and This this will entirely abstract from from where and what it's actually doing behind the scenes So you could create a postgres on as a pop based version or as a virtual machine based version Just like that you didn't thank you so much for taking time out today and sit down and talk about these topics Thank you, and I look forward to our next discussion. Thank you