Embedded or Remote Cassandra Instances are now Supported in Virgil
DZone's Guide to
Embedded or Remote Cassandra Instances are now Supported in Virgil
Join the DZone community and get the full member experience.
Join For FreeRead the 2019 State of Database DevOps Report for the very latest insights
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.
Read the 2019 State of Database DevOps Report for latest insights into DevOps adoption among SQL Server professionals, and the benefits and challenges of including the database in DevOps initiatives
Like This Article? Read More From DZone
Topics:
Published at DZone with permission of Brian O' Neill , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}