I've been successfully running a monitoring application (to gather stats from riak) inside of the riak application for over a year with no issues.
I also know of another company which uses the internal client because of performance issues with the PB client, so its completely possible to run an application inside riak. The only issue I've ever run into was having to bounce riak when my application needs to be updated (which is very infrequent in this case), because I need to bounce riak. For actual client applications of riak I've found a better pattern (even if running on the same machine), is your app pointing to haproxy, haproxy pointing to all the riak nodes. You can configure haproxy to prefer the local connection and only use the others as fall backs. This way you can perform a rolling restart of riak followed by a restart of haproxy, or a restart of your client application, and never have any downtime. -Anthony On Tue, Sep 25, 2012 at 01:56:40PM -0700, Mike Oxford wrote: > I am stacking my application and Riak on the same machine. > It seems wasteful to use 127.0.0.1 or even AF_UNIX sockets. Is there > anything that precludes me from running it directly within the same VM as > Riak, to cut down/eliminate the impedance mismatch/marshalling of going > through the external client protocols like HTTP/Protobuf? > Instead of building on riak_core, I'd be building on Riak(_kv?) itself. > > Here be dragons? > > Thanks! > > -mox > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com -- ------------------------------------------------------------------------ Anthony Molinaro <antho...@alumni.caltech.edu> _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
