Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,368,490
Community Members
 
Community Events
168
Community Groups

Architect your Atlassian Data Center Application (Jira, Confluence, Bitbucket) in Azure

Hello folks!

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.

Jira data center size profile

Confluence data center size profile

Bitbucket data center size profile

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.

 SmallMediumDatabaseLargexLargeDatabase
JiraD8as_v4 * 2D8as_v4 * 3D2s_v3DS5_v2_Promo * 3DS5_v2_Promo * 4D4s_v3
ConfluenceD8as_v4 * 2D8as_v4 * 3 D2s_v3DS5_v2_Promo * 3DS5_v2_Promo * 4D4s_v3
BitbucketD8as_v4 * 2D8as_v4 * 3D2s_v3DS5_v2_Promo * 4DS5_v2_Promo * 5D4s_v3
Bitbcuket ESD2s_v4 * 1D2s_v4 * 1 D2s_v4 * 2D2s_v4 * 3 
Bitbucket NFSD8as_v4D8as_v4 DS5_v2_PromoDS5_v2_Promo 

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.

Thanks,
Pramodh

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events