 Okay, thanks guys, thanks John. If you haven't registered for the event tomorrow, really, if you're serious about APIs, go there. If I look around the room, I see familiar faces and I know that you're probably not going to be the typical audience. If I look at the 600 people who are probably coming, many of you are presenting as well. So thanks John for the opportunity to really just rehearse some of my slides. Many of you will know that we all kind of do them the night before. I actually finished them last week, so I'm quite happy. It's going to be a busy week for us, right? So Axway has three sessions. My dear friend Emeline is here as well. She's going to speak tomorrow. We have a technical hands-on session. I think we are still able to have folks joining us where you get to know some of the bits hands-on as well. Yes, my talk's going to be about open banking, but really, I'm a geek. I'm a developer, right? And I wanted to look at this from that perspective. So I haven't rehearsed this much. My idea really is to say, let's, we are among friends. Let me show you the slides that I've prepared and what I had in mind in presenting it to the audience. So yes, I'm a developer advocate. I work for Axway, based in Singapore, traveling a lot, find me on LinkedIn, stalk me on LinkedIn. I will welcome that. My slides, and including this one, I haven't put them up yet. But I make it a habit before I start a presentation. My slides are in my GitHub repository. Am I standing in the way? It's probably better if I'm here. Right, so if we talk about social media, right? There's other platforms as well. And as I get to travel, I'm also a foodie, right? And I like seeing architecture. I like things. So there's other platforms that I use as well, besides LinkedIn, besides GitHub. And obviously, I like to take photos, right? So at some point, since I'm a geek as well, I was curious. So we hear a lot about this AI stuff, machine learning these days. And it's always really high level. And can we have some practical examples? And I was curious. So if a machine looks at my 1,000 plus photos, what would it see? And I said, yeah, let's take a lunch break and build this. And I'll show you the results before I show you how it's done. So I think if you showed me this 20 years ago, and you talk to me about, so there is a machine, it looks at photos, and it makes this. Because this is not something I built. This is something a machine built. This is science fiction. Today, people have an idea that machines can do this. Not sure about the how, but it is possible. So how did I do this? OK, I'm a Python dude. I use APIs. And in this case, I use Microsoft Cognitive Services. I could have used probably IBM Watson or Google as well. But I chose this one. And it didn't take me more than a lunch break to build this using APIs. This is where my clicker is dying. Oh, fantastic. OK, here we go. I was going to give you the examples, where, hello, I'm just going to click there myself. So we all know, you go to Google, you search for pizza, and Google gives you 50 million images of pizza. This is the reverse version, where you say, here's a photo, there is no exif, no metadata, anything. Here is just a photo. Tell me what you see. And the machine says, this is a close-up of a pizza. And I'm 92% confident. And here is a couple of tags. And I do this for another photo. It says, oh, this is a cup of coffee. And I'm not really happy with this clicker. A wooden table next to a window, 83%. A sunset over the ocean. So I mean, I have no idea how the machine does it, but it's spectacular. But yeah, a bunch of bananas. No, right? But it's only 37% confidence. So the only thing that I actually have done with the script is, when you build that word cloud, just take the photos where you're 80% sure or more. So I use this to set the scene. I'm an API guy. What is this API stuff actually about? And why should we do it? Because that's what we want to talk about, right? Open banking, the evolution in the roadmap. What is this about developers who get thrown into this? What's kind of the history in a few minutes? Because I work a lot with these people. What are the typical challenges and roblox that we see? And what do we need to build great APIs? And my point is, obviously, I'm a foodie, and the machine proved it. But I think my point is that today, when you use APIs, and when you have APIs that are designed the right way, it doesn't take you longer than a lunch break to build something like this. Because AI, cognitive services, is something really complex. There are days where I would like to understand how it works, but actually, I'm really good enough if I just use the API. So it abstracts something really complicated, and I don't care if this runs on a Raspberry Pi or on a main frame. I just know how does the interface work. And my point is, if you have a great API, people will use the service more. So in this case, cognitive services for Microsoft, it gets a lot more sample data. Because people use it more. The product gets better. People use it more. So that's kind of the message. And how do we apply this to the big topic? Because, ultimately, we want to talk about, oh, fantastic. Can you please just? Yeah. OK. We want to talk about the two walls, right? Open banking. There is the theme that was introduced by the regulators to the large banks, imposed. And there is everything that we are looking at from the Fintech and the financial services perspective, to create new offerings. And where you can do banking as a service without having that monster machine behind you. Offer and consume financial services in a new way. So to me, the big bang is in 2015 in the EU, where PSD2 launched the new way of doing things where the regulator said, we'll allow specialized and licensed startups to access your banking details on your behalf, where you are able to outsource that to a third party. And the banks are obligated to provide access. And what was the intention? To make things safer for the payments, to increase visibility, make things safer for the customer, and to have innovation. That was the overall theme. And then the guys in the UK said, yeah, that's awesome. But can we do a little more? And we want to talk about the individual phases, where we say payments is only the start. This is phase one. And then we speak about what do I need? I need to have access to accounts, which is the first phase. I need to initiate the actual payment. And I want to find out, has the payment actually happened? And what is the history behind this? So this one is talking about this part. And then this gets adopted worldwide, where the individual countries have their own interpretation, their own approach of looking at open banking, the way we have it here in Singapore is different from the way in Australia, the guys in Hong Kong felt. You know what? Let's just do it the way the guys in the UK have done it. So there is multiple renditions of those. Who knows this guy? OK. Maurice Moss from the IT crowd. Because what does it have to do with developers? Those are really special people. Marketing works very different if you are a developer. They can instantly verify stuff. They are very resistant to fluff as well. So how do you make it relevant for them? Because I get asked, so I'm bank number X. I'm bank number Z. How do I attract developers to work for me? What sort of environment do I have to create to make it acceptable? What sort of things are they interested in doing? And I'll take DBS as an example. It's a very visual bank over here in this part of the world. And when you go to the API portal, which is open to everyone, you can sign up, register, and have sandbox access to 200 APIs where you learn about how APIs work in general. And DBS can go to the National University and run a hackathon. You have no background about how our systems work. You actually don't need it. The only thing that you need is the API, the service catalog. Because my theme is, how can I build a Hello World program in five minutes? If you have somebody who joins your department and they take six months to figure out how your system works, how can I onboard a partner in a few days? How can I open my silo database to a different business unit? Or how can I enable someone from the community to leverage my systems to innovate new stuff? That should be the theme. The challenges that we see are very much about the interface design, the documentation. People will say, yes, we have APIs. And I spent a whole day with someone just to figure out how the API actually works. They have to call someone. There is an outdated Word document. The Word document might be up to date, but there is 17 parameters in it, and I have no idea what they do, where they come from, right? Which has a direct impact to security, right? If I want to make the API secure, it's got to be in the documentation. It's got to be in the Swagger document. Otherwise, a proper API management solution will block it, right? I'm not very religious about the cloud, right? You can use the cloud. You don't have to use the cloud, but it sets the expectation. If I'm a developer, I want access to a resource in, it doesn't have to be five minutes. Give me five hours. That's good enough, but I certainly don't want to wait five weeks, and then it still doesn't work, right? So how do I get access to resources? Quick prototyping. How can I quickly see something? How can I, you know, we have all these talks about elastic and Kafka and Kubernetes. This is all science fiction, right? Because we want to start something today. We don't want to set up a massive infrastructure just to get going, just to experiment, right? And plausible mock data, right? Semantic experience, where it's not just Lorem Ipsum and ABC123. There is many others, but I think I'll focus on just a few. Design first, right? Again, I'm pretty sure this is an experience audience today, but I never, never stop highlighting that we really, as much as I'm a geek, as much as I love coding, we've got to stop that and say, let's look at the contract first. What does the API do? What's the data model? How do I authenticate? Maybe what's the license, right? And then there is stoplight, there is swagger, there is postman, right? Which should be part of the initial steps before you code. And even when you code, you're like, do I really have to code or are there tools available that do the work for me? Because ultimately, and I mentioned that in several discussions before the meetup, if we do this the right way, right? What we are consuming, what Uli is consuming in his lunch break to build that Instagram bot, right? I want to go to an API portal. I want to sign up for a key. I want to download a swagger definition. I want to get API keys. Maybe there is OAuth in the picture. It's all about JSON, HTTP-based messaging. That's all I care about, right? And we have all these complex backends in the backend. And it's a great new world where all individual developers and teams can choose the tool that they like. But we need to have that managing infrastructure in the middle that I compare it to, it's a mix of a bodyguard and a translator, right? Got to see your ticket, otherwise you can't access my API. Oh, you speak SOAP, the API that's JSON. Let me translate that for you, right? I'm sure this is something that you're all familiar with. I've personally started a project, an open source project in 2017, which gives you open banking related docker containers. I've also put some of them live in a live environment which you can consume, right? So this is an ATM locator, this is payments, this is currency conversion, account management, right? Like seven, eight containers. And you can run them on OpenShift, you can run them on your Mac, you can run them on Kubernetes, you can run them on Windows. Basically every environment that gives you docker and you'll have immediately in an offline fashion, if you like, available containers that produce reasonable data in an open banking environment. Another method to get you started quite quickly. And yeah, that's basically my talk, right? Where I try to imagine that there is probably several folks in the audience who say, how do I get started? How can I have some quick wins? What should I do? And I don't want to do a thank you slide. I say, guys, use Postman, use Stoplight, use Swagger, if you are not already doing that. Check out my stuff on GitHub, follow me on LinkedIn. There is material that you can use for free. And join meetups like the API craft because it's all about how we share and help each other. Thanks.