Narrowing the Scope of Slack Collections: Stop Trying to Drink From a Firehose

Slack is pumping out data at an inconceivable rate. Trying to collect potentially relevant electronically stored information (ESI) from Slack is like trying to drink from a firehose. There’s too much data coming in and too much of it is entirely irrelevant.

Extract from an article by James Murphy

Slack has only been in use for about five years, but it has exploded in that time. Earlier this year, it hit 8 million daily users, with 3 million of those paying for higher service levels. And it’s not like people are getting on Slack for a minute or two out of their busy day or sending a few isolated messages. A year ago (when Slack only had 6 million daily users), estimates indicated that paying customers were actively engaged in Slack conversations for better than two hours per day. Those users had the application open for a stunning 10 hours a day.

Needless to say, Slack is pumping out data at an inconceivable rate. Trying to collect potentially relevant electronically stored information (ESI) from Slack is like trying to drink from a firehose. There’s too much data coming in and too much of it is entirely irrelevant. Plus, it can be harder than you’d expect to siphon off the trivial side conversations so that you can focus on the important ones.

Additional Reading

Source: ComplexDiscovery

WP-Backgrounds Lite by InoPlugs Web Design and Juwelier Schönmann 1010 Wien
Read previous post:
AWS Announces Amazon DocumentDB (with MongoDB Compatibility)

“To meet developers’ needs, we looked at multiple different approaches to supporting MongoDB workloads and concluded that the best way...

Close