Protocols
Deployment Guidelines : 
: Protocols
Protocols
The protocols used by Doradus and Cassandra and their security considerations are summarized below:
• |
Doradus REST API: This is the primary protocol used by applications to update and query objects. Doradus does not provide application-level security features: an application that can successfully connect to Doradus can update and access all objects. However, Doradus allows the REST API to be configured to use TLS (SSL), and it can restrict connections to those that provide a specific client-side certificate. |
• |
Doradus JMX API: Doradus uses the standard Java Management Extensions (JMX) protocol for monitoring and to perform operational functions such as backup and recovery. Though application data is not transferred over the JMX API, access to it can be restricted to prevent unintended operational functions. The JMX API can be secured with authentication and/or TLS. |
• |
Cassandra Thrift API: This is the primary application protocol for Cassandra. Encryption support (TLS) for this protocol was added with the 1.2.0 release, however Doradus does not yet support this. Alternatively, simple user/password-based authorization is available, and Doradus can be configured to use this option. |
• |
Cassandra JMX API: Cassandra also uses the JMX protocol for monitoring and to perform certain operational functions. JMX can be configured to require authorization and/or to encrypt data using TLS. |
• |
Cassandra Gossip API: This is an inter-node communication protocol used by Cassandra to replicate data, coordinate schema changes, and perform other activities. The protocol can be configured to use TLS for encryption, however, because of the high-volume nature of this protocol, encryption is not recommended except for cross-data center communication. |