Deploy Jamstack Websites at the Edge

Explore how Jamstack and Azion enhance e-commerce via secure, scalable solutions using Edge Computing, continuous deployment, and developer-friendly tools.

View as Markdown

Jamstack website architectures leverage pre-rendered pages and APIs to design web applications, significantly improving e-commerce capabilities with resilient, secure, and scalable solutions. These architectures manage every part of the application, from front-end to back-end, using APIs running on JavaScript, reusable Markup templates, and prebuilt static Assets, resulting in enhanced performance, higher security, cost-effectiveness, and a superior developer experience. Meanwhile, leveraging edge computing—processing data at the network’s edge closest to the user—can reduce latency and bandwidth use, further boosting performance.

This solution is ideal for organizations looking to enhance website performance, improve the overall user experience, and empower developers to rapidly build and deploy high-performance, scalable applications at the edge, closer to end-users.

Jamstack Website Architecture Diagram

Architecture diagram

Jamstack Website Dataflow

  1. The developer interacts with Azion’s platform using tools like the web-based Console and the command-line interface (CLI). These tools are essential for configuring and managing applications and services on the platform.
  2. Developers work on application code locally on their machines. When ready, they commit changes to their local Git repository and then push these commits to a remote repository. In the case of working with Azion, this remote repository could be linked to Azion’s platform to trigger further actions.
  3. The applications files are sent to Object Storage, then a bucket is created and the files are stored in it. The developer can store data and application assets here, which can be processed quickly by the application.
  4. Azion Actions sets up a Continuous Deployment flow, connecting the GitHub repository with the Azion application created in the deployment. This process is possible through the communication between Azion Actions and Azion API.
  5. Azion Actions deploy the application and its cofigurations, based on a default config or the one informed by the user in a manifest file. The configs include Rules Engine, Cache, Image Processor, and Functions.
  6. The output from the edge node is delivered to the end-users via a domain, representing the user-facing endpoint of the web where the hosted application is accessible.

Components

  • Azion Console: the interface where you can access all the available products and their settings.
  • Azion CLI: an open-source command-line interface (CLI) that allows interaction with Azion Web Platform using a terminal.
  • Applications: an Azion product that allows you to build applications that run in Azion’s edge network.
  • Object Storage: a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations.

Implementation