Removing *QL from application code is not really an indicator of the maturity of a technology. ORMs and automatic type mapping in general tend to be very easy things for a developer to work with allowing for rapid prototypes, but those applications are often ill-suited to being deployed is high-volume environments.
I have used a wide variety of ORMs over the last 15 years, hibernate being a favourite at which I am held to have some expertise, but when I am creating an app for the real world in situations where I can expect several million requests/day, I do not touch them. On Tue, Jul 22, 2014 at 5:10 PM, Jake Luciani <jak...@gmail.com> wrote: > Checkout datastax devcenter which is a GUI datamodelling tool for cql3 > > http://www.datastax.com/what-we-offer/products-services/devcenter > > > On Sun, Jul 20, 2014 at 7:17 PM, jcllings <jclli...@gmail.com> wrote: >> >> So I'm a Java application developer and I'm trying to find entry points >> for learning to work with Cassandra. >> I just finished reading "Cassandra: The Definitive Guide" which seems >> pretty out of date and while very informative as to the technology that >> Cassandra uses, was not very helpful from the perspective of an >> application developer. >> >> Having said that, what Java clients should I be looking at? Are there >> any reasonably mature PoJo mapping techs for Cassandra analogous to >> Hibernate? I can't say that I'm looking forward to yet another *QL >> variant but I guess CQL is going to be a necessity. What, if any, GUI >> tools are available for working with Cassandra, for data modelling? >> >> Jim C. >> > > > > -- > http://twitter.com/tjake -- - michael dykman - mdyk...@gmail.com May the Source be with you.
