Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can the DataStax Java Driver (Cassandra) be safely used in EE servers? #2

Open
arjantijms opened this issue Aug 7, 2017 · 0 comments

Comments

@arjantijms
Copy link
Collaborator

Hi everyone,

I saw that there is an example of integration with Cassandra using the DataStax driver but I wonder if in a production environment the presented approach can be valid.

From what I could see from code example of javaee7-samples and the answers in the group-list of DataStax Java Driver (https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user) my findings until the moment are:

The driver does not hurt the EJB specification and can use it within an EJB normally;
Although not hurt the EJB specification, there is no official API/standardized/widely used in which the Java EE Server can manage connections of a Cassandra cluster;
Can I create a Cluster/Session objects within a javax.ejb.Singleton to facilitate the implementation of the four rules for using Cassandra driver (http://www.datastax.com/dev/blog/4-simple-rules-when-using-the-datastax-drivers-for-cassandra);
Could take advantage of some features of EJB as concurrency control and dependency injection with CDI, however, other features like transaction management lose all sense;
I am currently seeking this information because I am doing a small application to learn Cassandra, and I'll try this javaee7-sample approach.

But the question remains that: In a production environment, you see this attempt at integration as something plausible?

Migrated from: javaee-samples/javaee7-samples#323

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant