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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
As one of many I'm looking for possible options in terms for possible cloud migration. OFC natural criteria is license cost. But I'd like to share with community some research which I did as part of preparation to choose one of options which we (users/admins) need to take. This is really non case specific as each admin will need to check his must have apps on each environment. Here is more generic set of data to have overview about app coverage.
Yes, I'm aware of:
- differences between environments (ignored as not part of that exercise)
- not all apps are equally important for users
- I'm ignoring app popularity in that exercise
Goal of that exercise was more general to get overview on whole picture.
What I was looking for is information about amount of all addons (including duplicates) for each environment per category.
Main question will be how many apps is available for each env?
|% of server||100%||40%||59%|
Next to that I checked coverage - what is percentage relation to Server (most mature env.)
Next question which I was trying to answer was: How many apps within each category is available. Knowing that I calculated coverage eg. within category Workflow Server has 361 apps while Cloud 228 - that gives 63% coverage of Server.
Based on above calculation I checked how many within each category is matching XX% level of Server ...
|more than 50% of server||3%||70%|
|more than 60% of server||0%||57%|
|more than 70% of server||0%||27%|
|more than 80% of server||0%||19%|
What above mean for me?
To get real outcome I will check all my used apps for each application and will check is it available on DC/Cloud. Also I'll verify cost of each of those options. But it's little worrying, knowing that DC can provide 40% possibilities of Server same for Cloud (59%).
Hi @Kat yes, you're right. Those environments (DC/Cloud) and it's apps are different. As this was only part of greather research on the path to move further I'm looking into more detailed usage on next steps but this in case speciffic.
Interesting comparison @m93 ! Given your conclusion,
"But it’s little worrying, knowing that DC can provide 40% possibilities of Server same for Cloud (59%)."
I have some thoughts to share:
On top of all that, I recently looked at a batch of apps in the Atlassian Labs space to see if any might need attention during our next ShipIt. I found that out of quite a few Server-only apps, most wouldn't apply to Cloud. They either had Server-specific problems they were solving (example: Atlassian Support Tools plugin which uploads a support zip from your server when you open a support case - doesn't apply to Cloud) or addressed features that are Cloud-native (Jira Automation, Slack integration, some Jira and Confluence workflow/page templates, Confluence analytics, etc). It's really not an apples-to-apples comparison to look at the raw numbers.
Hi @Daniel Eads
Thanks for reply. Fully agree, I just started reasearch to get raw overview on maturity between those env's. Naturally Server is mature due to long time focus. Do you know about any comparission/test in which admins like me could get some idea about "how jira will work in cloud?" Case which I think is often is that mid-size company is considering Atlassian cloud as more mature env. One of those mature elements can me CDN, access speed. Following such instancies can be
100/1000 users locaded world wide (Local/Azure AD authentication)
100/1000 custom fields
How can look like performace? I terms of access, average page load time? There is on Atlassian KB page stating that instance will be spinned up in US and then after (unknown) some time moved to location where most users is located. For simplicity letls assume that most users are in US (40% of user base). What user experience will have user located in Taiwan (20% of user base), Germany (30%of user base), Turkey (10% of user base)? Mostlikely it was not tested but it's worth to ask.