Thanks for sharing.<p>&gt;In the streaming case, documents arrive at a very fast rate (e.g. average of 6000 per second in the case of Twitter) and with this kind of velocity and volume it is impractical to build the inverted document index in real-time.<p>Actually, it&#x27;s completely practical. It&#x27;s expensive, but it can be done. When I was at Loggly we built a big ES cluster, pumped 10,000s log messages into it per second, and served queries. Ingest to query was on the order of seconds - it still runs today. The key, of course, is not to build a single inverted index.<p>I don&#x27;t want to underestimate the work, but it is practical. And expensive.<p><a href="http:&#x2F;&#x2F;www.slideshare.net&#x2F;AmazonWebServices&#x2F;infrastructure-at-scale-apache-kafka-twitter-storm-elastic-search-arc303-aws-reinvent-2013" rel="nofollow">http:&#x2F;&#x2F;www.slideshare.net&#x2F;AmazonWebServices&#x2F;infrastructure-a...</a>