The Simplified Stack

When you begin to design a serverless application, you'll probably find that most of the big cloud providers have more services than you can keep track of. This is good news, more services means you can pick the right one for your requirements!

But it does mean that you spend a lot of extra time trying to understand each service, and if the documentation isn't clear you may have to spend time validating system components, digging through documentation... You may even find that a service that looked good on paper is still technically in beta, or the provider isn't prioritizing patches and updates.

Even though Cloudflare "only" has 44 services, it can be hard to know what services are fully supported (versus beta or "public beta"), and the documentation isn't always clear on how to properly use them.

Introducing Plainflare: The best parts of the Cloudflare serverless stack, simplified and explained.

The services in the sidebar are ones that I have used in production systems and feel confident recommending.

Some of those services are used in production, but have caveats and footguns, so those are noted carefully and explicitly.

Finally, there's a list of services that are upcoming: beta or public beta. Some of those have been tested a bit, so if you live on the bleeding edge you can look there for guidance or inspiration.

If you want to get updates as this documentation evolves, be sure to sign up for the email newsletter.