184 karma · joined January 2, 2019
https://github.com/elastic/logstash was one of the first modern approaches. I started using it less the more often I ran into JRuby related bugs.
https://github.com/trivago/gollum is my pick from the golang ecosystem.
There are many more variants depending on how much complexity you are trying to apply. If you need to apply machine learning models, for example, you're probably going to end up with something similar to Apache Storm, though I don't know if it's operational story has improved enough to consider it over other alternatives, I lost track years ago between Apache Spark and the half dozen other stream processing projects.
There are viable products around human threat hunting which would be impossible without a 'collect all the data' component.
Also you get tremendously worse translations when you translate a document (pdf, doc) vs the "scan/import" an image of text function.
It's a real bummer because hypertext and mobile UI should be excellent mediums for presenting multiple candidate translations and letting the reader indicate the best translation.
We had a running gag in our social media startup of tweeting "poop" from people who left their phones/computers unlocked ... someone did it to an employee that was logged in as a customer (corporate brand) context and that was the end of that 'joke'.
neither of them solve for CI or pull request workflows themselves, so people try to bridge the gap with Jenkins and now the frankenstein monster comes to life -- now you've got golang, groovy, yaml, none of which your product devs generally have any familiarity with, let alone the idiosyncrasies of terraform state management, cloudformation stacks stuck in ROLLBACK_COMPLETE, yaml whitespace sensitivity, Jenkins scripting sandbox woes, troubleshooting from logs without being able to step through a debugger in an IDE, errors that only happen in eu-west-3, etc, etc...
Clutch looks great!
Don't be a sourpuss because you were exposed to a new meme, that's how echo chambers form.
The only saving grace is that Javascript is willing to throw itself away every couple of years.
Another comment suggested doing queries across so many databases is challenging, and it's just not, we have both adhoc query capabilities across the fleet and a traditional data warehouse...
Now, trying to make additional infrastructure changes is challenging, but the architecture is robust enough to solve all the immediate business needs.
I took my extension down instead, as I didn't have time to figure out how I had painted a target on my back.
I only published my extension as a fork of an open source project that started injecting malware, presumably from a similar offer...