3 ms·
Incidents like these help remind people that their data isn't necessarily safe just because it's in the cloud.
by justin_oaks 5y ago
Incidents like these help remind people that their data isn't necessarily safe just because it's in the cloud.
- smackeyacky 5y agoThis seems strange though. Surely the Atlassian people, being funded with a bonkers amount of money and being able to afford the best people, have a decent setup wherever their cloud installs are. With a lot of the AWS stuff (for example) you have to go out of your way to screw it up. Unless they aren't leaning on S3 / AuroraDB / managed services and doing everything on VMs. Surely not though, nobody does that any more, right?
- mdoms 5y agoI haven't worked at Atlassian in a a few years but when I was there Jira and Confluence cloud ran a Postgres DB per tenant in huge ECS instances (hundreds of DBs per VM). No managed databases. I can't imagine this has changed.
- smackeyacky 5y agoUm...yuck! It's no surprise they are having trouble with restores then. I can't imagine what it's like to try to manage something like that.
- mdoms 5y agoYeah there were a lot of home grown tools for managing it, and some self-made async migration infrastructure built into the Jira code base.
- smackeyacky 5y agoTheir own worst enemy then. I didn't figure Atlassian as a NIH shop but that story is scary.
- pleb_nz 5y agoSurely you jest
- pleb_nz 5y agoA lot of cloud providers say somewhere it's your responsibility to backup your cloud data. I doubt very many people do. I used to work for a business that was fairly strict about updatng everything in office 365, all mail, files etc.