Replication with Confluence/JIRA Cloud

[gtirloni]

Both services are extremely slow to users outside our main geographical location (Europe).

Is it possible to have it geo-replicated to other regions so users don't have >30s load times for simple pages?

[Kian Stack Mumo Systems]

Tacking onto what Nick said, data center is also soon to come with support for a content delivery network to more rapidly load static resources. This could also speed up performance for your remote teams.

[gtirloni]

Static assets are not the problem. They are already cached at CloudFront and load very quickly. Sure, Atlassian could group the JS/CSS files into fewer files to avoid concurrent download issues with browsers.

The biggest problem are the requests for dynamic content that go to Atlassian-owned servers and slow everything down. It's a really painful experience. So much that's I'm suggesting alternatives at work. We're expanding globally and this is not sustainable.

[Nic Brough -Adaptavist-]

No, the core Atlassian software itself doesn't have any remote node functions in it (except Bitbucket, but that's doing a very different job to Jira and Confluence).  Cloud, as a managed service, would need to be significantly rebuilt to support it, and it would become a lot more expensive.

You can't do it with Jira or Confluence server either.  The Data Centre version does allow for clustering, but at present, only supports nodes local to each other (in the same building).  Atlassian have said remote nodes are something on the plan, but we don't know when they might arrive.

There is a possible partial solution for Jira though.  If you have two systems one for each region, you can use one of the synchronisation apps to link the projects people need to share.  (I've only really used Exalate and Backbone for sync, and only Backbone for a remote site sync)