Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
The engine is open source: https://github.com/cloudflare/workerd
We did not create our own engine to create "lock-in". On the contrary, it would be a huge win for us if we could simply run FastCGI or Node or whatever applications unmodified. We'd be able to onboard a lot more customers more quickly that way! Our product is our physical network (with hundreds of locations around the world), not our specific development environment.
But none of that tech scales well enough that we could run every app in every one of our locations around the world, at an affordable price. Meeting that goal required new tech. The best we could do is base it on open standard APIs (browser APIs, mostly), so a lot of code designed for browsers ports over nicely.
(I'm the lead engineer for Workers. These were my design choices, originally.)
We're working on the documentation, I agree it can certainly be thin (or just not understandable). Please do file an issue for any improvements you'd like to see: https://github.com/cloudflare/cloudflare-docs/issues
Related posts
- It's now possible to find the AWS Account ID for any S3 Bucket (private too)
- Cloudflare Workers: Unpacking My Fundamental Misunderstanding
- Configuring applications to secure site
- cloudflare-docs/_index.md at production · cloudflare/cloudflare-docs
- I'm a little new to Cloudflare any suggestions on how to use it properly?