laurencer/indextank-engine — comment on commit 8d8efbf756030ebcb33b2b34e34c0c3868ed5c4a
File:  line 0
By laurencer:

We'll be using the Thrift interface from a Scala service which uses Netty and Akka (thus we don't want to be blocking on any of those threads and we want our architecture to be as asynchronous as possible - it's particularly write heavy).

For now (ie. next few weeks) we'll just be using it as a stand-alone search engine. One of the main motivations was to keep our deployment simple for now (I don't want to have to add Django and the other dependencies to our production environment when we won't really need them for now).

In the future, I'll probably be implementing more of a service layer so we can internally manage instances/scaling. Depending on the direction we take - I'll probably also be looking at making the indexer more distributed if it isn't already (think Akka style - where the indexer can be split into many JVM instances talking to each other). I haven't really looked into this at the current stage.