I fully agree, but our business need was to stream log files (e.g. tail -f) and to search for snippets in them and to produce statistic counters (e.g. |grep|wc)

While I can imagine situations where ElasticSearch is the best solution, I have seen it mostly used in situations that would be better served with simple command-line tools, similar to what the author demonstrated with awk vs. Hadoop.

> ElasticSearch also does a lot more than your CLI does.

This is not necessarily a good thing. In fact, it is probably a really bad thing if you do not need the additional stuff.