JAMstack Is the New Development Architecture

The server-based architecture has become too complex

As websites and web applications get bigger, include more functionality, and become more dynamic, server-based architecture is increasing in complexity. Additionally, security, data and performance requirements lead to further pieces in the architecture puzzle as well as increased maintenance, updating, and upgrading. In today's tech, features are king, and the time spent working with a complex architecture is time away from features. So what is the problem and what is the solution to combat this growing trend? After all, your company needs to focus on what is important: your business.

Complex Server-Based Architecture

Databases

Simple default configurations for databases no longer meet current performance requirements. This requires a lot of action and administration (tuning, redundancies, migration in the CMS, schema adjustment, backups, patches, updates, indexing, etc.).

Cache systems

Without caching, performance is poor. The big challenge is to keep the cache consistent and valid across multiple servers and redundant databases. This required a whole cascade of action (database replication, content consistency, cache invalidation, etc.).

Application server

This requires a high degree of administration (backups, keeping security plugins up-to-date, etc.).

CDN

Without Content Delivery Networks (CDN), large videos and images are not readily available. These large files take time to download and the further they are away from the end-user the longer the process takes. Conventional CMSs are not designed for this, which means increased effort (keeping content in sync, versioning, etc.) and poor performance.

Server

The issues of scaling, redundancy for servers and load balancers, development, test and production environments, firewall configuration, patches, updates, etc. are all time-consuming and costly.

JAMstack is the new development architecture

The JAMstack approach (JavaScript, API, and pre-rendered HTML markup) is just a few years old. It is a new method of creating websites and applications. Content is no longer processed and generated afresh on the server for every visitor. It is generated locally in the browser as JAMstack pages. Dynamic applications can also be processed in the browser thanks to JavaScript and APIs.

Classic, legacy and modern web architecture

Relocation from the server to the browser

The former principle of loading as much of the work as possible onto the webserver is outdated. Today’s user devices have more than enough resources to run web applications. This also includes mobile devices.

JavaScript frameworks

Google, Facebook, and others have developed completely new web frameworks based on JavaScript, such as the JavaScript library React, and then released them as open source. React has been the most popular and fastest-growing JavaScript framework since its first application in 2011. The use of such web frameworks creates a new development architecture, where applications are no longer tied to specific operating systems or webservers.

Modern web APIs

Modern web APIs can be integrated for any JavaScript client to implement third-party services such as business applications with access to CRM and ERP systems as well as eCommerce functionalities such as payments and subscriptions. Utilizing web APIs can eliminate the need for additional servers.

Microservices architecture

Because web functions no longer need to be managed in the server, websites can be designed around microservices. A microservice undertakes a narrowly defined task which is initiated, carried out and terminated independently of other microservices.

Current browser technologies

JAMstack relocates the logic from the server to the browser, where the pages are dynamically generated through APIs and microservices. Modern browsers can interact with many APIs using JavaScript, as well as execute complex and dynamic applications.

Decoupled architecture

The tasks carried out at the backend, such as creating, managing and saving content, are separated from the presentation on a frontend device (so the architecture is headless, or decoupled). Once it has been created, content can be used for any device. The functionality taking place in the frontend and the deployment of individual APIs can now be handled in isolation.

Pre-rendering of HTML markup

In the JAMstack approach, the website HTML is no longer generated by traditional frontend web servers, but rather the page is preconfigured, distributed via a Content Delivery Network (CDN), and displayed in the user’s browser. All other activity takes place in the browser because the pages contain JavaScript code that access APIs and is executed after the page is rendered.

JAMstack for Web Projects

The JAMstack approach has several key advantages over the traditional server infrastructure. It enables higher performance, improves security, lowers costs, scales more easily, and delivers a better user experience. Download our free white paper to find out more about the revolutionary architecture and learn how Scrivito is using it to make our customers' web projects successful.

Register to download the white paper

required field

More great blog posts from Michał Kunysz

  • Diagram showing native CMS cloud solutions like Scrivito have already integrated the CDN

    Particular Challenges for the JAMstack Approach

    The transition from the server-oriented LAMP stack approach to the new JAMstack approach has proven to be a practicable concept. In recent years, a large number of JAMstack web projects have been implemented. The concept applies to smaller websites as well as complex web applications with...

  • JAMstack - JavaScript, API and Markup jam jars

    JAMstack for Web Projects

    Faster, More Secure and Easier to Administer

    In the early 2000s, webservers were developed and optimized in leaps and bounds to deliver HTML pages. These days, this has become a part of the problem. Server-based web technologies are no longer sufficiently performant, they are too complex, too expensive, too high-maintenance and too...

  • Modern JAMstack web application architecture vs traditional web architecture

    Zero Hacks

    Win the Update Race Against the Hackers

    As seen in many reports, vulnerabilities in web-based CMS systems are a constant factor. Common CMS security issues are derived from running default installations which are not security-hardened, not regularly updated (often hard to do, given the 542 security exploits WordPress suffered from in...

  • List of seful, customizable widgets Scrivito offers out-of-the-box

    10k+ Audited Frameworks

    Low Code: Avoiding to Reinvent the Wheel

    Security is a challenge Many CMSs, mainly open source, offer hundreds of plug-ins to enhance the functionality of the websites and the CMS. Some are useful, many are not. A certain degree of redundancy exists. They are often created by the community or anonymous third- party companies, which...

  • pyramid hierarchy

    < 10 Min. of Training

    Only by Providing Users with a Great Way to Utilize the CMS, Projects Will Succeed

    User experience is key to success The usability of many traditional CMSs is poor. Some systems are even inoperable from the user's point of view. This starts a downward spiral: the more difficult the use of the CMS, the less it is used - quickly leading to outdated content on the websites....

  • 99.95 % + Uptime

    No Breaks in Content Delivery.

    Non-stop availability Running a traditional content management system comes with system administration jobs that might affect the availability of service: installing CMS patches and avoiding breaking plug-in dependencies while doing so, updating staging and production systems, CMS and...

  • 100 % Cloud

    Only the True Cloud Offers Real Benefits

    Full-stack, cloud-native architecture Current CMS set-ups require a lot of IT infrastructure. In addition to the CMS and the operating system itself, databases, servers, load balancers, monitoring/backup systems, and search engines are needed. The production environment includes development and...

  • CMS-Projekte erfolgreich aufsetzen

    Status Quo - The Role of the CMS is Changing 

    Limitations of current CMS systems The web has constantly changed and improved since Sir Tim Berners-Lee invented it in 1989. Unfortunately, the technology behind it has not. Web pages still load too slowly, responsiveness sometimes is just a promise, and weak security remains an ongoing issue....

  • JAMstack, full of jam

    Everyone’s Talking About JAMstack, But What Does it Mean?

    You’ve probably heard a lot about JAMstack recently as it is one of web development’s great buzzwords in 2019. And you maybe don’t know that our enterprise CMS Scrivito is based on this architecture. So what exactly is JAMstack? According to jamstack.org JAMstack is “a modern web development...