What happens when your Rocket Chat instance goes down though? At least with Slack there's a dedicated team of engineers working to restore service. With something self hosted, you have to handle...
What happens when your Rocket Chat instance goes down though? At least with Slack there's a dedicated team of engineers working to restore service. With something self hosted, you have to handle those situations yourself. Self-hosted, non-proprietary solutions are magically immune to service disruptions.
Yeah, there are two separate metrics here. Objectively measured downtime (which is nonzero for both "cloud" and self-hosted solutions), and a sense of control. People feel out of control when...
Yeah, there are two separate metrics here. Objectively measured downtime (which is nonzero for both "cloud" and self-hosted solutions), and a sense of control.
People feel out of control when their "cloud" hosted solution goes down for two hours. When your internally hosted chat goes down for two hours, at least you have the comforting sense that your own people are working to solve it. Although, whoever's stuck trying to recover your internally hosted chat is probably falling behind on their regularly scheduled work as a result...
Eh, I have more confidence in the dedicated team of Slack engineers, whose careers are specifically dedicated to fixing this issue, than I do in my company's IT department which is juggling any...
Eh, I have more confidence in the dedicated team of Slack engineers, whose careers are specifically dedicated to fixing this issue, than I do in my company's IT department which is juggling any number of unrelated concerns and has no specialized knowledge about the chat system. If either's going to give me a "comforting sense," it's the company I pay to do a single thing well.
Not sure if this is appropriate for ~comp, but I figured this is a tool most people here probably use, especially if they work in the industry. Even enterprise is down, my team is pretty sour...
Not sure if this is appropriate for ~comp, but I figured this is a tool most people here probably use, especially if they work in the industry. Even enterprise is down, my team is pretty sour right now
Yeesh, same. You'd think they'd have better redundancy and disaster recovery automation being a medium that can be heavily utilized for ops automation.
Yeesh, same. You'd think they'd have better redundancy and disaster recovery automation being a medium that can be heavily utilized for ops automation.
What happens when your Rocket Chat instance goes down though? At least with Slack there's a dedicated team of engineers working to restore service. With something self hosted, you have to handle those situations yourself. Self-hosted, non-proprietary solutions are magically immune to service disruptions.
Yeah, there are two separate metrics here. Objectively measured downtime (which is nonzero for both "cloud" and self-hosted solutions), and a sense of control.
People feel out of control when their "cloud" hosted solution goes down for two hours. When your internally hosted chat goes down for two hours, at least you have the comforting sense that your own people are working to solve it. Although, whoever's stuck trying to recover your internally hosted chat is probably falling behind on their regularly scheduled work as a result...
Eh, I have more confidence in the dedicated team of Slack engineers, whose careers are specifically dedicated to fixing this issue, than I do in my company's IT department which is juggling any number of unrelated concerns and has no specialized knowledge about the chat system. If either's going to give me a "comforting sense," it's the company I pay to do a single thing well.
We just moved from self-hosted Atlassian Hipchat to Slack about two months ago. This feels like punishment.
Not sure if this is appropriate for ~comp, but I figured this is a tool most people here probably use, especially if they work in the industry. Even enterprise is down, my team is pretty sour right now
Thanks for the heads up! Seems it's been down for a couple of hours now and they're still investigating the issue.
Yeesh, same. You'd think they'd have better redundancy and disaster recovery automation being a medium that can be heavily utilized for ops automation.