How We Unlocked Performance at Scale with Jira Platform

This post details the re-architecture of Jira Cloud, focusing on the creation of the Jira Issue Service (JIS). It describes the challenges of the previous monolithic, single-tenant database architecture and the need for a cloud-native, multi-tenant platform. Key technical details include the design of JIS for massive scale (up to 1 billion issues per tenant), performance targets (under 15ms SLO for reads), reliability goals (99.999% API uptime), and cost efficiency. The architecture utilizes service sharding, multi-level caching, and resilience patterns like bounded retries and circuit breakers. Read operations are optimized via cache lookups and document store queries with support for `minVersion` for read-after-write consistency. Hydration uses the Command Pattern for parallel bulk requests to resolve related entities. Write operations are batched to a document store, with issue documents split into root and sibling nodes to handle size limits. The post also introduces Jira Scalable Issue Search (JSIS) and Jira Authorization Service (JAS) as core components of the new Jira Platform.