You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
To the member of organizations who are still running their Atlassian applications on the server, we are on the side of the bridge, and if we need to sail the boat with confidence either towards the cloud or data center, we have to have a strategy, migration plan in place.
Let's look briefly at how we start with the Data center journey!
Before you start with even installing the test environment, let's discuss the aspects that have to be covered.
Outline architecture and infrastructure options
Best to start with Atlassian guide here
Start with establishing how big your instance is currently. It might be Small, Medium, Large, or XLarge. Please follow the guidelines for Jira Confluence and Bitbucket size profiles.
Following the recommendation here from Atlassian for AWS here
Performance depends on a number of factors such as third-party apps, large repositories, data, traffic, concurrency, customizations, or instance type.
Atlassian recommends having first tested this on your test environment and see how the results are, then proceed into production.
Make sure you provision sufficient and dedicated resources (vCPU and Memory) to the Atlassian application you are running.
You have the option to set up a Data center either in a non-clustered environment or clustered environment.
Based on Atlassian's laid out recommendations, please follow the guide to choose which environment is right for you here
I've outlined similar instance size profiles for Azure well, which will get you started with building infrastructure without any doubts.
|Jira||D8as_v4 * 2||D8as_v4 * 3||D2s_v3||DS5_v2_Promo * 3||DS5_v2_Promo * 4||D4s_v3|
|Confluence||D8as_v4 * 2||D8as_v4 * 3||D2s_v3||DS5_v2_Promo * 3||DS5_v2_Promo * 4||D4s_v3|
|Bitbucket||D8as_v4 * 2||D8as_v4 * 3||D2s_v3||DS5_v2_Promo * 4||DS5_v2_Promo * 5||D4s_v3|
|Bitbcuket ES||D2s_v4 * 1||D2s_v4 * 1||D2s_v4 * 2||D2s_v4 * 3|
When you consider these recommendations, please dig see the test details to see what the throughput was for the recommended instance configuration.
Test details are here
It might give you extra data to make an informed decision between the best-performing and the most cost-effective option.
To analyze the node sizing please follow the documentation here
Over time, Atlassian may change recommendations depending on new tests, insights, or improvements in Data Center. Please keep an eye out for the latest updates through Atlassian blogs, Partners they are working with!
Please let me know what are your thoughts on the article, and if you are managing an enterprise environment, what are your recommendations in the comment section.