 All right, ready to go. Hi everyone. I'm Mark Duiker, one of the Dapper community managers and of course I'm here to talk about Dapper Maybe some of you get it already with this hat Dapper is very useful for APIs for building secure and reliable microservices So let's set a bit of a context first So if you're building distributed applications that involve many microservices and different kind of state stores and different kind of message brokers Then you run into some kind of developer challenges, right? Because you always have to think about certain things One of these things is how you do like proper service orchestration, right? So how can you make like calls across different services in a reliable way How do you do like distributed tracing across services and also across message brokers Another thing is how do you do like access control, right? So how do you define which service can call which other service, which service is allowed to save some state to your database Which service is allowed to publish on a topic for instance And finally, how do you deal with resiliency? Because some things will always fail Maybe some services are not available temporarily or maybe a state store is unavailable for a moment So how do you do that and how do you reach rise for instance So if you're in this situation, then Dapper, the distributed application runtime is really something for you On the right you see our newly designed website, definitely have a look there later on Dapper runs in a sidecar, so it uses the sidecar pattern and the sidecar takes care of the heavy lifting So you just write your business logic in any language that you want in your application And the Dapper sidecar will take care of the security, the observability and the resiliency So if you look from Dapper from development to hosting, you can basically use any language to talk to the Dapper sidecar Because the Dapper sidecar accepts like calls via HTTP or DRPC We also have a couple of client SDKs as well, so if you prefer to use a client SDK, please go for that And Dapper offers like a very broad suite of different APIs that really speeds up microservice development One of the newer ones is workflows, you can now write your workflows in code and do like service orchestration via workflows And we also have like a pop-up API, a service application API, state management, you can do like the actor model and so on and so on And with each release of Dapper, this API server gets bigger and bigger And like I mentioned, Dapper has like built-in observability capabilities and security and resiliency And the nice thing is you can run it everywhere, right? Because it runs on Kubernetes, but you can also run it on VMs And you can run it on your local machine as well The nice thing about Dapper is that the APIs are decoupled from the underlying infrastructure So you can use the state management API in your own program But then you configure which underlying resource you use via component files And these are just YAML files that describe the type of component that you're using, for instance state management But for local development, you can use like a local in-memory store for instance But if you push the production, then you can change one of these YAML files into something else to use like a cloud provider state store for instance So it's a really diverse application or framework to use And there are over like 120 different components across all of the APIs So here's like a very concrete example of how you would use your Dapper APIs in your applications So for instance you have an application that's triggered by a Dapper input binding Maybe you're receiving a message from a Kafka message broker Then in your application you use the secrets API to retrieve a secret that you're using your application Then you do a call to another application using the service-to-service application API That other application will use the configuration API to read some config values Then application A publishes a message to a topic using the publish endpoint Then another Dapper service is subscribing to the same topic And that Dapper service then posts some states using the state endpoint And finally we use a Dapper output binding to maybe send a message via Twilio for instance So this is just one of the many ways you can use and combine different Dapper APIs to really speed up microservice development So about the product and the community, it's one of the biggest CNCF projects that's really cool We are about to go into the final graduation state that's been proposed for it by Mark Fossel So hopefully that will be done this year All of the 120 components are provided by the community, so that's really great There's over 3,000 contributors which is really awesome and we have a very big Dapper Discord So if you have questions, please go to that Dapper Discord So we have lots of Dapper users, these are the ones I can mention publicly We know of many more users but we cannot use their logo yet But there's definitely some very big names that are using Dapper Definitely large enterprise users are using Dapper There's also some deeper case studies on the CNCF website So definitely have a look if you want to read more about how these big enterprises are using Dapper We're doing like 3-4 releases a year So earlier this month we had version 113 So you can now use Go for workflow authoring or you can use JavaScript for workflow authoring And workflow authoring was already there for .NET and for Python and for Java But now even more languages can be beneficial of this workflow authoring You can now also use the actor model in Rust There's been a lot of performance improvements for the actor model in general as well And there's like a preview of component hot reloading So that means you don't have to restart your application anymore When you switch components The next release will be 114 probably somewhere in June The aim is to have workflow as a stable API A new thing will be the distributed scheduler So you can actually schedule calls for doing scheduled publishing for instance And dynamic subscribe and unsubscribe from topics There's many more resources online, definitely check out the website There's a YouTube channel and I also recommend you to go to the GitHub for Dapper Quickstars If you want to try out some things really hands on yourself go to the Quickstars Like I mentioned there's a very big discord with thousands of users If you want more information and some Q&A Also the maintainers are on Discord And of course we have like Twitter or XHannel as well And last but not least there is a Dapper game these days So if you want to play the Dapper game Come visit us at the DiGrid booth We're now at the developer con We'll be in the expo for the rest of the cube con as well at K30 Thanks everyone