Live data from Hacker News

Atlassian moving to cloud-only, will stop selling server licenses

atlassian.com

51–60 of 305 posts

Re: Atlassian moving to cloud-only, will stop selling server licenses

#52
post #21
post #19

Earlier quoted context omitted.

If I was going to switch anyway, I wouldn't switch to Azure DevOps Server, I'd switch to GitHub Enterprise. I don't think there's much of a future for Azure DevOps.

> I don't think there's much of a future for Azure DevOps. This is just... wow. Every Microsoft shop I've ever worked at defaults to Azure. You need a really good reason to use GCP or AWS for anything, and it's an uphill battle. They're already paying licensing fees to Microsoft, there are incentives and discounts to stay within the ecosystem. My current employer has GitHub Enterprise and we still use DevOps for a lo…

I work in a Microsoft shop and we're all in on AWS. Seen a few transition from Azure to AWS also.

Re: Atlassian moving to cloud-only, will stop selling server licenses

#53
post #44

Earlier quoted context omitted.

TFS is the self-hosted predecessor to Azure DevOps and it absolutely sucks compared to JIRA.

How can you be worse than JIRA? Thats almost impressive.

What's wrong with JIRA? If it is about the usage of it within some orgs, I don't know if it is the tool or culture.

I have seen some people fawning over tools like Asana but in my usage I just found it fancier and slower than Jira.

Personally, as a developer I find GitHub issues to be good enough.

Re: Atlassian moving to cloud-only, will stop selling server licenses

#56
post #44

Earlier quoted context omitted.

TFS is the self-hosted predecessor to Azure DevOps and it absolutely sucks compared to JIRA.

How can you be worse than JIRA? Thats almost impressive.

My understanding of Jira is that it by itself does not suck but it bends over backwards for asinine “business processes” so it is difficult to find an implementation in the wild that does not suck.

Re: Atlassian moving to cloud-only, will stop selling server licenses

#58
post #44

Earlier quoted context omitted.

> If I was a Microsoft or another enterprise tech company I’d hire a thousand engineers tomorrow to develop a Jira/Confluence competitor before the grace period for server licenses ends. Azure DevOps Server, née Visual Studio Team System, already exists.

TFS is the self-hosted predecessor to Azure DevOps and it absolutely sucks compared to JIRA.

This disagrees with my experience in both systems, especially if you’re using TFS for your build system, too and Visual Studio for programming. TFS was far better.

Re: Atlassian moving to cloud-only, will stop selling server licenses

#59

This sounds like a terrible move and will probably force all medium-size organizations I work with to ditch Atlassian. We have the technical know-how to administer data center versions of their products, but we can’t do shit if they force potential customers to pay for a minimum of 40 000 USD for a license per product. Many of these orgs have multiple Atlassian products so this will probably end up doubling costs on…

In our case we're ditching our office and that probably means we'll be using the Atlassian cloud instance (since I imagine our server racks will be scrapped eventually), which might be a trend they're seeing altogether.

Re: Atlassian moving to cloud-only, will stop selling server licenses

#60
post #7

We're using Jira, Confluence, and BitBucket on-prem at our DC now, on some pretty sizeable VM's with good network connectivity back to head office. Despite that, it feels very slow. Not the occasional 10+ second page load, where you've accidentally clicked something that happens to generate a cascade of cache misses. I can forgive that kind of infrequent performance hiccup. But rather, regular usage, especially of Co…

Atlassian does not provide particularly good guidance on how to get their tools to perform well. The first big issue for any moderately busy system is that you need to dedicate huge gobs of heap memory (think 16G+) to the tool. After that, they suffer from poor schema design - there are tables that are literally missing indexes on commonly queried columns, and some columns that have delimited values embedded in them.

It's hard for me to imagine that atlassian would allow individual instances of jira/confluence/etc in their cloud versions to get nearly as much resources as you need to give them on-prem. The incentive would always be for them to try to minimize the amount of memory every instance gets, which does NOT maximize your individual performance. Shared resources will also make performance more variable and "noisy", making it more difficult to narrow down specific causes. It's hard for me to see how "Java" and "cloud" go together.

Post reply on HN