Sean Owen wrote:
Yeah it should be easy and fine to separate the EJB, web service
clients further. Beyond that I think it's mostly driven by what we
want to achieve, and it sounds like that is Hadoop-ifying it
basically.
So far, I was always thinking of mahout as a backend process. it would
produce a file (or two), and that would be sucked up into SOLR or mysql
(or whatever) that the webapp would make use of. Obviously this is a
PITA as you would introduce a delay in how long it took before a event
gets fed back into the system.
Mainly because we (our developers) know how to scale solr and mysql very
easily, and making a hadoop cluster into a OLTP thing is completely new
to us, and I was thinking it was not really designed for 10-30ms
response times.
Or am I misjudging HDFS? could you run a webserver farm serving lots of
static files on top of HDFS?
--Ian
