Skip to content

SYSTEM Cited by 1 source

Atlassian Unleash PWA

Atlassian Unleash PWA is a React/TypeScript event application built for Atlassian Unleash 2026. It uses static hosting and a global CDN for the browser shell, Jira Cloud as the workflow-shaped system of record, Jira Automation for scheduled/control-plane work, and a thin stateless service for operations that cannot safely originate in the browser. The design deliberately minimizes custom stateful infrastructure while making client-side convergence and offline intent durable.

Architecture

  • Static PWA + CDN: serves the application shell; all authenticated calls traverse the Atlassian platform edge for routing, session management, and API-gateway responsibilities.
  • Jira Cloud: stores sessions, speakers, booths, registrations, attendee state, XP events, leaderboard rows, announcements, and push subscriptions as structured issues/fields.
  • Jira Automation: recomputes leaderboard totals, finds upcoming sessions, triggers reminder flows, and transitions workflow state.
  • Thin stateless service: performs bot-authenticated writes, notification signing, and traffic-spike smoothing. It has no business state or database.
  • Product surfaces: Rovo Chat grounded in Confluence backs the event guide; Loom embeds recordings; Rovo Dev, Bitbucket, and Bitbucket Pipelines form the live feature-delivery loop.

Consistency model

Provisioning and permission propagation are eventually consistent, so the client follows the eventual-readiness state-machine pattern. It renders safe local/bundled data, persists actions through a durable client outbox, and keeps a settled optimistic overlay until an authoritative Jira read confirms the operation. This is the named-system instance of patterns/durable-client-outbox-with-settled-overlay.

XP events are the write model; leaderboard rows are a derived materialized view. Jira Automation supports near-real-time updates, periodic incremental recomputation, and a full rebuild, making scores repairable from the source events instead of treating display rows as truth.

Performance results

The team reported 24 to 16 page-load API calls and 8 to 0 duplicate calls after sharing in-flight promises; add-to-schedule calls fell from 11 to 5 after selective revalidation. A build configuration fix reduced JavaScript from approximately 7.7 MB to 1.53 MB, and local/bundled render plus background revalidation reduced time to first useful content from roughly 12 seconds to under one second. Returning users skip idempotent provisioning after an access check, saving about five seconds. (Source: sources/2026-08-07-atlassian-building-a-real-time-pwa-on-atlassians-own-stack)

Seen in

Last updated · 620 distilled / 1,953 read