Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am designing a high volume web service which will rely on a central database containing objects of a single JSON type. Currently I am considering using ChunkDB to store the objects and retrieve the objects using views (RESTful API). Some of the views may be complex. The amount of data stored in the database will be limited as objects will 'expire'.

Is a sensible approach to the problem? What are the other options?

share|improve this question
Url for ChunkDB? The 4th hit on google for it is this question. Not exactly confidence building. And what is 'high volume' to you? Is there some technical reason you cant or shouldnt use a more traditional database (be it SQL or NoSQL)? – GrandmasterB May 20 '11 at 22:15
up vote 1 down vote accepted

RavenDb is a good candidate -- it is a Json-based document database with a HTTP interface, so you could serve directly out of that application.

You could also look at using something like node.js with whatever backing database you can make work. It scales really, really well by design.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.