Product Comparisons: JIRA MultiSite

See How JIRA MultiSite Compares to:

Central JIRA Server

• A central JIRA server is effectively a single point of failure and there are no built-in backup and recovery capabilities. When the central JIRA server goes down, or is taken offline for maintenance, there is no user access. This makes 24X7 operation impossible.
• There is no single point of failure in JIRA MultiSite's architecture, and backup and recovery are built in. If one location's JIRA server goes down, or is taken offline for maintenance, users can failover to a JIRA server at another site and continue working with full access to their data. When the server comes back online it recovers automatically from the server(s) at other locations.
• Upgrading the central server's hardware may improve JIRA's performance, but it cannot overcome WAN latency for remote site users. In contrast, JIRA MultiSite leverages WANdisco's unique replication technology to turn a central JIRA server implementation into a distributed solution that balances workload across servers at multiple sites and overcomes WAN latency. As a result, users at every location experience LAN speed performance for both read and write operations.

Back to Top

Partitioning

• A central JIRA server implementation can be partitioned into separate JIRA servers at each location to overcome WAN latency and performance issues. However, there is no integration between the JIRA servers at each location to enable a global view of projects and issues, or allow distributed teams to collaborate.
• With Partitioning, each location's JIRA server can become a single point of failure, and there are no built-in backup and recovery capabilities.
• There is no single point of failure in JIRA MultiSite's architecture, and backup and recovery are built in. If one location's JIRA server goes down, or is taken offline for maintenance, users can failover to a JIRA server at another location and continue working with full access to their data. When the server comes back online it recovers automatically from the server(s) at other the other site(s).

Back to Top