 Okay, awesome guys. Thank you so much. Can I start with a good awesome. Hi guys. Thank you so much for coming here My name is Edith and I'm the founder and CEO of solar IO and I'm really really excited to be here for two reason number one Really really passionate about what we're going to talk today and number two I think it was two years since I talked to a real audience so let's talk So as I said solo is the company that I founded and we are focusing on solving the application that working problem so the connectivity and as one we basically living this STL community are stuck is basically STL and envoy and therefore we have working very very hard upstream We have two to see member from the six that exist in STO and we are working very hard to kind of like push the project for it We have basically a platform called glue mesh and this platform is basically a Built from four pieces the first one It's basically the mesh go a core and that's basically what it's basically an STO upstream within the hands from us like external and rate limiting is where is a set rotation and a lot of other stuff and Big big focus on multi-clusters The second one is we basically took the STO ingress and get right and basically make it a full-blown API Getaway so what we did we extended with a lot of and we filter like WAF like Like the data loss provision like soap the only STO soap that exists in the market and so on and The lesson at least we have developer portal again the only developer portal that exists first year in the market today and it's supporting, you know open API and as well as gRPC so that's what we have and The last and not least what we have is extension and extensions is basically the ability to customers the service mesh to your need And we're doing it with wasm. So it's built into our platform It's working seamlessly and you will be able to write your own custom filters to and boy Okay, so that's great. So as I said service mesh and boy proxy, that's where we're focusing and Service much is solving a lot of problems you all know because that's why you are here One of them is networking the other one is observability and the lesson not least is security and policy That's the stuff that they are focusing on this is great But then what happened is that there is a request coming into your clusters and there is some getaway that catching that request And it's going to some service and sometimes it's maybe a front-end service, right? Maybe some UI of your application and then in the UI micro services You have a lot of code. What is this code doing? You need to basically aggregate all the data from all those micro services that is connected to So maybe what you wanted to ask yourself is give me all the engineering solo that's working on glue mesh and earning less than 200k that means that we need to go to the engineering server to the product service to the final service to the To the ha and basically make the match to return that That that off So this is where graph kill is coming into the place, right? And as you know, hopefully, you know graph pl idea is basically to abstract that loss logic and basically Suggested that as as an obstruction Basically, you will make one request to the GraphQL service and the GraphQL service that is basically configured by Configuration and declarative configuration will go and do all those run-through for you Okay, that's great. So what is graph QL graph QL is basically the ability to do 8 to ask all your services use all your services as a query language, right? Get all the data that you want with Query language and it's very very very quick, right? You can see really quick animation, but basically as you can see you're adding filled boom. It's giving you the So it's pretty pretty true Now It doesn't mean that it need to do it only for one service, right? He can do it from a lot of surface It doesn't really care how much service you need to query from and that's what you can see you have three services here You're asking a query again in the response. He's going and doing all the run-through for you. You don't know honestly it's abstract for me so that's what graph QL is and Then biggest point about graph QL and I think it's really really important is how easy it's making to consume it And I think this is something that you will hear from a lot of our front-end team and UI team They want graph QL because then it's one query that they're putting in their application and basically the data is coming to them So it's a declarative query. It's quick and it's bringing you very easy to consume which one one request So now the question is what's the problem? Why am I telling you about it? This is a service mesh So we'll tell you why because actually build this graph QL service It's actually taking a lot of time you need to take some libraries, right? And this library usually a lot of the time that at least the leading one is no JS because it's a UI kind of like front-end team and Then you need to give them the schema and then you need to build in the resolver Which basically will resolve to that graph and then you need to deploy it and build it, right? This is another thing that you need to take care on your infrastructure And of course, you know, you can't have something in your infrastructure without security and observability that too risky specifically because it's kind of like acting right now as your Gateway so it's really really dangerous So when you're looking at this we try to figure out if there is any way for us to make that thing Simple that we're working with a lot of customer in production and we constantly heard about that conflict about There is this graph QL. There is a service match already ever get where how is that going to work? And that's exactly why we decided to make it better So envoy has this amazing ability to basically be extendable and this is why we a big fan of that And what you can do is basically you have the notion of Filter chain and the request is coming to the filter chain and going to a filters that you can put your own Custom filter inside and that's what's solo doing a lot, right? So if you see about what our differentiator, we know and we're in and out. So we have rough support We have data loss provision a filter. We have a double a slum that the coin creating the relationship in them They the trust immediately we have request and response transformation one of the most Honestly, but probably being used filter that we have we brought soap to envoy right and therefore to STO as well And now we basically brought graph QL to us to avoid. So what does it mean? so Basically we build a graph QL server that coming before the router and honestly if it will eat this it's not going to the router and basically know how to get a query and Basically go and do all this round trip for you He know how to do this and by doing this if you think what we just did we now be able to leverage in everything that and we're giving Us out of the blue so for instance the security the tracing the observability we getting it The caching everything that envoy can give me I can basically leverage right now in graph QL And the only thing that we need to give him is a schema right to know You know how to process the request and a resolver and the resolver we build in a lot of our resolver But honestly we also creating an integration with wasm that way that you can build it in any language that you want There is over and dynamically loaded to end right and that's really important. So again Basically what we just did right now is that every service slash get away in your infrastructure Know how to talk and become a graph QL server without you Need to do much so the question what do you need to do and as I said what you need to do is to give the schema and the Resolver, but we actually thought that we don't even have to let you do this So we find a way to auto generate the schema and the resolver for you for those services So how do we do this either? We're using open API or we're using, you know, uh, so swagger Are we using a you know, uh, whistel or anything that we can in order to kind of like understand What the schema should be and they're basically converted as the resolver So again, you basically can make everything in your infrastructure with a click of a button now Basically serve graph QL don't need to do anything. Just click a button and said I want that service as a graph QL Okay, but we didn't stop there because we also think that if everything in your infrastructure is graph QL And again, the reason to use graph QL just to remind you easy to use right? You're the velocity of the people that consuming it will go up dramatically So what it was very important to us is also to stitch it because if everything right now is a little graph QL That represent those graph we also need to stitch it and that's what we'll do in the getaway So we actually built into that envoy Stitching and federation is coming next. So basically again click off a button You're just telling us the relationship between them and boom everything declarative You can actually have graph QL everything in your services and stitch the on the getaway Okay, so now we have also another piece on that pattern right this is this is a product right This is what we are selling and now we're selling only also that piece which is again flip over button everything can be querable But in glue it's actually even more interesting in our platform because in our platform There is the ability to actually create what call a workspace. So what does it mean a workspace? The workspace is basically a ability to take namespace cross-class there in same class there Wherever you want and basically create a workspace and delegate it to your team And when you delegate to the team, you also tell me what they allowed or not allowed to do Okay So basically this is a very very interesting way to actually expose and delegate that in your organization The beautiful of it is now you can also export export Services in your workspace to the other so for instance I'm the billing service and I wanted to be consumable but all my company I will be able to expose it and what will happen in the other services They will see a catalog and those catalog is basically will allow them to import that service So now they will basically be able to said I want to take those So, you know, this is the services that exposed to me and click on a button I can consume them to my walks and If you're consuming it, let's do it the right way and what we basically did was that let's embed a developer portal in that Process so when you actually try to import a service in the catalog You will be able to get everything the developer portal giving you which is basically the docs Try it get the keys Whatever you want on boarding your people very easily and until now you could have done it with open a bi and glpc But now we also you can expose anyone you can decide that either to expose this as a rest like it is or so Or you can expose it as a graph QL And then you will see that you will be able to see that you will be able to Let your team easily consume it with the flag So that's what I have but I wanted to kind of like summarize what I just talked about because I think it's extremely important What we saw me is a huge huge technology problem. It's not easy. So trust me. Anybody. It's not easy writing C plus Ascing graph QL inside and boy, it's even harder though Which I think it's very very important is the fact that we're solving a conflict inside your team We had customer coming to us constantly and said My team one graph QL. How's that working with service mesh? So here is how it works in service mesh It's part of your services. He's taking advantage of the service match You don't need anything in your thing and in a quick on a button. You can basically enable your your you know Your velocity or your organization? So that's all I have and I think I'm out of time anyway, so thank you so much and hopefully you enjoy