Re:Slack outage: Connectivity issues affecting all workspaces
by cwyers on Wednesday June 27, 2018 @12:13PM
(#17409358)
That's uptime-as-anecdote. Yes, you can throw your entire IT department at your outage instead of waiting on the vendor to fix it. How many of us work somewhere where the entire IT team is as large as the team that works on Slack's uptime?
Re:Slack outage: Connectivity issues affecting all workspaces
by detaro on Wednesday June 27, 2018 @12:15PM
(#17409373)
How many self-hosted setups need the complexity and matching team size of a centralized service serving millions of users?
Re:Slack outage: Connectivity issues affecting all workspaces
by forgot-my-pw on Wednesday June 27, 2018 @12:50PM
(#17409705)
I remember the netsplits of IRC days...
Re:Slack outage: Connectivity issues affecting all workspaces
by RandallBrown on Wednesday June 27, 2018 @12:21PM
(#17409428)
Let's say the self hosted chat app does go down. Now someone has to fix it. Someone who probably has something better to do. In a cloud hosted solution, the person in charge of fixing your computer doesn't work for you.
My experience with self hosted solutions is that they go down way more often and take longer to fix than cloud solutions.
This all goes back to one basic fact: The Cloud is Someone Else's Computer(tm).
If your hosted Confluence or Jira is down, you can go walk over to your IT team and they'll be like, "Yea we know. We broke something. We're working on it." If you're using a hosted (a.k.a "Cloud" solution), you're just kinda fucked. You can't even extract your data and try to run it locally if it's down (if that's even an option).