Wednesday, March 31, 2010

More on Cassandra

I've spent the past little while playing more with the Cassandra database or key store. I've learned a bunch of new things.

I've got Cassandra setup on two dedicated servers and a third server to act as the web server. After a little bit of initial configuration issues, I've got both servers up and running in their own cluster.

Want the simplest piece of advice to get it up and running? Read the README. Best guide that there is.

It's interesting, from what I've seen so far, there are no user accounts to be created for accessing the database. This made me wonder initially how to secure the database from other people accessing it and manipulating the data maliciously. But I believe I figured out how to do this.

The nice thing, is you can setup the interface that Cassandra binds on. This pretty much leaves two different methods for securing Cassandra:

1. Setup the web server to run on the same box as Cassandra. This way, you can tell Cassandra to bind to localhost or 127.0.0.1, and it would therefore ignore all other requests.

2. Setup Cassandra to be bound to it's actual network address, but have the box Cassandra (and the cluster) is on in a location on the network that is not accessible on the outside. This way, the web server on the inside can hit Cassandra, but nothing from the outside will be able to.

More to come, but I'm interested in seeing where this goes so far.

No comments:

Post a Comment