We’ve talked a lot about Atlassian Data Center– who it’s for, why to upgrade, and how to migrate your Atlassian tools for greater flexibility, scalability, and reliability.
We also recently published a whitepaper: The Considerations for Scaling Your Atlassian Environment to share the key indicators that it might be time for your organization to uplevel its infrastructure, the key benefits of using Data Center to host your Atlassian tools, and more.
However, we know that sometimes it takes hearing about others’ experiences to truly help you pull the trigger for your own business. So today, we’ve compiled a group of Atlassian customer testimonials to share with you.
We hope these stories will help you make the decision as to whether or not it’s time for you to upgrade. And as always, if you need a guiding hand to answer some of the tough questions that come along with a migration, Coyote Creek is happy to help you.
So let’s jump right in.
Atlassian Customer Testimonial #1: Amadeus
Our first story is from Amadeus. Amadeus is a global travel technology company. Their solutions cover sales, marketing, operations & business management and help to improve the travel & traveler experience.
Amadeus uses Atlassian tools to support operations for over 5000+ employees worldwide. With a team that large, spanning all over the world, Amadeus can’t afford downtime or inefficiency. Therefore, moving to Data Center was a must to provide 24/7 access without the risk of outages or compromised performance.
Click here to read Amadus’s Strategies for implementing Atlassian at an Enterprise Scale.
Atlassian Customer Testimonial #2: Cerner
Cerner is an American supplier of health IT services, devices, and other hardware. As of 2018, Certner products were being used in more than 27,000 facilities around the world.
Cerner was utilizing three federated instances of JIRA Software with 10,000+ team members accessing each instance at all hours of the day, around the globe. However, this arrangement was unmanageable long term and they quickly began to see downtime issues and performance degradation.
To ensure the high-availability they needed, they upgraded from Atlassian Server to Data Center so that they could cluster multiple active servers and provide unfettered access to JIRA Software users.
Additionally, while utilizing Zabbix and Splunk to monitor their JIRA instances, Cerner identified that REST API abuse was also an issue inhibiting access to high-availability. Users were using the REST API to get real-time status updates which greatly taxed the service.
Not wanting to restrict users’ creativity, but knowing they needed to find another way, Cerner decided to isolate their REST calls to a single server within a multi-node Data Center infrastructure. This allowed them to intelligently distribute traffic and find the best of both worlds.
This new arrangement also guaranteed that all external requests went to this dedicated node as opposed to having users manually change the domain to an IP address, which was less reliable.
How Cerner Transitioned to Data Center
To ensure that all external REST API requests were routed away from other traffic, Cerner introduced four nodes into their cluster, with a load balancer and each node performing the following services:
- Node 1 – External REST API node
- Nodes 2 & 3 – Normal usage nodes
- Node 4 – Admin and power user node- only accessible by IP address
Originally, they had planned to use the load balancer to route all requests with ‘/rest’ to the REST API node. But after some testing, they found the REST API was also being used throughout JIRA Software, so that meant they’d still be mixing REST API traffic with normal usage.
Instead, working with an Atlassian partner, they found that they could isolate REST API requests by looking for ‘/rest’ in each request AND by looking at where the request originated using the HTTP referer header.
If a user was attempting to login to JIRA Software or was already using it, they would get directed to or remain on a “Normal Usage” node. However, if they were requesting the REST API, they’d be directed to the specific node dedicated to the REST calls.
After making this chance, Cerner began seeing 4X the amount of traffic on the REST API node compared to the other nodes. This reduced response time, decreased CPU utilization across the non-admin nodes, and they haven’t seen a single unplanned outage since the switch.
Download the full Cerner Case Study.
Atlassian Customer Testimonial #3: Mitchell International
Mitchell International harnesses smart technology to deliver solutions that simplify claims handling and repair processes, driving more accurate, consistent, and cost-effective resolutions for their customers.
They began using Confluence to enable content collaboration, and as word of the initial team’s success spread, Confluence adoption began to spread throughout other areas of the organization.
Eventually, Mitchell International realized they needed a way to scale to meet the growth in Confluence usage. That’s when they decided to go all-in and fully invest in Confluence Data Center to support their entire organization and provide reliable, scalable access to their mission-critical tools.
Click here to read more about Mitchell International’s full story.
Atlassian Customer Testimonial #4: The Novomatic Group
The NOVOMATIC Group is one of the largest gaming technology companies in the world with a turnover of around EUR 2.3 billion in 2016, and locations in 45 countries that export high-tech gaming equipment to more than 70 countries.
With many subsidiaries, and each operating and managing their own Atlassian tools separately, there was an extensive lack of visibility and standardization within the organization as a whole. Realizing how decentralized they were, they knew they needed a way to standardize operations and tools.
For their Atlassian solutions, they decided to create a single user base across all of their subsidiaries along with a single sign-on experience for every Atlassian user. With the added level of complexity due to distributed teams, the NOVOMATIC Group needed to ensure they could give the appropriate level of access to each team without hindering collaboration.
They determined that Crowd would be the best solution to centralize user management for all of their Atlassian products. So they worked with an Atlassian Solutions Partner to set up a central Crowd instance along with three Crowd instances for their subsidiaries.
They integrated Crowd with several Jira Software, Confluence, Bitbucket, Fisheye, and Crucible instances and established one single user base that synced with each of these four Crowd instances to provide a single source of truth.
After completing this project, they quickly realized that Crowd, along with their other integrated Atlassian tools, had become critical to their users’ day to day operations. In fact, downtime of a Crowd instance could mean hindered access to other Atlassian tools as well.
Thus, the NOVOMATIC Group engaged their partner to investigate how they might be able to introduce high availability to their Crowd instances. The answer? Crowd Data Center.
How The NOVOMATIC Group Transitioned to Data Center
With the help of their solutions partner, The NOVOMATIC Group evaluated the prerequisites and considerations to make sure that they were a good candidate for Crowd Data Center Beta.
In less than two months, they were able to set up and test Crowd Data Center in a staging environment. After completing the installation and finding no issues, they completed a full roll-out of the Crowd Data Center beta version into production.
Since then, The NOVOMATIC Group has not experienced any unscheduled downtime. In addition to an overwhelming reduction in outages, all upgrades and changes can now be rolled into a single, scheduled outage as opposed to multiple instances of downtime.
Download the full NOVOMATIC Case Study.
Atlassian Customer Testimonial #5: Splunk
Our last story is from Splunk. Splunk produces software that helps other businesses search, monitor, and analyze machine-generated big data in order to target the right prospects and generate more revenue.
They rely heavily on Confluence Data Center to manage several components of their engineering process including internal team and project websites, automated release note generation, project standard operating procedures, and other documents.
Splunk also integrates Confluence with the rest of their Atlassian tools, including JIRA and HipChat, to more efficiently produce world-class software with a robust, end-to-end tech stack.
Learn more about how Splunk Scaled with Atlassian by watching their “Too big to fail: scaling systems the smart way at Splunk” webinar.
Scaling with Data Center
If you’re considering an Atlassian Data Center migration, we strongly encourage you to check out our latest whitepaper.
In addition, if you need a guiding hand to help you plan, execute, and optimize a Data Center migration, Coyote Creek can provide proactive and strategic guidance that will enable you to get the most out of your Atlassian investment.
We are also experienced with Atlassian Cloud and Server as well as hybrid environments like AWS and Azure.
Our senior IT consultants can help you to identify issues within your existing environment during a pre-migration audit and help you correct these issues to optimize your new Atlassian Data Center environment.
To learn more about how we can work closely with you to assist with your installation and configuration, contact us today.