If you want to have an actor per domain object handled by akka-sharding for
read/write and after each write update the indexes affected by that object
for an in-memory map reduce engine
which again one exist per akka-shard node.
That is...very do-able, you can save yourself sometime and use a ma
+1 Ryan.
I understood this is a hobby project, where it might be fun to challange
yourself,
but I wouldn't recommend reinventing search unless "reinventing search" is your
entire business ;-)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Lightbend
On 31 March 2016 at 22:46:41, 'Ryan Tanner' via A
I don't want to rain on anyone's parade, but I think there's a reason that
products like Solr and Elasticsearch are complicated: search is hard!
Getting it right at scale is *really tough*.
Personally, I would gladly trade the operational complexity of ES/Solr over
reimplementing them myself.
