Atlassian Jamstack App

Overview

The article discusses the use of Jamstack architecture with Atlassian ecosystem to achieve performance, scalability, and developer productivity. It explains the differences between Jamstack-based Connect apps and Forge apps, and how they interact with the CDN and backends through Ajax calls.

Features

• Performance, scalability, and developer productivity achieved through static frontends and distributed backends.
• Easy migration between Atlassian Connect and Atlassian Forge platform.
• Jamstack-based Connect apps fetch resources from CDN and invoke backends via Ajax calls.
• Forge apps are deployed into Atlassian infrastructure, eliminating the need for developers to provide their own CDN or SaaS infrastructure.
• Common APIs abstract away platform-specific integration points, allowing app’s business logic to remain unaffected.

Installation

To install the theme, follow these steps:

1. Clone the repository using git clone <repository-url>.
2. Change to the project directory using cd <project-directory>.
3. Install the required dependencies using npm install.
4. Configure the webpack config file in the respective apps to inject Connect- or Forge-specific implementations.
5. Run the app using npm start or yarn start.

Summary

The article discusses the use of Jamstack architecture with Atlassian ecosystem, specifically Atlassian Connect and Atlassian Forge platform. It explains how Jamstack-based apps fetch resources from CDN and interact with backends through Ajax calls. The article also highlights the benefits of using Forge apps in Atlassian infrastructure, eliminating the need for developers to provide their own CDN or SaaS infrastructure. Overall, the article provides insights into leveraging Jamstack architecture in the Atlassian ecosystem for improved performance and scalability.