 Okay, good morning. I'm going to get myself started at this. I hope we're all settled in. So welcome indeed to the first app developer con in Europe. It's amazing to have you all here. Fantastic. So I'm going to be your host today. My name is Mark Fussell. I'm one of the program chairs of app developer con. I'm also maintainer on the Dapper project for CNCF. And I'm also the CEO of Diagram. And I hope we have a very exciting lineup for you today. The premise of this talk and why are we here is about a year ago, we went to CNCF and said, look, there are all these people at turn up that want to talk about developers and how you build applications. And we need a forum to talk about this. And in fact, if you actually look at the CNCF stats themselves from the last two coup cons, you'll see that over a third of the people that turn up are developers like yourselves, architects as well. And there's a lot of discussion around infrastructure and option environments and how we build the distributed systems. But how much do we talk about the applications design themselves? How do we talk about the business that has to be built by you as a developers by architects? And how do we have a forum to discuss that? And in fact, if you dive into those numbers, you know, a large number of people turn up like yourselves here wanting to talk about full stack development or back end distributed systems. So that's the premise of app developer con. You meet like minded developers. We talk about architecture. We talk about the application design themselves. I'd like to kind of introduce you as well to the other people in the program committee. And I was trying to look out for them if they were here, but Roland Savita or Valentino are here from Red Hat. They, along with myself and Mauricio from Diagrid and Paul from IBM formed the program committee. We were lucky that we had 150 submissions, which is a huge number to go through. We go through a range of different topics. We try to kind of spread across the spectrum of everything from development tools to deployment to how you do patterns for design, the use of libraries, serverless, venting based paradigms. Certainly we're interested still in migration. There's plenty of that still happening today. And we have one of those great talks that covers that. I wish it was a little bit more AI in some of the CFPs that were submitted in terms of how it's actually being used today. We had a few of them, but not as much as I expect to have. And then we always try and do a little bit of future looking stuff. This is a sort of idea of the talk. We welcome you that will hopefully hold this again. In fact, we will be holding this again in North America. And of course, all the subsequent app developer cons and coupons from now on out. So I encourage you to submit CFPs themselves about for talks that you would like to hear of these. So thank you for the committee. Thank you for those people going through these. It takes a lot of effort and a lot of energy. Hopefully we've inspired you by picking a set that will help you think about your application design and take this forward. So if we dive in a little bit more about what does it mean? I thought I'd just draw out a classic cloud-native architecture, the combination of externalizing some APIs, using that through policies and API gateways in order to make sure that you have external APIs exposed to your end users. Typically, of course, increasingly, we see that built upon sort of platform APIs around service discovery and identity. And then particularly, of course, the application architecture itself. What are the architectures application? How do we put those patterns together? And how do we take advantage of backing services, all sort of stitched together effectively with the CITD pipelines and deployments and all the things you need to actually get your code in place. And what that means is diving into architecture discussions. Yes, we can talk about the bonnet. It exists. It's a great application design. But this is CNCF. We like to break those things apart. We like to build it into other architecture designs, certainly the rise of microservices, the de facto pattern, a venture of applications, and putting those all together. So this is kind of a celebration of that and how we put those together. And then when you look inside the application itself, what are some of the patterns that put the applications together? How do we think about messaging? How do we think about building stateful, long running, durable applications and sharding, building resiliency with throttling retries and circuit breakers? And certainly how you then put together other patterns that put you in the place of the application developer thinking about how is it you design scalable systems? Certainly one of my favorite I see all the time is we talk a lot about distributed applications, but the coordination across them and how you actually build distributed systems where you actually make sure that you deal with compensation and failovers and the recovery from them, the saga pattern around those. We see a lot of this where people simply write their code and then have to fall into place about how they stitch all those applications together. So I see a lot of that happening. I'd love to hear from you about do incorporate workflow engines into your design, how you put your code together. And so this is captured in sort of the talks that we do. But building these systems is complex. In many ways there's complexity in two angles. There's complexity of the business itself. I mean, we shouldn't be scared to say that enterprise applications are complex, but then there's sort of complexity of the technology and how we put it all together. And it makes our job difficult. But the challenge for us as developers is that we love to build abstractions on top of complexity. And in fact, that's exactly what we should be doing. So as we evolve these distributed applications, we should be looking for abstractions to help us not reinvent the pattern. There is so much time that we rebuild things and rebuild platforms when we really should be building on the business logic itself. So let's think about those abstractions. How do we make things easier for ourselves in the sea of complexity? At the same time, let's not stifle innovation. We have to have innovation. We want to build new things. We want to build new technologies. But along with innovation, at some point, you have to get to some agreement around things. In many ways, sort of Kubernetes has became an agreement around what you do at the hosting level. For me, I think the agreement around open telemetry that happened over the last five years where we went from a diversity of different monitoring, diagnostics, tracing tools to a single protocol has helped enormously in terms of how we think about designing systems. And I think we should do that in other places as well, where we can, given the fact that there's a complex world of different technologies that we have to put together. So with that, I just thought we'd just do a little kind of exploration about what the audience was like, who we are today, and where have you all come from. So I'm going to ask you a few questions and let's kind of discover a few things about where our background is. So first, I'd love to ask you, you know, let's talk about languages, because that's the easy one. So how many people here programming Java? Oh, good number of hands, I expected that. How many do JavaScript? Okay, Python. Oh, C sharp. Now the sea of hands rust. Oh, go. Oh, all right. Any language I should have said? Okay. Yes. All right. Actually, that was a pretty good mixture. How many use more than one language? Oh, wow. Yes. Okay. That's that's what increasingly I'm seeing as well, like the combination of languages, putting them together. All right. Okay. How many of you are involved with a platform engineering team or are a platform engineering team? Oh, okay. Just a few hands. Okay. Yes. So you mostly depend upon other people doing that job for you, hopefully, or you're part of them. How many of you deployed to more than one public cloud? Okay. So I shouldn't use this. How do many of you just use a single cloud? Okay. So most people still use a single cloud. Okay. I mean, it's just a good feeling for what, you know, the type of things that we build, the challenges we face and kind of hearing, you know, from you. So, you know, for me, you know, I put out a few trends that I think are interesting. You know, we tried to reflect these in the session. I think there's a whole interesting world of security out there where we're pushing security back into the application, the whole shift left movement, you know, not only just scanning software and infrastructure's code, but what is the application secure as you know, what is the lockbox inside the safe inside the locked room inside the castle behind the moat? You know, we all care about the moat, but getting inside the castle, you could still steal all of your crown jewels that were. So, you know, we got to look at the application security itself more in depth than how is it that we make sure that we do security between services themselves. I think there's a lot to explore around observability and sort of chaos engineering space. How is it that we understand the end-to-end system and see the diagnostic? I mean, effectively, observability is a lifeblood. You know, if you don't have observability in your distributed application, you're effectively walking blind in the world. So, understanding how we incorporate that into our application design is important. Working with those platform development teams and internal developer platforms, effectively, we see more and more now that most organizations having two or more of something. So, consolidating those around and providing that abstraction layer around them. And then I think there's a strong will of like the multi-platform, multi-run time and multi-language emergence. There was a world where, you know, a lot of the cloud providers said, here's the platform or the paths that will run all your code. Turns out it doesn't work like that. And, you know, typically you have to choose the platform as the best choice for where you run your code. You have to choose the runtime as well. And as you just demonstrated, you know, a combination of languages put it together. And so, there's this world now with, you know, multi-paths platform and multi-run time and multi-language and how we shape that and put that together in a way that doesn't breed that complexity and also doesn't breed that deployment nightmare I think is something interesting to explore. That leaves on to sort of cloud portability. I asked a multi-cloud question just because increasingly both through legislation and lack of vendor lock-in and the idea that you can move your code around, you know, cloud portability, whether it's on-premise to the cloud or multi-cloud is increasingly emerging. And finally, you know, I wouldn't be behoofed to say that, you know, AI is affecting many of the roles that we're building inside applications themselves and in fact the blending together of building small and more discrete models and putting that with procedural code I think is an emerging topic and I'd love to hear more of that in terms of discussions that we have here in the future. So, if you put this all together, I think we have an amazing lineup of sessions covering across sort of polyglot application development, across, you know, bit of migration and developer tools and, you know, hopefully you get from this a wealth of knowledge and things to take away. I thought I'd just pull up this one little fun example that I came across the other day of a sort of the use of observability as I call it in power transmission and this company called Hymdel, you know, they looked up power systems and from where the energy was generated and to where it was distributed was complete lack of observability. They had no idea what was happening on the power lines and it turns out that if you simply know the temperature at each of the power line points along the whole distribution, you can actually effectively optimize how you distribute the energy, including shutting down in power power lines because you can approach more energy down through a particular cable because the cables as they get warmer, sag more or as they cooler can take more energy through them. So, they literally dropped these observability balls down this power line and now they can simply see the temperature along the whole power line and effectively observe their application end-to-end in this case power distribution and shut things on and off. And I thought it was an interesting example of putting together, you know, IoT observability and thinking about sort of, you know, how you see what's happening inside your systems. So, with that, you know, I'm going to close this out. I deeply want to thank all the sponsors for this. Sponsors are an important part of getting these co-located events running. I want to thank our diamond sponsor Heroku and along with that are two platinum sponsors, Diagrid and Dagger. They all have tables outside. I encourage you to go visit and have a conversation and find out about them. I've been asked to make sure that you're aware of making sure that we treat others with respect in the code of conduct of CNCF and there are snacks outside at the end of this event. There is actually a co-located event that happens on level 7.1 that you're all welcome to attend and apparently there's little signs outside that you can write. I'm a Java developer on and you can go and find other Java developers and rush around. And finally, I want to leave you with a survey. We're going to try and improve these things. We're going to make them better. Either visit the Bitly link at the bottom there or scan this QR code. But please, please, we'd love to hear from you. What is it important for you? What is it you want to see at future events like this? How is it we can make this better? In the end, you know, application developers, I believe are the heartblood of cloud-native computing because if you don't build an application, what do you sell to make money? So here we are gathered together and hopefully you've been inspired by today. So thank you.