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?
Bloggers continue to discuss Twitter and Foursquare deprecating XML.
dbcrawler for returning POJO objects from the underlying schema of a database.
JAX-WS RI 2.2.1 is now available. With this release, wsgen can now generate inline schema in a generated wsdl using […]
Apache Xerces-J version 2.10.0 is now available. This version introduces experimental support for the XML Schema 1.1 Structures and Datatypes […]
Version 2.0 of HyperSQLDB (HyperSQL DataBase) is now available. HSQLDB is a SQL relational database engine. It features in-memory and […]
Riak 0.11 is out now. With this release, Basho’s key/value store ‘Bitcask’ is used as the default backend for Riak, […]
The source code for the PsychoPath XPath 2.x processor is now available on github. This is a snapshot of the […]
OrientDB is a new NOSQL DBMS, which is written in Java and manages its relationships with direct connections among records. […]
Milestone 6 of the PsychoPath XPath 2.0 processor is now available. The open source PsychoPath XPath processor is a Java-based, […]
A new Db4o plugin for enabling access to database functionality using the open source object database engine db4o, is now […]