Fastest Headless CMS on Earth - SonicJs on Cloudflare Workers
Fastest Headless CMS on Earth - SonicJs on Cloudflare Workers
Big Plans - Let's make SonicJs the Fastest Headless CMS on Earth!
I recently was turned on to Cloudflare Workers by a fellow dev.
I haven’t been this blown away by new technology since using AWS EC2 for the first time in 2007.
What are CloudFlare Workers?
So you probably know about Cloudflare’s CDN. But imagine if you could take it a huge leap further and deploy your application code AND database to the Cloudflare CDN in the same way that you can with your assets (css, javascript, images). Well, that’s precisely what CloudFlare Workers allow you to do.
Its like deploying your code with AWS Lambda, but instead of having to select a region for your code and database to be deployed, you instead have a “global” region, and your code and database is instantly deployed to over 200 servers farms around the world!
So regardless of where your end users are located in the world, they will experience insanely low latency for all requests. Couple this with Cloudflare’s KV Database (Key Value store) and we’re setup for building applications that respond to requests from our end users drastically faster than anything before possible.
This is a complete game-changer!
I should probably mention at this point that I am in no way affiliated with Cloudflare, I just think Workers are completely awesome. The pricing is also very reasonable and they offer a very sold free tier which gives you 15,000 requests per month. Paid plans start at only $5 a month, so it is very affordable for the vast majority of application infrastructure needs.
So what does this have to do with SonicJs?
SonicJs is a Node.js based open source CMS that I started many years ago. It has a solid following, but the CMS landscape is a very crowded space and it has not exploded in popularity the way that I had imagined that it might.
What I have realized is that most devs want to bring their own front end as opposed to having it partially built for them, the way a low-code system does (which is why SonicJs is also a low code platform).
So headless CMS are much more popular among my fellow developer target audience.
So what doe this mean for the future of SonicJS?
I am currently building a POC of a headless CMS-based version of SonicJs on top of Cloudflare workers from the ground up.
It will have an administrative backend where developers can log in as administrators with the below capabilities:
- Manage application authentication, registration, log in, forgot password, etc
- Manage users, roles, permissions, etc
- Manage content types (ie blog posts, books, movies, etc) using a drag and drop form editor
- Manage modules (aka Plugins), allowing the developer to implement custom workflows and business logic using Javascript/Typescript
- Manage media (images, videos, PDFs)
- Manage the backend UX itself, allows a developer to customize and brand it for their client’s needs
- Perform backups/restore
- Stage content in one environment and publish it to another (ie staging to production)
So if you are familiar with Strapi or other similar headless CMS, think Strapi on steroids in terms of performance.
That’s it for now - that’s the plan.
If you have any thoughts or better yet might be interested in contributing to this open-source project, please join our existing discord community.
← Previous Post