BSON: Difference between revisions
Removed IPA pronunciation; There's many ways to pronounce it, and no official one |
|||
(7 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
{{Short description|Computer data interchange format}} |
{{Short description|Computer data interchange format}} |
||
{{Infobox file format |
{{Infobox file format |
||
| screenshot = BSON website logo.svg |
|||
| name = BSON |
| name = BSON |
||
|_nomimecode = on |
|_nomimecode = on |
||
Line 7: | Line 8: | ||
| genre = Data interchange |
| genre = Data interchange |
||
| extended from = [[JSON]] |
| extended from = [[JSON]] |
||
| url = {{URL| |
| url = {{URL|https://bsonspec.org/}} |
||
}} |
}} |
||
'''BSON''' is a [[computer]] data interchange format. The name "BSON" is based on the term [[JSON]] and stands for "Binary JSON".<ref |
'''BSON''' ({{IPAc-en|ˈ|b|iː|s|ə|n}}<ref name="bsonspec-org">{{cite web |title=BSON (Binary JSON) Serialization |url=https://bsonspec.org/ |access-date=23 November 2021}}</ref>) is a [[computer]] data interchange format. The name "BSON" is based on the term [[JSON]] and stands for "Binary JSON".<ref name="bsonspec-org" /> It is a binary form for representing simple or complex [[data structure]]s including [[associative array]]s (also known as name-value pairs), integer indexed arrays, and a suite of fundamental scalar types. |
||
BSON originated in 2009 at [[MongoDB]]. Several scalar data types are of specific interest to MongoDB and the format is used both as a data storage and network transfer format for the MongoDB database, but it can be used independently outside of MongoDB. |
BSON originated in 2009 at [[MongoDB]]. Several scalar data types are of specific interest to MongoDB and the format is used both as a data storage and network transfer format for the MongoDB database, but it can be used independently outside of MongoDB. |
||
Implementations are available in a variety of languages such as [[C (programming language)|C]], [[C++]], [[C Sharp (programming language)|C#]], [[D (programming language)|D]], [[Delphi (IDE)|Delphi]], [[Erlang (programming language)|Erlang]], [[Go (programming language)|Go]], [[Haskell (programming language)|Haskell]], [[Java (programming language)|Java]], [[JavaScript]], [[Julia (programming language)|Julia]], [[Lua (programming language)|Lua]], [[OCaml]], [[Perl]], [[PHP]], [[Python (programming language)|Python]], [[Ruby (programming language)|Ruby]], [[Rust (programming language)|Rust]], [[Scala (programming language)|Scala]], [[Smalltalk]], and [[Swift (programming language)|Swift]].<ref>{{cite web |url= |
Implementations are available in a variety of languages such as [[C (programming language)|C]], [[C++]], [[C Sharp (programming language)|C#]], [[D (programming language)|D]], [[Delphi (IDE)|Delphi]], [[Erlang (programming language)|Erlang]], [[Go (programming language)|Go]], [[Haskell (programming language)|Haskell]], [[Java (programming language)|Java]], [[JavaScript]], [[Julia (programming language)|Julia]], [[Lua (programming language)|Lua]], [[OCaml]], [[Perl]], [[PHP]], [[Python (programming language)|Python]], [[Ruby (programming language)|Ruby]], [[Rust (programming language)|Rust]], [[Scala (programming language)|Scala]], [[Smalltalk]], and [[Swift (programming language)|Swift]].<ref>{{cite web |url=https://bsonspec.org/implementations.html |title=BSON Implementation Projects |access-date=2021-11-24 }}</ref> |
||
==Data types and syntax== |
==Data types and syntax== |
||
BSON has a published specification.<ref>{{Cite web|url= |
BSON has a published specification.<ref>{{Cite web|url=https://bsonspec.org/spec.html|title=BSON (Binary JSON): Specification|website=bsonspec.org|access-date=2021-11-24}}</ref><ref>{{Cite web|url=https://www.informit.com/articles/article.aspx?p=2247310&seqNum=4%20api.mongodb.com/python/current/api/bson/regex.html|title=Introducing NoSQL and MongoDB {{!}} What Is NoSQL? {{!}} InformIT|website=www.informit.com|access-date=2018-01-17}}</ref> The topmost element in the structure must be of type BSON object and |
||
contains 1 or more elements, where an element consists of a field name, a type, and a value. Field names are strings. Types include: |
contains 1 or more elements, where an element consists of a field name, a type, and a value. Field names are strings. Types include: |
||
Line 21: | Line 22: | ||
* 32 bit integer |
* 32 bit integer |
||
* 64 bit integer |
* 64 bit integer |
||
* double (64-bit [[IEEE 754]] floating point number) |
* [[Double-precision floating-point format|double]] (64-bit [[IEEE 754]] floating point number) |
||
* decimal128 (128-bit [[IEEE 754-2008]] floating point number; Binary Integer Decimal (BID) variant), suitable as a carrier for decimal-place sensitive financial data and arbitrary precision numerics with 34 decimal digits of precision, a max value of approximately 10<sup>6145</sup> |
* [[decimal128 floating-point format|decimal128]] (128-bit [[IEEE 754-2008]] floating point number; [[Binary integer decimal|Binary Integer Decimal]] (BID) variant), suitable as a carrier for decimal-place sensitive financial data and arbitrary precision numerics with 34 decimal digits of precision, a max value of approximately 10<sup>6145</sup> |
||
* datetime w/o time zone (long integer number of milliseconds since the [[Unix epoch]]) |
* datetime w/o time zone (long integer number of milliseconds since the [[Unix epoch]]) |
||
* byte array (for arbitrary binary data) |
* byte array (for arbitrary binary data) |
||
Line 31: | Line 32: | ||
* JavaScript code |
* JavaScript code |
||
* [[MD5]] binary data |
* [[MD5]] binary data |
||
* [[Regular expression]] ([[Perl]] compatible regular expressions ("[[PCRE]]") version 8.41 with UTF-8 support)<ref>{{Cite web|url=https://api.mongodb.com/python/current/api/bson/regex.html|title=regex – Tools for representing MongoDB regular expressions — PyMongo 3.6.0 documentation|website=api.mongodb.com|access-date=2018-01-17}}</ref> |
* [[Regular expression]] ([[Perl]] compatible regular expressions ("[[PCRE]]") version 8.41 with UTF-8 support)<ref>{{Cite web|url=https://api.mongodb.com/python/current/api/bson/regex.html|title=regex – Tools for representing MongoDB regular expressions — PyMongo 3.6.0 documentation|website=api.mongodb.com|access-date=2018-01-17|archive-date=2016-05-10|archive-url=https://web.archive.org/web/20160510224657/https://api.mongodb.com/python/current/api/bson/regex.html|url-status=dead}}</ref> |
||
An important differentiator to [[JSON]] is that BSON contains types not present in JSON (e.g. datetime and byte array) and offers type-strict handling for several numeric types instead of a universal "number" type. For situations where these additional types need to be represented in a textual way, MongoDB's Extended JSON format<ref>{{Cite web|url=https://docs.mongodb.com/manual/reference/mongodb-extended-json/|title=MongoDB Extended JSON documentation|website=docs.mongodb.com|access-date=2020-05-03}}</ref> can be used. |
An important differentiator to [[JSON]] is that BSON contains types not present in JSON (e.g. datetime and byte array) and offers type-strict handling for several numeric types instead of a universal "number" type. For situations where these additional types need to be represented in a textual way, MongoDB's Extended JSON format<ref>{{Cite web|url=https://docs.mongodb.com/manual/reference/mongodb-extended-json/|title=MongoDB Extended JSON documentation|website=docs.mongodb.com|access-date=2020-05-03}}</ref> can be used. |
||
==Efficiency== |
==Efficiency== |
||
Compared to JSON, BSON is designed to be efficient both in storage space and scan-speed. Large elements in a BSON document are prefixed with a length field to facilitate scanning. In some cases, BSON will use more space than JSON due to the length prefixes and explicit array indices.<ref name="bsonspec"/> |
Compared to JSON, BSON is designed to be efficient both in storage space and scan-speed. Large elements in a BSON document are prefixed with a length field to facilitate scanning. In some cases, BSON will use more space than JSON due to the length prefixes and explicit array indices.<ref name="bsonspec-org"/> |
||
== Example == |
== Example == |
||
A document such as {"hello":"world"} will be stored as: |
A document such as {{code|{"hello": "world"} }} will be stored as: |
||
<pre> |
|||
<syntaxhighlight lang="c"> |
|||
\x16\x00\x00\x00 // total document size |
|||
⚫ | |||
Bson: |
|||
hello\x00 // field name |
|||
⚫ | |||
⚫ | |||
\x00 // 0x00 = type EOO ('end of object') |
|||
</pre> |
|||
⚫ | |||
\x00 // 0x00 = type EOO ('end of object') |
|||
</syntaxhighlight> |
|||
== See also == |
== See also == |
||
Line 57: | Line 56: | ||
* [[Smile_(data_interchange_format)|Smile]] (binary JSON) |
* [[Smile_(data_interchange_format)|Smile]] (binary JSON) |
||
* [[UBJSON]] |
* [[UBJSON]] |
||
* [[Protocol Buffers]] |
|||
* [[Action Message Format]] |
|||
* [[Apache Thrift]] |
|||
* [[MessagePack]] |
|||
* [[Document-oriented database]] |
|||
** [[MongoDB]] |
|||
* [[Abstract Syntax Notation One]] (ASN.1) |
|||
* [[Wireless Binary XML]] (WBXML) |
|||
* [[Efficient XML Interchange]] |
|||
==References== |
==References== |
||
Line 71: | Line 61: | ||
== External links == |
== External links == |
||
* |
* {{Official website|https://bsonspec.org/}} |
||
* [ |
* [https://docs.mongodb.com/database-tools/bsondump/ {{mono|bsondump}} tool included with MongoDB] |
||
* [http://docs.mongodb.org/manual/reference/bsondump/ <tt>bsondump</tt> tool included with MongoDB] |
|||
{{Data Exchange}} |
{{Data Exchange}} |
Latest revision as of 09:43, 29 November 2023
Filename extension |
.bson |
---|---|
Internet media type | application/bson [1] |
Type of format | Data interchange |
Extended from | JSON |
Website | bsonspec |
BSON (/ˈbiːsən/[2]) is a computer data interchange format. The name "BSON" is based on the term JSON and stands for "Binary JSON".[2] It is a binary form for representing simple or complex data structures including associative arrays (also known as name-value pairs), integer indexed arrays, and a suite of fundamental scalar types. BSON originated in 2009 at MongoDB. Several scalar data types are of specific interest to MongoDB and the format is used both as a data storage and network transfer format for the MongoDB database, but it can be used independently outside of MongoDB. Implementations are available in a variety of languages such as C, C++, C#, D, Delphi, Erlang, Go, Haskell, Java, JavaScript, Julia, Lua, OCaml, Perl, PHP, Python, Ruby, Rust, Scala, Smalltalk, and Swift.[3]
Data types and syntax[edit]
BSON has a published specification.[4][5] The topmost element in the structure must be of type BSON object and contains 1 or more elements, where an element consists of a field name, a type, and a value. Field names are strings. Types include:
- Unicode string (using the UTF-8 encoding)
- 32 bit integer
- 64 bit integer
- double (64-bit IEEE 754 floating point number)
- decimal128 (128-bit IEEE 754-2008 floating point number; Binary Integer Decimal (BID) variant), suitable as a carrier for decimal-place sensitive financial data and arbitrary precision numerics with 34 decimal digits of precision, a max value of approximately 106145
- datetime w/o time zone (long integer number of milliseconds since the Unix epoch)
- byte array (for arbitrary binary data)
- boolean (
true
andfalse
) - null
- BSON object
- BSON array
- JavaScript code
- MD5 binary data
- Regular expression (Perl compatible regular expressions ("PCRE") version 8.41 with UTF-8 support)[6]
An important differentiator to JSON is that BSON contains types not present in JSON (e.g. datetime and byte array) and offers type-strict handling for several numeric types instead of a universal "number" type. For situations where these additional types need to be represented in a textual way, MongoDB's Extended JSON format[7] can be used.
Efficiency[edit]
Compared to JSON, BSON is designed to be efficient both in storage space and scan-speed. Large elements in a BSON document are prefixed with a length field to facilitate scanning. In some cases, BSON will use more space than JSON due to the length prefixes and explicit array indices.[2]
Example[edit]
A document such as {"hello": "world"}
will be stored as:
\x16\x00\x00\x00 // total document size \x02 // 0x02 = type String hello\x00 // field name \x06\x00\x00\x00world\x00 // field value (size of value, value, null terminator) \x00 // 0x00 = type EOO ('end of object')
See also[edit]
- Comparison of data serialization formats
- JSON
- CBOR
- Smile (binary JSON)
- UBJSON
References[edit]
- ^ "BSON Support in ASP.NET Web API 2.1 - ASP.NET 4.x". Microsoft Docs. 2014-01-20. Retrieved 2010-01-12.
- ^ a b c "BSON (Binary JSON) Serialization". Retrieved 23 November 2021.
- ^ "BSON Implementation Projects". Retrieved 2021-11-24.
- ^ "BSON (Binary JSON): Specification". bsonspec.org. Retrieved 2021-11-24.
- ^ "Introducing NoSQL and MongoDB | What Is NoSQL? | InformIT". www.informit.com. Retrieved 2018-01-17.
- ^ "regex – Tools for representing MongoDB regular expressions — PyMongo 3.6.0 documentation". api.mongodb.com. Archived from the original on 2016-05-10. Retrieved 2018-01-17.
- ^ "MongoDB Extended JSON documentation". docs.mongodb.com. Retrieved 2020-05-03.