Why do we create websites in JamStack over WordPress?

#Performance

JamStack websites are generally more performant than WordPress websites because they are statically generated, meaning that all of the HTML, CSS, and JavaScript are generated at build time rather than dynamically generated on each request. This can result in faster page load times and a better user experience.

There are several reasons why JamStack-driven websites leads to better performance:

1. Fewer Server Requests: With static site generation, all of the content is pre-generated and served to the user as a static file, or ready to be generated on-demand if content is dynamic. This means that the server does not have to dynamically generate the content on each request, which reduces the load on the server and speeds up the response time.

2. Caching: Static files can be cached by the browser and by intermediate caching layers, such as CDNs, which means that the content is served to the user faster.

3. No runtime Server-Side Rendering: Server-side rendering, where the server dynamically generates the HTML for a page on each request, can be resource-intensive and slow down the response time. With inremental static site generation, the HTML is generated at build time and in background on horizontally-scalable lambda functions, so the

4. server does not have to do any rendering on each request.

#Security

JamStack websites are generally more secure than WordPress websites because they are statically generated, meaning that there is no server-side code that can be exploited by attackers. This makes JamStack websites more resistant to common security threat like SQL injection attacks, cross-site scripting (XSS) attacks, and server-side code execution.

There are several other factors that contribute to the improved security of JamStack websites:

1. Fewer Moving Parts: WordPress sites often have many plugins and custom themes, which can add complexity and increase the attack surface. We use separation of concerns pattern to achieve the best performance and security.

2. No Server Management: There is no need to manage a server or worry about server-side vulnerabilities. Everything is covered by AWS and Vercel with their serverless computation and edge-functions. This can reduce the attack surface and make it easier to maintain the security of the site.

3. Improved Deployment Workflow: The deployment workflow for JamStack sites is generally more streamlined and secure than that of WordPress sites. This can make it easier to deploy updates and patches that improve the security of the site. In Gorazdo, we use branching-strategy and develop new features in isolated staging environments.

It's worth noting that no platform is completely immune to security threats, and it's important to follow best practices and keep your site up to date to protect against potential vulnerabilities.

#Cost and time of development

There are several reasons why we in Gorazdo save time and your money on development:

1. Separation of Concerns: With JamStack, the frontend and backend are decoupled, which means we can integrate any 3rd-party services, databases and it allows gradually migrate from one to another if nesessary.

2. Simplicity: JamStack websites are generally simpler in technologies than WordPress websites because they are statically generated and do not have a sophisticated server environment. This can make it easier to understand how the architecture of the site works and to make changes to it.

3. Flexibility: With JamStack, we are not limited to a specific set of tools or technologies. This gives us an incredible flexibility in technologies, services and 3rd-party intergations.

#Low maintenance and hosting cost

Serverless computation, also known as function-as-a-service (FaaS), can be cheaper than traditional WordPress hosting for several reasons:

1. Pay-per-use Pricing: With serverless computing, you are only charged for the resources you use. This means that you are not paying for idle resources or resources that are not being fully utilized. This can result in significant cost savings, especially if your site has variable traffic or usage patterns.

2. No Server Management: With serverless computing, you do not need to worry about managing servers or maintaining a server infrastructure. This can save you time and money, as you do not need to hire staff or pay for server maintenance.

3. Scaling: Serverless computing can automatically scale to meet demand, which means that you do not need to over-provision resources to handle peak traffic. This can result in lower costs, as you are only paying for the resources you actually use.

4. Reduced Overhead: Serverless computing can reduce the overhead associated with running and maintaining a server infrastructure, which can result in lower costs.