5 ms·
Will Slack actually outdo your in house solution though? If you have a service (Slack alternative or otherwise) locally hosted, you're cutting out a whole bunc
by boardwaalk 5y ago
Will Slack actually outdo your in house solution though?
If you have a service (Slack alternative or otherwise) locally hosted, you're cutting out a whole bunch of failure modes:
1. Upgrades/maintenance at inopportune times (you can control this, or not even upgrade at all if you don't need it)
2. Networking issues, if you can colocate with with upstream or downstream dependencies
3. Many scaling issues (disk fills up, etc) since you're only serving your own needs and you're not trying to put as many users in as little capacity as possible
4. Relatedly, abusive use by other users won't effect you.
5. You can keep the service off the public internet and avoid things like DDOS attacks
It's nice to do able to blame someone else, I get, but that seems kind of gross, and actually being able to provide the best service overall is what I'd go for.
- Hamuko 5y agoAnd how many failure modes are you introducing? If your service is off the public Internet, you now have a failure mode where the company VPN going down kills all productivity. And if you're going to have issues with a disk getting filled up, that's most likely going to happen with an on-premise solution than with a hosted solution where they have a team to take care that the disks don't "fill up". And not keeping your software updated because "an update would happen at an inappropriate time and we don't need it" sounds like a good vulnerability vector.
- iso1631 5y ago4 or 5 slack outages in the last 12 months. Happy to do the update at a quiet time (say 3pm on a wednesday before we go to the pub), but wouldn't do it during a major event (say the middle of the world cup final when we're monitoring things very closely)