Gunnar Morling

So the main component or let's say the main runtime, we target is Kafka Connect so Kafka Connect as a separate project under the Apache Kafka umbrella, and it's a framework and also a runtime for building and operating those connectors. And you would have source and sync connectors and DBZ. Essentially, it's a family of source connectors, so they get data from your database into Kafka, so you would have to have your Kafka Connect cluster. So this typically is cluster so you have again, high availability and this kind of qualities. So you would need to deploy the connectors there. Then we expose some sort of metrics and monitoring options so you always can be aware of Okay, and what status securit does the connector is doing a snapshot at which table is it in the snapshot? How many rows has it processed, or is it streaming mode. So you know, which was the last event, what is the kind of lack you would observe between the point in time when the event happened in the database and when we process it. So you have all those monitoring options in terms of upgrading? So that's that's a very interesting question, because there's many moving parts, right? So there's the DBZ version, maybe you do schema changes, while the connector isn't running consumers, they must be aware of all these things. So that's something you have to be careful with, we always document very carefully the upgrading steps. So let's say you go from one to medium version to the next you would have a guide which describes Okay, that's that's the matter. That's the procedure you have to follow. And in general, we try to be very cautious and careful about not breaking things in a incompatible way. So that's actually very interesting. When I took over from Randall I think the convergence was ODOT five or four, so some some early Oh dot x version, and now you've would think It's you know, it's it's it's very early and it was very early in the project lifecycle but still people were already using this heavily in production it only crew ever since. So now if you do a upgrade and you put out oh eight out of nine out of 10 and well we have lots of production users already and now of course we are we don't want to make their lives harder, right? So we are very cautious to if you have to change something to duplicate options, so it's not like heartbreak, you have some time to adhere to certain changes and this kind of stuff. And now just very recently, yesterday, literally we went to the one that old version. So that's the that's the big one, that final version we have been working towards to for for a long time. And now we are even more strict going forward about those guarantees. So that's the message structure and you know, there's no guarantees in terms of how this evolves in future upgrades and this kind of thing