 in technology called RSS. Holy Moly. I just realized that Glacier just launched in Singapore like two weeks ago. Well, you would have known it earlier if you just looked at your RSS feed. In fact, I think I even highlight, you see over here, I highlight Singapore. I use this ancient RSS feed reader called Newsboiter. And I think it's fair to say this is the fastest way of seeing what's new. And you can do what I do in highlight terms. Is that clear? Who's using RSS or another good one is the YouTube. I think the AWS YouTube, fantastic. I think even though it's XML, the YouTube AWS channel has also got a lot better. And they usually, I think there's another channel called Cloud Guru, not AWS. They give a nice roundup of what's new. So, and I don't know, it's better than me telling, reading something off here. Because a lot of the stuff is quite boring. No, it's really interesting. No, it's boring. Actually, the fastest way is just to have Slack. Just put your RSS integration. You read it every morning at night. Oh really? Okay. Slack. Slack? I heard of it. It's the one that kills two gigabytes of RAM, right? Is that the one? I've only got eight gigabytes of RAM. So I'm very careful with my Slack. Don't invite me to a Slack group. Fishing attacks. Pardon? I said it's also very popular for fishing. Oh really? Okay. I'm not a huge fan of, who's heard of this thing called, it's an ancient protocol named IRC? I'm an IRC. Is anyone else? Oh, cool. I'm Hendry on FreeNode. I'm on a few networks. You can message me and I'll probably ignore you. It's pretty cool like that. Okay. No. Where's my talk? Nope. That wasn't my business. So, oh crap. Let me just make sure I'm with them in time. I just want to keep it short. So, this doesn't look right, does it? Does it look better? One day I'm going to figure out XORG. I'll publish the slide somewhere. So, a couple of weeks ago I was invited as a user group leader to attend this meetup in Seoul, which Amazon sponsored. So thanks Amazon. I went to Seoul. It's been to Korea. It's quite great. I like it. Korean food. The climate there is also quite awesome. And I gave a talk there in Korea with other community members to sort of showcase in Singapore, telling people that Singapore is the most awesome place in the world. It is. But I also used to live in Korea. And I must say, I missed a dish right here. It's a seafood hot pot. Where the hell can I get this in Singapore? Because it just doesn't taste the same as that gorgeous, gorgeous dish. Pardon? It's special, all right? I used to live in Korea, so it was great to go back there. But the talk I gave is a message I want to share with you guys too, just to reiterate. I work with serverless stuff at work for Spool in the Juche area. Spool is in the Juche area. You should hang out with me. We can talk about AWS stuff. And we've used, we've fully embraced serverless. So we, I mean, I've lost count of how many Lambda functions we got in the panel. It's very easy to lose count, right? I think it's like something crazy, like AT or something at the moment. And I think to save you guys a lot of trouble, I'm just going to share my experiences of having AT Lambda functions. What problem we had was coordinating them. And obviously, the go-to thing for coordinating serverless stuff is SNS. What does that stand for? Something, something, something. Yeah, that's the one. Using SNS is quite painful. Let me just quickly skip ahead. This is basically what your interface looks like, right? It's the SNS message, which you basically encode your data as JSON, which you string a file and you pass again. And I daresay that's the wrong way to do it. I encourage you to think of another way to do it, or the way that I'm doing it, is using a standards-based approach, making sure you have a restful interface to your Lambda functions. And that is achieved with a thing. Yeah, I'm just explaining where it fits in there. You still use API Gateway. You actually still use SNS under the hood. But it's actually rewriting it so that everything just works. And that particular tool to do that is called ApexUP. It's not for any particular language. You can even be crazy enough to use Python. Python 2 or 3? Oh, yeah. I have doubts. But Apex is a tool by this really brilliant guy named TJ Holloway-Chuck. I stalk him on the internet. He's amazing. I mean, he's just good and I don't really look at his stuff that much. But he is the guy behind ExpressJS. And now he's more into Golang. But Apex is a reverse proxy that basically abstracts that crazy SNS interface out and you just basically deal with restful types of interfaces. So basically, you have nice benefits to that. Your routing is really easy. Your local testing becomes easy. Another good thing about Apex is that it's really fast to deploy. It's like five seconds to deploy. It has nice little things like logging. But the most important thing is that you do not... Like, previously when I talked to people about serverless, the topic that came up was like, oh, you have to re-engineer your app for serverless. I don't think that's strictly true nowadays with things like Apex. You can just use the standard request-response model. Of course, if you use a crazy FDAP stack like Rails with Puma and Sidekick and Bullshit, you're going to have a problem. But if you have a standard request-response model type application, you can deploy it on Lambda. You can deploy it as a service application and you can reap the benefits, the glory of serverless computing, which is like, you know, fine, forget... I'm not going to go... I can't even remember what the benefits are. They're just awesome compared to running an EC2 instance. So that's what I wanted to share with you. So what did I mention? Oh, yeah. The other thing you could do is run ECS, which I have to do for the Rails app at work or kind of. We've kind of gone back to Corpistano. Who uses ECS here? I want to cry with you. ECS running Docker? No. Don't do it, guys. Go serverless. You'll thank me later. You'll thank me later. Another thing that's painful about AWS, not to poo-poo AWS, but some of their products kind of suck, and that one is called API Gateway. It is horrible. But the good thing is that Apex can abstract that away, so you just have your standard routing with your Express app or your Golang app, and you don't have to deal with this. What's the politically correct term for bullshit? You don't have to deal with this, which is awesome. Apex has a lot of examples and a whole bunch of languages. In fact, you don't even have to write any language at all. You can just use static stuff, and it really helps. Deploying a static distribution with S3 and CloudFront can be a bit of a pain. You install Apex app, you configure your key, and you just type up, and your resources are there in five seconds. It's a breath of fresh air. So I really wish, I really wish, yeah, I really like it. So, unlike doing blue-green deployments with ECS, which is quite tragically difficult, you get blue-green deployments. Who knows what a blue-green deployment is? I'm not running it. It basically means you don't drop a request, which is a pretty professional way of deploying an app. Most people, I dare say, eff it up. But this thing with serverless, you get blue-green deployments out of the box, and it's like this in five seconds? Holy shit, we're living in the future, guys! Couldn't have dreamed that. What next? Rockets going from Shanghai to freaking California? It's never going to happen. We're living in the serverless world. So yeah, the great thing about this solution is that you don't have to hire schmucks like me to do your ECS stuff. I dare say, you don't have to worry about ECS instances. You just deploy the serverless so you can fire me, but I'm actually a programmer, so you might want to keep me around. It saves a lot of time, and it saves a lot of money. Like, seriously, we have a couple of production serverless apps at work, and I think we're still well within the, what do you call that, the free tier. So, yeah, this is where I invited Korean people to my home that I was joking, actually. I wouldn't let them come inside my home. No, no. If anyone likes drinking, we can continue outside. But yeah, that's it. That's what I wanted to share. Serverless is really coming of age. Thanks. Oh. A couple of announcements. I think, Valentine, did you want to... Oh yeah, one minute. Well, you got a minute. It's WordPress.