Atlassian's Solution on AWS

Amazon Web Services

Atlassian's Solution on AWS
Amazon Web Services Amazon Web Services
View Full Case Study
Contact Vendor
Feature New Record
OVERVIEW

At Atlassian, growth is on a fast track. The company adds more customers every day and consequently needed an easy way to scale JIRA, which is growing by 15,000 support tickets every month. The instance supporting this site was previously hosted in a data center, which created challenges for scaling. “The scale at which we were growing made it difficult to quickly add nodes to the application,” says Brad Bressler, technical account manager for Atlassian. “This is our customer-facing instance, which gathers all the support tickets for our products globally. It’s one of the largest JIRA instances in the world, and growing and maintaining it on premises was getting harder to do.” For example, the support.atlassian.com instance was hosted on a single on-premises server, which the company needed to frequently take down for maintenance.

The company also needed to ensure high availability for JIRA. “This is a mission-critical application, and the number of customers potentially impacted by downtime is huge,” says Neal Riley, principal solutions engineer for Atlassian. “As we grew, we became more concerned about the resiliency and disaster-recovery capabilities of the data center.”

To move into a more scalable, highly available environment, Atlassian created JIRA Data Center, a new enterprise version of the application. However, JIRA Data Center required shared storage. “We needed a shared file system so the individual application nodes could have a shared source of truth for profile information, plug-ins, and attachments,” says Riley. 

Atlassian

 

Atlassian also needed to respond to customers wanting to run JIRA on the Amazon Web Services (AWS) Cloud. “We initially looked at several vendors, but AWS was the clear leader,” Bressler says. “We needed automatic scaling and reliability, and AWS offered us that.” The company migrated JIRA Data Center to the AWS Cloud, running all application nodes on Amazon Elastic Compute Cloud (Amazon EC2) instances. Atlassian takes advantage of Auto Scaling groups to enable automatic scaling of both applications, and uses Elastic Load Balancing to redirect application traffic to Amazon EC2 instances for consistent performance.

OPERATIONAL IMPACT

Prior to using Amazon EFS as a shared file system for JIRA Data Center, Atlassian tested the solution internally. During testing, the company discovered the technology was simple to set up and enabled consistent throughput and capacity that stayed within threshold. “Once we went live, everything worked exactly as we expected it to,” says Bressler. “It was performant, resilient, and easy to set up, and it is easy to maintain.”

Because it can more easily manage its JIRA instances in the cloud, Atlassian is putting more effort into enhancing applications. “By moving to the AWS Cloud, our company has been able to focus more on what we do well: providing great services to our customers,” says Bressler. “Instead of having to spend time on managing the back-end application stack, we can really step up our game and better support our tens of thousands of global customers.”

Atlassian is better supporting its customers by utilizing the built-in disaster recovery and high availability of AWS. “We have better disaster-recovery capabilities and better uptime because our application data is replicated across multiple AWS Availability Zones,” says Riley. “If our application instances go down, we’re stopping thousands of people from getting support. By moving to a highly available platform on AWS, we are much more confident that our solutions are available at all times.”


Fatal error: Call to a member function getLabel() on null in /efs/iotone.com/module/Application/view/application/common/IoTSnapshot_view.phtml on line 9