Why is there a need for another framework? the current approach is not producing fast sites, and this problem will not disappear by waiting for a faster CPU.

Foreword

Qwik in Action

Introduction to the frontend development. Now, the responsibility of creating good or bad applications depends on you because the means available are all there.

Introduction

Overview of TypeScript. TypeScript introduced types into an untyped language like Javascript to ensure code consistency.

TypeScript

Overview of the frontend architectures. In this lesson you will understand the difference from Client Side Rendering and Multi Page Application.

Frontend architectures

Overview of the hydration. In this lesson you will understand the difference from Hydration and Island architecture/Partial Hydration.

Hydration

React Server Component. In this lesson you will understand the difference from Server Component and Client Component.

React Server Component

Qwik resumability will change the frontend ecosystem, In this lesson you will understand why is so great.

Resumability, the Qwik way

Wrap up of frontend architectures module.

Summary Chapter 2

In this lesson you will be able to understand more about performance and you will understand how improve your application with less JavaScript.

Qwik, the framework built on top of closure-extraction

Resumability is the core concept behind Qwik. In this lesson you will understand better the process.

Resumability

Code Extraction is a topic hard to master, you will understand how it works with different approaches.

Code Extraction

JSX syntax is the most famous one because of React, but what about the other frameworks, Vue, Angular?

Why Qwik use JSX syntax

Summary Chapter 3

Let's see together the fundamentals of Qwik. In this lesson you will compare Webpack and Vite.

Getting started with Qwik

The Qwik build process is so important because the resumability process requires correct and intelligent bundling.

Qwik compilation Process

Qwik CLI and amazing tool to have a great Developer Experience with Qwik.

Technical requirements to start a new Qwik application

Qwik Middleware an easy and clever way to expose your RESTful APIs or GraphQL APIs.

Middleware

Wrap up of Getting Started with Qwik module.

Summary Chapter 4

In this lesson you will learn the pillars of SEO. You will lean few new terms and metrics that can help you to measure your application.

In this lesson you will learn the some new things about SEO and crawler.

Sitemap and robots files

Partytown an amazing library to execute third scripts in the service worker.

Partytown

Core Web Vitals are so important for own application. You will learn in detail all the metrics.

Core Web Vitals

Core Web Vitals Labs Data vs Field Data. These two information are so different, let's figure out the peculiarity of those.

Labs data vs Field data

Summary Chapter 5

SEO and Core Web Vitals

There are many ways to deploy a Qwik application. You can have your own server and deploy your Qwik application easily with the Qwik CLI and integrations.

Deploy Qwik in production

Cloud solution are a good alternative for a low cost pipeline and host. Nowadays these kind of services are so smart and great, you should try them.

Cloud solutions

With different team and many developers, it's important to master branching strategies to avoid problems during your day by day.

Branching strategies

Progressive Web App approach can be an alternative to the stores. You can publish you application with a lot of benefit with PWA.

Progressive Web App

Wrap up of Deploy Qwik in Production module.

Summary Chapter 6

Style an application is so important let's see how engage your Stakeholders into this process.

Style and render data with Qwik

CSS is so huge, there are a lot of ways to style your application with Qwik, let's see them together.

CSS and Built-In Styling Methods

Tailwind is an amazing library, let's see together how master it. I will share you some tips and tricks to use Tailwind in a better way.

Tailwind CSS

In this lesson you will learn how manage data with Qwik. There are a lot of APIs to explore, let's jump into the code.

Managing data with Qwik

Summary Chapter 7

In this lesson you will learn how architect a modern frontend end application.

Creating an e-commerce with Qwik and Supabase

In this lesson you will learn the trade offs of technical decisions. I share with you some tips and tricks.

Technological spike

In this lesson you will explore Supabase. This is an amazing service to leverage your business.

Supabase for your backend

A custom authentication is too complex and risky to implement from scratch. Let's use the Supabase auth to optimize our goals.

Let's talk about the Authentication process

Summary Chapter 8

Supabase CLI an handy tool to improve consistency across environments.

Supabase CLI

Let's use the Supabase CLI to manage our database migrations and schemas.

Supabase db migrations

In this lesson you will create the e-commerce homepage with the Supabase client to read the data.

Show products on our homepage

Every e-commerce has a detail page, let's create our product detail page with Qwik.

Product Detail

Cache is really useful and in this lesson I will explain in the detail how it works. I will share my experience in this topic with some cool analogies.

Cache-control headers

Summary Chapter 9

Rendering products with Orama full text search

Let's improve out application with a useful "Add to favorites" feature.

Add a product to your favorites list

In this lesson you will learn how to use Stripe to manage your payments in a secure way.

Adding cart and checkout process with Stripe

Let's try the Supabase database function. This is an easy way to allows us to do several things and also add some logic to our procedure.

Page views tracking

A real-time database with Supabase is so simple to implement, let's build together a new functionality with this great feature.

Real-time database

Summary Chapter 10

Let's explore together the benefit of testing. In this lesson you will explore the various types of tests, Unit Test, E2E, Visual regression tests and more.

Overview of application testing

Let's discuss together how and when testing is valuable for our business. 3X Explore/Expand/Extract can help us is this reasoning.

How much testing is enough? When do I write tests?

In this lesson you will lean the Test driven development TDD flow. It's a really good practice to put in place.

Test-Driven Development (TDD)

In this lesson you will lean how test your components with Cypress.

Let's add some tests with Cypress

Do you need a Qwik component library? Qwik UI is the project for you because can give you a lot of Qwik accessible components out of the box.

Qwik UI

Summary Chapter 11

Adding tests to our Qwik application

Let's explore a bit of history of Qwik. A new framework with a great past.

Final thoughts

Qwik and React together, no problem, qwikify$ is the API to solve your problems.

qwikify$

Qwik and Astro together, no problem, @qwikdev/astro is the library to solve your problems.

Qwik inside Astro application

Qwik and micro-frontends together, no problem, out of the box Qwik can manage this scenario with no external dependencies.

Micro-frontends with Qwik

Summary chapter 12

Enter your name and email address below, then click the **"Send my free chapter"** button to get started

250+ page PDF

EPub

newline Access with Replits

All Code Samples

Discord Community Access

One-time price of $69

( the primaryDescriptionMarkdown is long - several lines, include images, as long as you want )

In this course we <headline of what we do>. <why this technology is good> but <here's how learning it is problem>. 

In <the length of these lessons> we cover <three salient points about what we cover. Your BEST points>. Its <however long it is> and comes with <these bonus features, and reasons to buy. code, etc.>

It's taught by <author name> who <credibility, reason you should listen to them>. <social proof, if you have it yet>

<then you can list other supporting stuff you want to add, anything you want here>

-------
Example:
-------

We created a free course to create your first GraphQL server (from scratch) using Node and TypeScript. TypeScript and GraphQL are a powerful combo, but there's a lot of confusing edges if you're getting it setup the first time.

In this course we cover the basics of getting TypeScript setup with Node, how GraphQL works, and how to set up a GraphQL server using Apollo server. It's two hours long, it comes with complete code examples, and we walk through the code step-by-step.

It's taught by my friend, Shopify-engineer Hassan Djirdeh and he's integrated what he's learned using GraphQL in production as an engineer at Shopify. We've already had over 1,300 students enroll and it's been getting great reviews so far.

// ... and so on

Harness Qwik Resumable Architecture for Lightning-Fast Startup Times

In this course we <headline of what we do>. <why this technology is good> but <here's how learning it is problem>. 

( the summary is short - one or two lines )

Complete Guide to Qwik

Starting with a greenfield application often presents a fortunate opportunity because it allows for the imagination to run wild. It's a chance to make decisions and consider what might be best for the application. Is this or that architecture better? How can the application be distributed to everyone quickly and easily? It's easy to get caught up in the moment's hype, but the best thing to do in these moments is to try to stay calm and put all choices on the table.

Listing the requirements to be met is certainly the first step to take. Who are the users? Will they use mobile or desktop? In what environmental conditions are they required to use the application? For example, suppose the typical platform user uses the app in an area with zero connectivity. In that case, this difficulty must be considered and, therefore, cannot be forgotten.

Once all these requirements are clear, the next step is to make the list of frontend architectures that allow for achieving the desired results within the deadlines imposed by the project. But what are the different architectures that can be chosen? The most important ones will be explained. This list will be very useful for aligning some terms and considerations that will be used throughout this book. The book's main topic is Qwik, but before learning to run, it's important to know how to walk.

Client Side Rendering is the process of sending to the browser a series of HTML, CSS and JS files with our logic and these files are the result of the compiling code we have written and the libraries we have used.
Single-Page applications (SPA) use this process and have been in vogue for many years in the frontend world starting with AngularJS way back in 2010 and then continuing with Angular and React and now many other frameworks. AngularJS was a game changer for frontend development because it replaced a way of developing applications where developer experience was sorely lacking.

Developer Experience (DX): We have already heard and digested the term user experience (UX) and it is the experience you have when using a product, service, or any system. This experience is based on the ease of use, its usefulness, and the perception we have of its use. If these users are developers then we can talk about developer experience (DX). Organizations that offer products, tools, or services for developers aim to improve DX. This particular attention leads to happy and loyal developers who will continue to use the products, tools, or services. This will also bring a further benefit because it will create word of mouth which will positively benefit and increase its use. A clear example is the presence of good documentation, easy to understand and resolves doubts very quickly.

At the time it was very difficult to write and maintain applications because vanilla JavaScript was used versus a more modern TypeScript used today.
Using JavaScript in large applications used to be the norm, but thinking back to the effort required to write such applications at the time and how easily bugs could be introduced without obviously knowing makes me smile. But let's not waste time talking and get back to the topic of this paragraph, Client Side Rendering.
The more features we add to our Single-page application, the larger the JS files will be and will affect the loading speed.
There is a clear direct correlation between functionality and required JavaScript, the bigger your app gets, the more JavaScript it will need at the expense of performance.

Libraries can be included to take advantage of functions written by third parties.
e.g., If I want to be able to easily manipulate dates and time zones, instead of writing all the logic to handle the various cases, I can download and use the DayJS library distributed via NPM, which is the repository of all the JavaScript libraries and more.

However, it's useful to know that the more dependencies included in the project, the more the size of the application bundle increases because the functionality is being added to the code base. Therefore, one of the best practices to apply is to keep unnecessary dependencies to a minimum. The compilation process will allow for optimizing and packaging the application code of the SPA and obtaining files that can be loaded when the application starts.

A usually very concise HTML file (index.html) will be produced, which, via script tags, will include all the JS and CSS necessary to display and make the application interactive.

This is an example of a real-world SPA index.html file. It can be noticed that it will appear as a blank page because there are no things to display.

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8" />
    <title>...</title>
    <meta
      name="viewport"
      content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, viewport-fit=cover"
    />
    <link
      rel="icon"
      type="image/x-icon"
      href="favicon.ico"
    />
    <meta name="description" content="..." />
    <link rel="stylesheet" href="theme.2780d3.css" />
    <link rel="stylesheet" href="styles.4e229bd3f.css" />
  </head>
  <body>
    <script
      type="text/javascript"
      src="runtime.7c545.js"
    ></script>
    <script
      type="text/javascript"
      src="polyfills.be8befaa.js"
    ></script>
    <script
      type="text/javascript"
      src="scripts.859e944f8beb.js"
    ></script>
    <script
      type="text/javascript"
      src="main.29d35dbd.js"
    ></script>
  </body>
</html>

An SPA application's build produces static files; therefore, our application can be easily served with CDN-based solutions.

Here, the CSR rendering process can be seen.

---
title: Frontend architectures
description: Overview of the frontend architectures. In this lesson you will understand the difference from Client Side Rendering and Multi Page Application.
---

# Frontend Architectures

Starting with a greenfield application often presents a fortunate opportunity because it allows for the imagination to run wild. It's a chance to make decisions and consider what might be best for the application. Is this or that architecture better? How can the application be distributed to everyone quickly and easily? It's easy to get caught up in the moment's hype, but the best thing to do in these moments is to try to stay calm and put all choices on the table.

Listing the requirements to be met is certainly the first step to take. Who are the users? Will they use mobile or desktop? In what environmental conditions are they required to use the application? For example, suppose the typical platform user uses the app in an area with zero connectivity. In that case, this difficulty must be considered and, therefore, cannot be forgotten.

Once all these requirements are clear, the next step is to make the list of frontend architectures that allow for achieving the desired results within the deadlines imposed by the project. But what are the different architectures that can be chosen? The most important ones will be explained. This list will be very useful for aligning some terms and considerations that will be used throughout this book. The book's main topic is Qwik, but before learning to run, it's important to know how to walk.

## Client Side Rendering (CSR)

Client Side Rendering is the process of sending to the browser a series of HTML, CSS and JS files with our logic and these files are the result of the compiling code we have written and the libraries we have used.
Single-Page applications (SPA) use this process and have been in vogue for many years in the frontend world starting with AngularJS way back in 2010 and then continuing with Angular and React and now many other frameworks. AngularJS was a game changer for frontend development because it replaced a way of developing applications where developer experience was sorely lacking.

> Developer Experience (DX): We have already heard and digested the term user experience (UX) and it is the experience you have when using a product, service, or any system. This experience is based on the ease of use, its usefulness, and the perception we have of its use. If these users are developers then we can talk about developer experience (DX). Organizations that offer products, tools, or services for developers aim to improve DX. This particular attention leads to happy and loyal developers who will continue to use the products, tools, or services. This will also bring a further benefit because it will create word of mouth which will positively benefit and increase its use. A clear example is the presence of good documentation, easy to understand and resolves doubts very quickly.

At the time it was very difficult to write and maintain applications because vanilla JavaScript was used versus a more modern TypeScript used today.
Using JavaScript in large applications used to be the norm, but thinking back to the effort required to write such applications at the time and how easily bugs could be introduced without obviously knowing makes me smile. But let's not waste time talking and get back to the topic of this paragraph, Client Side Rendering.
The more features we add to our Single-page application, the larger the JS files will be and will affect the loading speed.
There is a clear direct correlation between functionality and required JavaScript, the bigger your app gets, the more JavaScript it will need at the expense of performance.

> Libraries can be included to take advantage of functions written by third parties.
> e.g., If I want to be able to easily manipulate dates and time zones, instead of writing all the logic to handle the various cases, I can download and use the DayJS library distributed via NPM, which is the repository of all the JavaScript libraries and more.

However, it's useful to know that the more dependencies included in the project, the more the size of the application bundle increases because the functionality is being added to the code base. Therefore, one of the best practices to apply is to keep unnecessary dependencies to a minimum. The compilation process will allow for optimizing and packaging the application code of the SPA and obtaining files that can be loaded when the application starts.

A usually very concise HTML file (index.html) will be produced, which, via script tags, will include all the JS and CSS necessary to display and make the application interactive.

This is an example of a real-world SPA index.html file. It can be noticed that it will appear as a blank page because there are no things to display.

```html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8" />
    <title>...</title>
    <meta
      name="viewport"
      content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, viewport-fit=cover"
    />
    <link
      rel="icon"
      type="image/x-icon"
      href="favicon.ico"
    />
    <meta name="description" content="..." />
    <link rel="stylesheet" href="theme.2780d3.css" />
    <link rel="stylesheet" href="styles.4e229bd3f.css" />
  </head>
  <body>
    <script
      type="text/javascript"
      src="runtime.7c545.js"
    ></script>
    <script
      type="text/javascript"
      src="polyfills.be8befaa.js"
    ></script>
    <script
      type="text/javascript"
      src="scripts.859e944f8beb.js"
    ></script>
    <script
      type="text/javascript"
      src="main.29d35dbd.js"
    ></script>
  </body>
</html>
```

> An SPA application's build produces static files; therefore, our application can be easily served with CDN-based solutions.

Here, the CSR rendering process can be seen.

![CSR](https://d2uusema5elisf.cloudfront.net/courses/complete-guide-to-qwik/module_02/lesson_02.03/public/assets/CSR.png)

Steps:

-   Download the HTML
-   Via the links in the HTML, download the assets and the JavaScript
-   Run JavaScript
-   Render the application
-   Finally, the user can click

With this approach, the application will immediately download everything it needs, and all the logic will be available in advance, but this type of process has limitations that must be taken into account. The first limit is related to performance because the application will be downloaded entirely into the browser's memory, and therefore, the initial waiting times, before being able to interact with the platform, will require a few seconds of waiting for larger applications. When downloading the app, the user will only see a blank page until it is fully loaded, not the best user experience. Frameworks have introduced a lazy loading feature over the years to avoid this problem. Let's imagine an application needs to be optimized as a bundle because there are a lot of features and js to load. As developers, the code can be modified to isolate a certain part at the module level; for example, the user profile section can be isolated to load it only if the user wants to access that section.