Jamstack is the real deal, here’s why
JAMstack is the real deal, here’s why
Over the last two years a convergence of architectural patterns has begun homogenizing these choices. I’m always look for ways to improve performance, lower costs, and achieve scalability. The earlier you can build that foundation, the smoother growth and agility can be to achieve.
What is Jamstack?
In it’s basic form, JAMstack is a moniker for a new web architecture. the JAM stands for “Javascript, APIs, and Markup. Most folks are familiar with a LAMP stack or traditional three-tier web architectures. This has been the go-to choice for decades for many a startup, PHP still commands a 78% market share on the internet. (https://w3techs.com/technologies/overview/programming_language). JAMstack flips this, creating an effective abstraction from the backend, leaning on a much more powerful client-side in the browser.
JAMstack isn’t new, it’s been around roughly since 2017, stemming from Netlify as their new cloud-native web architecture. The early years focused on content management competing with the likes of WordPress by providing a simpler and modern developer experience. It was rising in popularity in parallel with ReactJS at the same time, however both technologies lacked the breadth of features and support ecosystem to be viable for smaller startup teams. That’s all beginning to change, ReactJS
Why you should consider JAMstack for your startup
JAMstack is revolutionizing the way we think about workflow by providing a simpler developer experience, better performance, lower cost and greater scalability.
Notes:
Evolution of a startup, team size scale to technology requirements, begins typically with a monolith, fewer people, lower complexity, easier communication. Once domains begin to rise to meet product demand/complexity, new processes and tools will be required. It’s an opportunity to refactor code to match org to match the business. Microfrontends can help facilitate this in a more natural progression by providing a modular approach to technical domain decomposition.