Since you say politics reasons wholly because of this reason, it’s not like Slack is not available if you are not fully remote.
846 karma · joined November 3, 2016
Since you say politics reasons wholly because of this reason, it’s not like Slack is not available if you are not fully remote.
There have been other Gmail outages in the past though. My two favorites are:
1. The multi-hour outage in 2009 http://www.cnn.com/2009/TECH/09/01/gmail.outage/index.html?e.... 2. And one where they had to restore data from magnetic tape backups https://gmail.googleblog.com/2011/02/gmail-back-soon-for-eve....
Of course, there are other email providers too and their own outages. But I like Gmail and that's what I follow.
Lot of people have suggest these problems stem from the culture. Culture of companies and people is similar to the culture of, say, bread. The starter really matters and sets the tone. I'd be interested in hearing from people who have seen a drastic change in culture at a big place or better yet, have been behind that change.
The other idea is it could just be a few rotten apples giving everyone a bad name. I don't know the answer.
All this assumes you have only so much data that can fit in one machine. If that's not the case you're in need of a database that spans more than one machine.
The test is testing the worst-case scenario of everything needing locking. CockroachDB uses an optimistic "locking" approach which makes this bad. But if you're use-case is strictly linearizable high-throughput reads good luck finding anything that is not a single-machine database.
On the topic of looking at Scylla next, I wonder why did the team not just start out with it to begin with. Also, are they people with experience running both. How is the performance? And what is the state of reliability?