For the sake of argument... why do you think you should embed Cassandra? I'll be honest with you, making Cassandra restart every time you want to upgrade your daemon sounds like a horrible idea.
Run your 10 DB instances on their own and save yourself the operational headache. On Tue, Jan 26, 2016 at 11:35 AM Richard L. Burton III <mrbur...@gmail.com> wrote: > I'm certain you're going to get a lot of users on this mailing list > telling you that's a bad idea. You should read up on Cassandra via datastax > website to understand how Cassandra is designed and works. > > There's tools for monitoring and more. > > On Tue, Jan 26, 2016 at 2:31 PM, Enrico Olivelli <eolive...@gmail.com> > wrote: > >> Hi, >> I' new to Cassandra. I'm evaluating to launch Cassandra daemon inside the >> JVM of my program. This is essentially because I want the lifecycle of >> Cassandra to be managed by my daemon. >> My program can be launched on several machines (in the order of max 10 >> instances) and every instance collaborate with others in a peer to peer, >> fully decentralized way. Cassandra seems to be the best java db which can >> be useful for my purpose. >> >> Is there any experience of Cassandra embedded in production systems ? >> >> Regards >> Enrico Olivelli >> > > > > -- > -Richard L. Burton III > @rburton >
