>-----Original Message----- >From: Ciancetta, Jesse E. [mailto:[email protected]] >Sent: Friday, October 21, 2011 6:09 AM >To: [email protected] >Subject: RE: Rave to work on top of another application/Rave DB system > >>-----Original Message----- >>From: Jasha Joachimsthal [mailto:[email protected]] >>Sent: Friday, October 21, 2011 3:15 AM >>To: [email protected] >>Subject: Re: Rave to work on top of another application/Rave DB system >> ... >>The default database is H2, but it is possible to replace that with MySQL >>(that's what's documented on the site). There's no specific reason why >>there's no NoSQL support yet. > >We started with JPA and an RDBMS because we assumed it would be the >lowest common denominator for implementers. We assumed pretty much >everyone would already have a RDBMS of some type running in their >datacenter, but weren't sure that would necessarily be true for NoSQL stores. > >We very much want to be able to support NoSQL stores though and have >been trying our best to keep the right extensibility points in the codebase and >the object model clean enough to easily allow for it.
Personally, I would like to look at using a document store (like Mongo) for page & region widget instances and I know others in the community have their own desires for alternative persistence. As Jesse said, we have tried to keep things as simple as extensible as possible, but I expect that we will always be tweaking things to support new use cases.
