JSON database: Difference between revisions
Content deleted Content added
different Persevere |
more tidy |
||
| Line 6: | Line 6: | ||
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 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. |
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 == |
== Implementations == |
||
* [[CouchDB]]: JSON database that exposes a [[RESTful]] HTTP API and the ability to define views using different languages |
* [[CouchDB]]: JSON database that exposes a [[RESTful]] HTTP API and the ability to define views using different languages. |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
* DBSlayer: Lightweight database abstraction layer that talks to clients via JSON over HTTP used by the [[New York Times]].<ref>http://code.nytimes.com/projects/dbslayer</ref> |
* DBSlayer: Lightweight database abstraction layer that talks to clients via JSON over HTTP used by the [[New York Times]].<ref>http://code.nytimes.com/projects/dbslayer</ref> |
||
| Line 21: | Line 17: | ||
* [[XML database]] |
* [[XML database]] |
||
* [[Nosql]] |
* [[Nosql]] |
||
== External References == |
== External References == |
||
| ⚫ | |||
http://persvr.org/ |
|||
| ⚫ | |||
Revision as of 18:22, 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
External References
- Kris Zyp, RESTful JSON web databases (slides)