<p>Problem -> I want to deploy JanusGraph as separate service on Kubernetes. which storage backend should i use for cassandra. Is it CQL or cassandrathrift?? Cassandra is running as stateful service on Kubernetes.</p>

<p>Detailed Description-> As per JanusGraph doc, in case of Remote Server Mode, storage backend should be cql. </p>

<pre><code>JanusGraph graph = JanusGraphFactory.build().
  set("storage.backend", "cql").
  set("storage.hostname", "77.77.77.77").
  open();
</code></pre>

<p>Even they mentioned that Thrift is deprecated going ahead with Cassandra 2.1 &amp; I am using Cassandra 3. 
But in some blog, they have mentioned that rest api call from JanusGraph to Cassandra is possible only through Thrift.   </p>

<p>Is Thrift really required?  Can't we use CQL as storage backend for rest api call as well?</p>

Mudassar Rana
<p>Yes, you absolutely should use the <code>cql</code> storage backend.</p>

<p>Thrift is deprecated, disabled by default in the current version of Cassandra (version 3), and has been removed from Cassandra version 4.</p>

<p>I would also be interested in reading the blog post you referenced.  Are you talking about IBM's Rest API mentioned in their <a href="https://github.com/IBM/janusgraph-utils" rel="nofollow noreferrer">JanusGraph-utils Git repo</a>?  That confuses me as well, because I see both Thrift and CQL config happening there.  In any case, I would go with the <code>cql</code> settings and give it a shot.</p>

<p><strong>tl;dr;</strong></p>

<p>Avoid Thrift at all costs!</p>
