Learn about Atlassian Data Center

Data Center products are designed for enterprise organizations that need Atlassian products to perform well at scale, with minimum downtime for their users Unlike Server products, Data Center products can be set up in a multi-node environment, which has a number of benefits :

  • reduced application downtime and uninterrupted user access to Atlassian products
  • consistent performance as you scale
  • scaling options that fit complex infrastructures

Configuration overview

One of the key differences between Data Center and Server environments is the number of Atlassian application nodes that you can configure in a supported setup.

Server

If your single application node fails, your Atlassian application becomes unavailable to users.


Reverse proxy

A reverse proxy sits in front of an application and directs incoming traffic to it. 

For example, you can use a reverse proxy to provide an easy to remember URL without a port number (that is, port forwarding), such as  https://jira.myCompany.com instead of  http://192.168.1.100:8080/

Atlassian application node

An Atlassian product installed on a single node. The application home directory lives on this node as well.


Data Center

If one node in the application cluster fails, your Atlassian application is still available to users.


Load balancer cluster

Multiple load balancers distribute requests from users to Atlassian application nodes. If a cluster node goes down, the load balancer immediately detects the failure and automatically directs requests to the other nodes.

Atlassian application cluster

An Atlassian application cluster consists of multiple Atlassian application nodes that are configured to use the same database and file system. Failure of a node causes no loss of availability for users, because requests are immediately directed to other nodes. All nodes are active and process requests.

File system & database  

A file system stores a shared home directory that is writable by the Atlassian application cluster. 

By implementing failover strategies, you can reduce the risk of your database or file system becoming a single point of failure.



Glossary

Here's a list of terms and definitions that you might find useful.

Term Description
Node

A node is a single physical or virtual entity.

Examples:

  • a virtual machine (VM)
  • a server
  • a load balancer
Cluster

More than one physical or virtual machine doing the same thing, it can be two or more nodes working together. All elements of a cluster need to have the same purpose. 

Examples:

  • Atlassian application cluster
  • load balancers cluster
Users All people using computers that have access to your network.
Application home directory The directory where an Atlassian application stores its configuration information and other operational data like page attachments.
File system

Stores a shared home directory that is writable by an Atlassian application. Data Center supports any shared file system, which stores:

  • import/export files
  • plugins
  • Logos directory
  • shared caches
  • any data directory which includes attachments, avatars, and icons


What's next?

Read How to set up Data Center if you're ready to get started with Atlassian Data Center. Our product documentation will guide you through the installation steps.


Good to know




Last modified on Jan 22, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.