The Jamstack is a modern approach to building websites and apps, delivering better performance, higher security, lower cost of scaling, and a better developer experience. However, with so many tools to choose from, it’s easy to feel overwhelmed.
You get excited about a product only to find out you need to fill in your credit card details in order to sign up. Or you can use it for free with one exception—the feature that got you excited in the first place. Conditions, rules, exceptions... enough. What if developers actually designed a free headless CMS plan for themselves?
In the times of monolithic systems, it was crucial to pick the right system at the beginning. That decision inevitably locked you with a single vendor for years. Nowadays, in the microservices era, vendors claim itʼs easy to switch between their systems. Letʼs take a look at what “easy” means when switching your headless CMS and whether that decision could cost you your job.
The microservices approach promises easy switching between services and claims to enable you to use the best-of-breed tools. Is this true? How hard is it to switch a headless CMS that powers your website?
What is Sourcebit? How does it work and how does it make Jamstack website implementation easier? Should you use it for your next project?
I aim to answer these questions during my presentation about Sourcebit. I explain how it tries to unify the relationships between headless CMSs and static site generators.