The rise of NoSQL is characterized with confusion and ambiguity; very much like any fast-emerging organic movement in the absence of well-defined standards and adequate software solutions. Whether you are a developer or an architect, many questions come to mind when faced with the decision of where your data should be stored and how it should be managed. What does the rise of all these NoSQL technologies mean to my enterprise? What is NoSQL to begin with? Does it mean “No SQL”? Could this be just another fad? Is it a good idea to bet the future of my enterprise on these new exotic technologies and simply abandon proven mature Relational DataBase Management Systems (RDBMS)? How scalable is scalable? Assuming that I am sold, how do I choose the one that fit my needs best?
Developing and running JPA code in diverse OSGi environments.
The SimpleDS persistence framework for Google App Engine reaches 1.0 and gets JRebel support.
Bug fixes for EclipseLink 2.1, including fixes for collection Properties and XMLStreamWriterRecord.
Maintenance release for Apache OpenJPA Java persistence project.
SimpleDS for App Engine version 1.0 RC1 is now available. SimpleDS is an open source framework for persistence in AppEngine. […]
Apache OpenJPA version 2.0.0 is now available. This distribution is a fully compliant implementation of the Java Persistence API, version […]
Craig Russell is a senior staff engineer at Sun Microsystems. He is specification lead for Java Data Objects (JSR 12 and 243) and leads the implementation team for its reference implementation and technology compatibility kit. In this interview we asked him about the new JPA 2.0 version, about persistence in general and the future of O/R mapping.