Live data from Hacker News

Inside the longest Atlassian outage

newsletter.pragmaticengineer.com

151–160 of 772 posts

Re: Inside the longest Atlassian outage

#151

Earlier quoted context omitted.

I suppose that’s why you don’t combine a tazer and gun into 1 device with 2 triggers.

Instead, you make it with one trigger and a PRNG that decides which gets activated. Just hope you've chosen the right PRNG!!

Considering American police can't even seem to get it right when they have two distinct firearms, and are trained to holster them on specific sides so they know what they are grabbing - and still manage to f*ck it up....this might be an improvement.

Re: Inside the longest Atlassian outage

#152
Something to consider is that Jira can require a great deal of configuration to tailor it to your needs. If you already have a DevOps team of some capacity (not everyone does) then it may only be a small incremental increase to run thinks on prem. I did it myself: I'm ver much not a DevOps person, mostly unfamiliar with optimizing JVM parameters for apps like this, but it still only took me about 5 hours to get things running stable, and then another 2 hours or so a few weeks later to tweak things like heap size to help things go a bit faster (though it was still somewhat slow)

To be complete open though I don't know how much DevOps overhead is involved in maintenance or feature updates. I hated the app and used it for less than a year so I didn't have much exposure. I guess my point though is simply that you may not need to use their SaaS option if you have a decent DevOps team already. After the initial setup time I doubt I spent more than half an hour a month managing the internals and updates.

I did spend more than that on configuring the system for use, which you'll need to do regardless.

Re: Inside the longest Atlassian outage

#153

> Most of them said they won’t leave the Atlassian stack, as long as they don’t lose data. This is because moving is complex and they don’t see a move would mitigate a risk of a cloud provider going down. I still don't understand the strangehold JIRA has on some clients. I can't quickly think of another SaaS product that could be down for almost 2 weeks and not have most customers leave.

A lot of companies have integrations to atlassian suite which might not be easy to shift from. Secondly, there are a lot of individual competitors to Jira, Confluence and Bitbucket but which competitor can offer all three under a single invoice? May be Microsoft, can't think of anyone else. Also for such an extended downtime the customers are entitled to a discount or a credit note which a lot of CXOs consider in the…

We are in a similar place with Slack. We moved from HipChat to Slack and that was painful enough. Then the company noticed we get Teams for "free" and they tried to push us over to it. But folks have so much automation (because "ChatOps" is that new new) that is pushing things into Slack the company eventually gave up.

Re: Inside the longest Atlassian outage

#154

Earlier quoted context omitted.

SLAs aren't real unless there's a contractual consequence for not meeting them. And a couple of percent discount on services for the extra downtime isn't really a meaningful consequence.

I was just thinking that there's a hysteresis function here: the service is worth much more to your team after you've wired your whole process into it than before you joined. Offering you a free month or whatever doesn't acknowledge all the person-hours lost.

There are certainly circumstances where you might have grounds to sue for damages if an SLA is breached. I'm not sure how often this happens but the losses from something like Jira being down could be quite a lot more than anybody pays for it. It's quite likely that defenses against exactly this are written into the contracts you agree to signing up for the service though.

Re: Inside the longest Atlassian outage

#155
post #85

i hate deleting things. prefer flags that hide things instead (like a boolean deleted flag in an rdbms table). prevents data integrity issues in relational databases, makes debugging easier and prevents disasters. ideally also include a timestamp, both for bookkeeping and safe tools that only remove things that have been soft deleted for some time and are safe to delete without compromising integrity of anything that…

Better still: a field that registers at what date a record was supposedly marked as deleted. Because otherwise you still can't bulk recover from an error.

yep. but at least in the rdbms case, and probably in all cases, a flag (and an index on it) tends to be essential for query performance since the state of the flag will appear in most, if not all queries.

that's okay though, queries that reference the timestamp can be slow since they're housekeeping.

Re: Inside the longest Atlassian outage

#156

Something to consider is that Jira can require a great deal of configuration to tailor it to your needs. If you already have a DevOps team of some capacity (not everyone does) then it may only be a small incremental increase to run thinks on prem. I did it myself: I'm ver much not a DevOps person, mostly unfamiliar with optimizing JVM parameters for apps like this, but it still only took me about 5 hours to get thing…

Atlassian has EOL'ed their non-cloud products

https://www.atlassian.com/migration/assess/journey-to-cloud

Re: Inside the longest Atlassian outage

#157

Earlier quoted context omitted.

I would really like to understand who makes the decision to purchase JIRA. It's like the C++ of ticketing software--it does everything because no one wanted to sit down and think critically about the use cases and instead decided it would be easier to say "yes" to every single feature request. It definitely feels like whoever is buying JIRA is not on the team who is using it (maybe IT or finance) because it ticks the…

JIRA is a framework for making assembly lines out of knowledge workers. When you're a middle manager at a decent sized company, a major problem you face is that the mass of knowledge workers beneath you are opaque : you have no way of knowing whether they're working or not. Another problem you face is that they're uppity : people who went to college and got used to managing their own time now have all kinds of idiosy…

Oh, nonsense. People buy Atlassisn because the licensing is cheap, not because it's particularly good at what it does or designed with any particular workflow in mind.

Re: Inside the longest Atlassian outage

#158

Earlier quoted context omitted.

A lot of companies have integrations to atlassian suite which might not be easy to shift from. Secondly, there are a lot of individual competitors to Jira, Confluence and Bitbucket but which competitor can offer all three under a single invoice? May be Microsoft, can't think of anyone else. Also for such an extended downtime the customers are entitled to a discount or a credit note which a lot of CXOs consider in the…

> May be Microsoft, Is there a Jira replacement/offering in the Microsoft 365 suite?

Never used it, but looks like Microsoft Project would fit that box.

Re: Inside the longest Atlassian outage

#159
post #58

Earlier quoted context omitted.

The answer is medium to large companies. Jira is a tool that can satisfy hundreds of different teams’ work management needs without having to buy dozens of different products. The fact that it’s so feature packed and customizable is the point. I think the complainers are not really investing the time in to change project settings to fit their needs. My only complaint about the Atlassian suite is the performance of Ji…

How do you change the markup language to be consistent between Jira and Confluence? How do you eliminate all non-task ticket types in a Jira board and allow any ticket to be a child of any other ticket? It’s hard to configure away complexity from a product if it’s designed to be complicated.

> How do you change the markup language to be consistent between Jira and Confluence?

This here is the single most insane thing about Atlassian.

Re: Inside the longest Atlassian outage

#160

Something to consider is that Jira can require a great deal of configuration to tailor it to your needs. If you already have a DevOps team of some capacity (not everyone does) then it may only be a small incremental increase to run thinks on prem. I did it myself: I'm ver much not a DevOps person, mostly unfamiliar with optimizing JVM parameters for apps like this, but it still only took me about 5 hours to get thing…

Their on-prem options are being reduced down to one product with pretty high minimum spend numbers:

- 500 users (Jira Software, Confluence, Crowd)

- 50 agents (Jira Service Management)

- 25 users (Bitbucket)

https://www.atlassian.com/migration/assess/journey-to-cloud

https://www.atlassian.com/migration/assess/compare-cloud-dat...

Post reply on HN