Changelog

If you've heard of serverless' virtues, but have never taken that first step toward trying it out, this crash course is for you. Here's how you might feel by the end: What a journey. You have now witnessed the transition from traditional web development into the serverless revolution. With these simple tools we now have everything we need to create awesome, scalable, and reliable applications. In my humble opinion, this is all still too much work for most of us to go through. AWS needs some serious competition in this space. Said competition is undoubtedly on the way.

Why is serverless a good fit for status page systems? According to the author: It eases your pain caused by the scaling / availability issues. It is terrible if your service is down AND heavy traffic from stuck users stops your status page. It enables you to pay only for what you use. A status page only occasionally gets huge traffic. The system takes only $1 per 30,000 visitors and almost $0 if no visitors. Makes sense to me. 💯

A new microsite by Chris Coyier. Let's get one thing out of the way: it still involves servers, so that word serverless might feel a bit disingenuous. It's actually a new way to pay for and work with servers that, in many cases, is cheaper and easier than buying and managing your own servers. In addition to a nice description of what Serverless is (and isn't), the site includes lists of service providers, ideas about things you could build, and related resources.