News for hackers. Stuff that matters.
Re:Inside the longest Atlassian outage by x0x0 on Wednesday April 13, 2022 @01:13PM (#31017274)
I can't believe anyone would do separate databases.

Just wait until a migration doesn't run on 2 of your 400+ customer databases. Or multi-hour migrations.

Re:Inside the longest Atlassian outage by rectang on Wednesday April 13, 2022 @01:43PM (#31017718)
When all customer data lives in the unified database: Just wait until a bug in a query exposes the data of customers to each other, creating instant regulatory and privacy nightmares for everyone.
Re:Inside the longest Atlassian outage by x0x0 on Wednesday April 13, 2022 @03:05PM (#31018831)
With an orm and customer objects to create scoped queries, I haven't found this to be a problem. It's also very easy to check in code reviews. And not a painful issue from, well, the lack of this happening given it's an extremely common app design.
Re:Inside the longest Atlassian outage by tedunangst on Wednesday April 13, 2022 @04:16PM (#31019716)
Sounds good to me. Now you've got 398 happy customers on the new version, and a small scale issue to resolve with two customers.