[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-250364-105":53,"doc-detail-250364-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","server-to-data-center-the-tipping-point-scaling-atlassian-applications","Server to Data Center - The Tipping Point - Scaling Atlassian Applications","","Server to Data Center: The Tipping Point explains how to scale Atlassian applications for broader organizational adoption, emphasizing that there is no one-size-fits-all approach. It provides guidance for determining growth, establishing internal governance, and sizing a Jira Software instance based on usage and administrative considerations. The paper also covers scaling patterns such as federated environments and introduces reliability concepts like warm failover to support uptime and performance needs.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/server-to-data-center-the-tipping-point-scaling-atlassian-applications/250364/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/server-to-data-center-the-tipping-point-scaling-atlassian-applications/250364.png","ImageObject",442,249,{"name":88,"@type":89},"WPS_1786070896","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-20","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":15},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"Why isn’t there a single one-size-fits-all method for scaling Atlassian applications?","Question",{"text":108,"@type":109},"Organizations and teams differ in workflows, processes, and needs. Growth characteristics also may not increase at the same rate across factors.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What governance approach helps administrators scale highly customizable applications like Jira Software?",{"text":113,"@type":109},"Administrators can limit the number of configurations made to the application, reducing complexity while supporting scale.",{"name":115,"@type":106,"acceptedAnswer":116},"What does “warm failover” mean in a single server environment?",{"text":117,"@type":109},"Warm failover is an active-passive setup where a standby server with a backup of the main server can be used after a main server failure. It adds assurance but does not eliminate a single point of failure for true high availability.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},250364,1791351560,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":15,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":141},549768072016,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","Atlassian unleashes the potential of every team. Our collaboration software helps teams organize, discuss and complete shared work. Teams at more than 119,000 customers, across large and small organizations—including Citigroup, eBay, Coca-Cola, Visa, BMW and NASA—use Atlassian’s project tracking, content creation and sharing, real-time communication and service management products to work better together and deliver quality results on time. Our products include Jira Software, Confluence, Stride, Trello, Bitbucket, Jira Service Desk and Bamboo.  \nServer to Data Center:  \nThe Tipping Point  \n4 Section I: Scaling Atlassian Applications  \n11 Section II: The Tipping Point  \n17 Section III: What is Data Center?  \n32 Section IV: Prepare, Plan, Execute  \n43 Section V: Refine  \n47 Section VI: Hear It From Our Customers  \n58 Sources and Resources  \nSERVER TO DATA CENTER: THE TIPPING POINT 3  \nSECTION I  \nScaling Atlassian Applications  \nAt some point in your Atlassian journey you’ll likely find yourself needing to scale your Atlassian applications to a wider group in your organization.  \nThis section provides some high-level guidelines for determining growth and creating internal governance before taking the final step in scaling Atlassian: providing true high availability and building a more robust infrastructure to support uptime and performance needs. Keep in mind that there is no ‘one-size-fits-all’ approach to scaling Atlassian applications. Each organization, and team, has different processes, work flows and needs.  \nDetermining Scale  \nWhen considering scaling a single instance of an application like Jira Software, many customers first think about the number of issues their instance can support, ignoring some of the other factors that can contribute to poor performance or increased administration. Below is a list of factors that we recommend considering when scaling a single instance of Jira Software. Keep mind that one characteristic may not grow at the same rate as others. Many people consider the amount of users that will have access to the system, but do not take into account the comparative activity of those users. Or conversely, just because the number of issues is increasing doesn’t mean that projects will too. More information on scaling Jira Software and other Atlassian applications can be found in our Enterprise Documentation.  \nGovernance  \nWith widespread adoption of highly customizable applications, like Jira Software, administrators are often left figuring out how to manage the application. One of the most effective ways to scale products is for administrators to limit the number of configurations made to the application.  \nWe’ve built some sizing guidelines to help you determine how large (or small) your Jira Software instance should be to meet your requirements. Keep in mind that the recommendations foryour company depend on the specific growth type, intensity, and use cases.  \nSECTION I: SCALING ATLASSIAN APPLICATIONS 5  \nSizing Legend  \nSmall-scale  \nMid-scale  \nLarge-scale  \nEnterprisescale  \nApplication usage  \n\n| Users | 100 | 500 | 2000 | 100,000 |\n| --- | --- | --- | --- | --- |\n| Active (Concurrent Users) | 25 | 200 | 600 | 2000 |\n| Issues | 15,000 | 60,000 | 200,000 | 1,000,000 |\n| Issues/month | 200 | 1000 | 4000 | 200,000 |\n| Custom Fields | 50 | 150 | 300 | 600 |\n| Permission Schemes | 3 | 15 | 25 | 100 |\n| Projects | 20 | 80 | 200 | 300 |\n| Parent Issue Types | 10 | 20 | 50 | 160 |\n| Resolutions | 10 | 20 | 30 | 40 |\n| Priorities | 10 | 15 | 25 | 40 |\n| Work flows | 5 | 20 | 35 | 100 |\n| System Level | Small-scale | Mediumscale | Large-scale | Enterprisescale |\n\nMore Jira Software sizing guidelines for things like system requirements can be found in our documentation.  \nSECTION I: SCALING ATLASSIAN APPLICATIONS 6  \nFederating  \nIf you’re running more than one server to support an Atlassian application, let’s say Confluence, then you’re likely running Confluence in a federated environment. Larger custo","cbCaiekuT187H3BN","https://ap.wps.com/l/cbCaiekuT187H3BN","pdf",1666029,62,"English","# Scaling Atlassian Applications\n## Determining Scale\n## Governance\n## Sizing Legend\n## Federating\n## Warm Failover","[{\"question\":\"Why isn’t there a single one-size-fits-all method for scaling Atlassian applications?\",\"answer\":\"Organizations and teams differ in workflows, processes, and needs. Growth characteristics also may not increase at the same rate across factors.\"},{\"question\":\"What governance approach helps administrators scale highly customizable applications like Jira Software?\",\"answer\":\"Administrators can limit the number of configurations made to the application, reducing complexity while supporting scale.\"},{\"question\":\"What does “warm failover” mean in a single server environment?\",\"answer\":\"Warm failover is an active-passive setup where a standby server with a backup of the main server can be used after a main server failure. It adds assurance but does not eliminate a single point of failure for true high availability.\"}]","Server to Data Center - The Tipping Point - Scaling Atlassian Applications | PDF",1789254723,22]