Nosql is a good idea and in my opinion a Graph database is very good system to e-commerce, because the graph concept is easy to make a recommendation system.
My suggestion is: http://www.hypergraphdb.org/index ( It's a very versatile DB) http://www.orientdb.org/index.htm http://neo4j.org/ ( please read the License model. I think It's have a limitations in the license) If you preferred a Key Value database my suggestion is: RIAK (because it's in Erlang not Java and Riak have a native integration to search engine not only lucene ) regards Joao Martins Em domingo, 22 de julho de 2012 11h08min27s UTC-3, dvbportal escreveu: > > I was going to advise you to use NoSQL. I just finished a basic Node.js > CMS engine and I am happy with it. I wrote it in a few days which I > couldn't have done without the flexibility of NoSQL. The more people you > ask, the more opinions you get. > > I chose a generic database agnostic model to build on. The node.js server > is just providing an API. The rest of the app is implemented on the client > using backbone. > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
