Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Embedded or Remote Cassandra Instances are now Supported in Virgil

DZone's Guide to

Embedded or Remote Cassandra Instances are now Supported in Virgil

· Database Zone ·
Free Resource

Running out of memory? Learn how Redis Enterprise enables large dataset analysis with the highest throughput and lowest latency while reducing costs over 75%! 

Since Virgil was originally developed as an embedded REST layer for the Cassandra Server, it ran as a daemon inside the server and performed operations directly against the CassandraServer classes. Running in a single JVM had some performance gains over a separate server that communicated over Thrift (either directly or via Hector) since operations didn't have to take a second hop across the network (with the associated marshalling/unmarshalling)

 

We had a request come in to add the ability to run Virgil against a remote Cassandra:
 

That seemed reasonable since there are a lot of existing cassandra clusters and users may just want to add a REST layer to support webapp/gui access or SOLR integration.

 

To support those cases, we added run-modes to the configuration:
 

Let us know what you think.
 

Running out of memory? Never run out of memory with Redis Enterprise databaseStart your free trial today.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}