# Jira Service Management Projects: Consolidation Versus Splitting at Scale

DevFeed: [Jira Service Management Projects: Consolidation Versus Splitting at Scale](<https://devfeed.tech/articles/when-atlas-meets-the-hyperscale-34016.md>)

Original publisher: [Read original article](<https://sridharrajarao.com/blog/jsm-projects-atlassian-vs-hyperscalers/>)

Author: Sridhar Rajarao

Published: 2026-07-28T00:00:00Z

Content type: opinion

Language: en

Sources: [Sridhar Rajarao](<https://devfeed.tech/sources/sridhar-rajarao.md>)

Topics: [jira](<https://devfeed.tech/topics/jira.md>), [atlassian](<https://devfeed.tech/topics/atlassian.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [atlassian](<https://devfeed.tech/tags/atlassian.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [coupling](<https://devfeed.tech/tags/coupling.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [jira](<https://devfeed.tech/tags/jira.md>), [jsm](<https://devfeed.tech/tags/jsm.md>), [security](<https://devfeed.tech/tags/security.md>), [sre](<https://devfeed.tech/tags/sre.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

## AI overview

The article compares Atlassian's recommendation to consolidate Jira Service Management work into fewer projects with the multi-project approach used by hyperscalers. It argues that consolidation suits smaller organizations, while separate projects can provide stronger security boundaries, limit configuration blast radius, and preserve team autonomy at scale.

## Source excerpt

Atlassian recommends consolidation. Hyperscalers use many. Both are right for different problems. Five real reasons to split, and what works at each scale.