JSON database: Difference between revisions
Appearance
Content deleted Content added
more tidy |
duh |
||
Line 17: | Line 17: | ||
* [[XML database]] |
* [[XML database]] |
||
* [[Nosql]] |
* [[Nosql]] |
||
==Notes and References== |
|||
{{reflist}} |
|||
== External References == |
== External References == |
Revision as of 18:23, 6 January 2010
An editor has nominated this article for deletion. You are welcome to participate in the deletion discussion, which will decide whether or not to retain it. |
A JSON database is a document-oriented database that manages a collection of JSON documents. It is a non-relational database management system. A JSON store provides an object-like representation of data to which today’s widely used Object-oriented programming languages and web services map nicely. At the same time it has the advantage of not being tied to any one language. As with other document-oriented databases, the JSON documents need not all share the same schema. This fits in well with agile programming and dynamically typed languages.
Implementations
- CouchDB: JSON database that exposes a RESTful HTTP API and the ability to define views using different languages.
- MongoDB: Manages collections of documents that are JSON-like and are stored in a binary format called BSON. Supports a rich query language and has a query optimizer.
- Persevere: JSON database and JavaScript Application Server. Provides RESTful JSON interface for Create, read, update, and delete access to data. Also supports JSONQuery/JSONPath querying.[1]
- DBSlayer: Lightweight database abstraction layer that talks to clients via JSON over HTTP used by the New York Times.[2]
See Also
Notes and References
External References
- Kris Zyp, RESTful JSON web databases (slides)