Jump to content

MongoDB

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Renewal6 (talk | contribs) at 20:45, 4 October 2023 (Reverted edits by Jingsukan Japan (talk) (AV)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

MongoDB
Developer(s)MongoDB Inc.
Initial releaseFebruary 11, 2009; 15 years ago (2009-02-11)[1]
Stable release
7.0.5[2] Edit this on Wikidata / 5 January 2024，9 months ago
Repository
Written inC++, JavaScript, Python
Operating systemWindows Vista and later, Linux, OS X 10.7 and later, Solaris,[3] FreeBSD[4]
Available inEnglish
TypeDocument-oriented database
LicenseServer Side Public License or proprietary
Websitemongodb.com

MongoDB is a source-available cross-platform document-oriented database program. Classified as a NoSQL database program, MongoDB uses JSON-like documents with optional schemas. MongoDB is developed by MongoDB Inc. and current versions are licensed under the Server Side Public License (SSPL) which is considered non-free by some organizations and distributions. MongoDB is a member of the MACH Alliance.

History

See also: MongoDB Inc. § History

The US software company 10gen began developing MongoDB in 2007 as a component of a planned platform as a service product.

In 2009, the company shifted to an open-source development model, with the company offering commercial support and other services.

In 2013, 10gen changed its name to MongoDB Inc.[5]

On October 20, 2017, MongoDB became a publicly traded company, listed on NASDAQ as MDB with an IPO price of $24 per share.[6]

On November 8, 2018 with the stable release 4.0.4 the software's license changed from AGPL 3.0 to SSPL.[7][8]

On October 30, 2019, MongoDB teamed up with Alibaba Cloud, who will offer its customers a MongoDB-as-a-service solution. Customers can use the managed offering from BABA's global data centers.[9]

MongoDB release history
Version Release date Feature notes Refs
1.0 August 2009 [10]
1.2 December 2009
  • more indexes per collection
  • faster index creation
  • map/reduce
  • stored JavaScript functions
  • configurable fsync time
  • several small features and fixes
 [11]
1.4 March 2010 [12]
1.6 August 2010
  • production-ready sharding
  • replica sets
  • support for IPv6
 [13]
1.8 March 2011 [14]
2.0 September 2011 [15]
2.2 August 2012 [16]
2.4 March 2013
  • enhanced geospatial support
  • switch to V8 JavaScript engine
  • security enhancements
  • text search (beta)
  • hashed index
 [17]
2.6 April 8, 2014
  • aggregation enhancements
  • text-search integration
  • query-engine improvements
  • new write-operation protocol
  • security enhancements
 [18]
3.0 March 3, 2015
  • WiredTiger storage engine support
  • pluggable storage engine API
  • SCRAM-SHA-1 authentication
  • improved explain functionality
  • MongoDB Ops Manager
 [19]
3.2 December 8, 2015
  • WiredTiger storage engine by default
  • replication election enhancements
  • config servers as replica sets
  • readConcern
  • document validations
  • moved from V8 to SpiderMonkey
 [20]
3.4 November 29, 2016
  • linearizable read concerns
  • views
  • collation
 [21]
3.6 November 2017 [22]
4.0 June 2018
  • transactions
  • license change effective pr. 4.0.4
 [23]
4.2 August 2019 [24]
4.4 July 2020 [25]
4.4.5 April 2021 [26]
4.4.6 May 2021 [27]
5.0 July 13, 2021
  • future-proofs versioned API
  • client-side field level encryption
  • live resharding
  • time series support
 [28][29][30]
6.0 July 2022 [31]
7.0 August, 15 2023 [32]

Main features

Ad-hoc queries

MongoDB supports field, range query, and regular-expression searches.[33] Queries can return specific fields of documents and also include user-defined JavaScript functions. Queries can also be configured to return a random sample of results of a given size.

Indexing

Fields in a MongoDB document can be indexed with primary and secondary indices or index.

Replication

MongoDB provides high availability with replica sets.[34] A replica set consists of two or more copies of the data. Each replica-set member may act in the role of primary or secondary replica at any time. All writes and reads are done on the primary replica by default. Secondary replicas maintain a copy of the data of the primary using built-in replication. When a primary replica fails, the replica set automatically conducts an election process to determine which secondary should become the primary. Secondaries can optionally serve read operations, but that data is only eventually consistent by default.

If the replicated MongoDB deployment only has a single secondary member, a separate daemon called an arbiter must be added to the set. It has a single responsibility, which is to resolve the election of the new primary.[35] As a consequence, an idealized distributed MongoDB deployment requires at least three separate servers, even in the case of just one primary and one secondary.[35]

Load balancing

MongoDB scales horizontally using sharding.[36] The user chooses a shard key, which determines how the data in a collection will be distributed. The data is split into ranges (based on the shard key) and distributed across multiple shards. (A shard is a master with one or more replicas.) Alternatively, the shard key can be hashed to map to a shard–enabling an even data distribution.

MongoDB can run over multiple servers, balancing the load or duplicating data to keep the system up and running in case of hardware failure.

File storage

MongoDB can be used as a file system, called GridFS, with load balancing and data replication features over multiple machines for storing files.

This function, called grid file system,[37] is included with MongoDB drivers. MongoDB exposes functions for file manipulation and content to developers. GridFS can be accessed using mongofiles utility or plugins for Nginx[38] and lighttpd.[39] GridFS divides a file into parts, or chunks, and stores each of those chunks as a separate document.[40]

Aggregation

MongoDB provides three ways to perform aggregation: the aggregation pipeline, the map-reduce function, and single-purpose aggregation methods.[41]

Map-reduce can be used for batch processing of data and aggregation operations. But according to MongoDB's documentation, the Aggregation Pipeline provides better performance for most aggregation operations.[42]

The aggregation framework enables users to obtain the kind of results for which the SQL GROUP BY clause is used. Aggregation operators can be strung together to form a pipeline – analogous to Unix pipes. The aggregation framework includes the $lookup operator which can join documents from multiple collections, as well as statistical operators such as standard deviation.

Server-side JavaScript execution

JavaScript can be used in queries, aggregation functions (such as MapReduce), and sent directly to the database to be executed.

Capped collections

MongoDB supports fixed-size collections called capped collections. This type of collection maintains insertion order and, once the specified size has been reached, behaves like a circular queue.

Transactions

MongoDB claims to support multi-document ACID transactions since the 4.0 release in June 2018.[43] This claim was found to not be true as MongoDB violates snapshot isolation.[44]

Editions

MongoDB Community Server

The MongoDB Community Edition is free and available for Windows, Linux, and macOS.[45]

MongoDB Enterprise Server

MongoDB Enterprise Server is the commercial edition of MongoDB and is available as part of the MongoDB Enterprise Advanced subscription.[46]

MongoDB Atlas

MongoDB is also available as an on-demand fully managed service. MongoDB Atlas runs on AWS, Microsoft Azure, and Google Cloud Platform.[47]

On March 10, 2022, MongoDB warned its users in Russia and Belarus that their data stored on the MongoDB Atlas platform will be destroyed due to U.S. sanctions over the War in Ukraine.[48]

Architecture

Programming language accessibility

MongoDB has official drivers for major programming languages and development environments.[49] There are also a large number of unofficial or community-supported drivers for other programming languages and frameworks.

Serverless access

Management and graphical front-ends

Record insertion in MongoDB with Robomongo 0.8.5

The primary interface to the database has been the mongo shell. Since MongoDB 3.2, MongoDB Compass is introduced as the native GUI. There are products and third-party projects that offer user interfaces for administration and data viewing.[50]

Licensing

MongoDB Community Server

As of October 2018, MongoDB is released under the Server Side Public License (SSPL), a non-free license developed by the project. It replaces the GNU Affero General Public License, and is nearly identical to the GNU General Public License version 3, but requires that those making the software publicly available as part of a "service" must make the service's entire source code (insofar that a user would be able to recreate the service themselves) available under this license. By contrast, the AGPL only requires the source code of the licensed software to be provided to users when the software is conveyed over a network.[51][52] The SSPL was submitted for certification to the Open Source Initiative but later withdrawn.[53] In January 2021, the Open Source Initiative stated that SSPL is not an open source license.[54] The language drivers are available under an Apache License. In addition, MongoDB Inc. offers proprietary licenses for MongoDB. The last versions licensed as AGPL version 3 are 4.0.3 (stable) and 4.1.4.

MongoDB has been removed from the Debian, Fedora and Red Hat Enterprise Linux distributions due to the licensing change. Fedora determined that the SSPL version 1 is not a free software license because it is "intentionally crafted to be aggressively discriminatory" towards commercial users.[55][56]

Bug reports and criticisms

Security

Due to the default security configuration of MongoDB, allowing anyone to have full access to the database, data from tens of thousands of MongoDB installations has been stolen. Furthermore, many MongoDB servers have been held for ransom.[57][58]

In September 2017; updated January 2018, in an official response Davi Ottenheimer, lead Product Security at MongoDB, proclaimed that measures have been taken by MongoDB to defend against these risks.[59]

From the MongoDB 2.6 release onwards, the binaries from the official MongoDB RPM and DEB packages bind to localhost by default. From MongoDB 3.6, this default behavior was extended to all MongoDB packages across all platforms. As a result, all networked connections to the database will be denied unless explicitly configured by an administrator.[60]

Technical criticisms

In some failure scenarios where an application can access two distinct MongoDB processes, but these processes cannot access each other, it is possible for MongoDB to return stale reads. In this scenario it is also possible for MongoDB to roll back writes that have been acknowledged.[61] The issue was addressed since version 3.4.0 released in November 2016[62] (and back-ported to v3.2.12).[63]

Before version 2.2, locks were implemented on a per-server process basis. With version 2.2, locks were implemented at the database level.[64] Since version 3.0,[65] pluggable storage engines were introduced, and each storage engine may implement locks differently.[65] With MongoDB 3.0 locks are implemented at the collection level for the MMAPv1 storage engine,[66] while the WiredTiger storage engine uses an optimistic concurrency protocol that effectively provides document-level locking.[67] Even with versions prior to 3.0, one approach to increase concurrency is to use sharding.[68] In some situations, reads and writes will yield their locks. If MongoDB predicts a page is unlikely to be in memory, operations will yield their lock while the pages load. The use of lock yielding expanded greatly in 2.2.[69]

Up until version 3.3.11, MongoDB could not do collation-based sorting and was limited to byte-wise comparison via memcmp which would not provide correct ordering for many non-English languages when used with a Unicode encoding. The issue was fixed on August 23, 2016.

Prior to MongoDB 4.0, queries against an index were not atomic. Documents which were being updated while the query was running could be missed.[70] The introduction of the snapshot read concern in MongoDB 4.0 eliminated this phenomenon.[71]

In an undated article entitled "MongoDB and Jepsen" (archived May 8, 2020),[72] MongoDB said that version 3.6.4 had passed "the industry's toughest data safety, correctness, and consistency tests" by Jepsen, and that, "MongoDB offers among the strongest data consistency, correctness, and safety guarantees of any database available today." On April 30, Jepsen, which describes itself as a "distributed systems safety research company", disputed both claims on Twitter, saying, "In that report, MongoDB lost data and violated causal by default." In its May 15 report on MongoDB version 4.2.6, Jepsen wrote that MongoDB had only mentioned tests that version 3.6.4 had passed, and that version had 4.2.6 introduced more problems.[73] Jepsen's test summary reads in part:

Jepsen evaluated MongoDB version 4.2.6, and found that even at the strongest levels of read and write concern, it failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations. Weak defaults meant that transactions could lose writes and allow dirty reads, even downgrading requested safety levels at the database and collection level. Moreover, the snapshot read concern did not guarantee snapshot unless paired with write concern majority—even for read-only transactions. These design choices complicate the safe use of MongoDB transactions.[74]

On May 26, Jepsen updated the report to say, "MongoDB identified a bug in the transaction retry mechanism which they believe was responsible for the anomalies observed in this report; a patch is scheduled for 4.2.8."[74] As of June 10, 2023, the "MongoDB and Jepsen" page said the issue had been patched as of that version, and that, "Jepsen criticisms of the default write concerns have also been addressed, with the default write concern now elevated to the majority concern (w:majority) from MongoDB 5.0."[75]

MongoDB Conference

MongoDB Inc. hosts an annual developer conference which has been referred to as either MongoDB World or MongoDB.live.[76]

Year Dates City Venue Notes
2014 [77] June 23–25 New York Sheraton Times Square Hotel
2015 [78] June 1–2 New York Sheraton Times Square Hotel
2016 [79] June 28–29 New York New York Hilton Midtown
2017 [80] June 20–21 Chicago Hyatt Regency Chicago First year not in New York City
2018 [81] June 26–27 New York New York Hilton Midtown
2019 [82] June 17–19 New York New York Hilton Midtown
2020 [83] May 4–6 Online In‑person event cancelled and conference held entirely online due to the COVID-19 pandemic
2021 [84] July 13–14 Online Conference held online due to the COVID-19 pandemic
2022 [85] June 7–9 New York Javitz Center

See also

References

  1. ^ "State of MongoDB March, 2010". DB-Engines. Archived from the original on September 18, 2017. Retrieved July 5, 2017.
  2. ^ "Release Notes for MongoDB 7.0.5".
  3. ^ "How to Set Up a MongoDB NoSQL Cluster Using Oracle Solaris Zones". Oracle. Archived from the original on August 12, 2017. Retrieved July 5, 2017.
  4. ^ "How-To: MongoDB on FreeBSD 10.x". FreeBSD News. Archived from the original on December 28, 2017. Retrieved July 5, 2017.
  5. ^ "10gen embraces what it created, becomes MongoDB Inc". Gigaom. Archived from the original on March 5, 2016. Retrieved January 29, 2016.
  6. ^ Witkowski, Wallace (October 21, 2017). "MongoDB shares rally 34% in first day of trading above elevated IPO price". MarketWatch. Dow Jones. Archived from the original on February 26, 2018. Retrieved February 26, 2018.
  7. ^ "4.0 Changelog - 4.0.4 Changelog - Build and Packaging". Retrieved June 28, 2023.
  8. ^ "Release Notes for MongoDB 4.0 - 4.0.4 - Nov 8, 2018". Retrieved June 28, 2023.
  9. ^ Betz, Brandy (October 30, 2019). "MongoDB teams with Alibaba Cloud". Seeking Alpha. Retrieved October 31, 2019.
  10. ^ "1.0 GA Released | MongoDB Blog". MongoDB. Retrieved May 19, 2022.
  11. ^ "Release Notes for MongoDB 1.2.x". mongodb.com.
  12. ^ "Release Notes for MongoDB 1.4". mongodb.com.
  13. ^ "Release Notes for MongoDB 1.6". mongodb.com.
  14. ^ "Release Notes for MongoDB 1.8". mongodb.com.
  15. ^ "Release Notes for MongoDB 2.0". mongodb.com.
  16. ^ "Release Notes for MongoDB 2.2". mongodb.com.
  17. ^ "Release Notes for MongoDB 2.4". mongodb.com.
  18. ^ "Release Notes for MongoDB 2.6". mongodb.com.
  19. ^ "Release Notes for MongoDB 3.0". mongodb.com.
  20. ^ "Release Notes for MongoDB 3.2". mongodb.com.
  21. ^ "Release Notes for MongoDB 3.4". mongodb.com.
  22. ^ "Release Notes for MongoDB 3.6". mongodb.com.
  23. ^ "Release Notes for MongoDB 4.0". mongodb.com.
  24. ^ "Release Notes for MongoDB 4.2". mongodb.com.
  25. ^ "Release Notes for MongoDB 4.4". mongodb.com.
  26. ^ "Release Notes for MongoDB 4.4". mongodb.com.
  27. ^ "Release Notes for MongoDB 4.4". mongodb.com.
  28. ^ "Release Notes for MongoDB 5.0". mongodb.com.
  29. ^ "Press Cover for MongoDB 5.0". hostadvice.com.
  30. ^ "MongoDB 5.0 White Paper". mongodb.com.
  31. ^ "MongoDB 6.0 Released". mongodb.com.
  32. ^ "Release Notes for MongoDB 7.0". mongodb.com.
  33. ^ Davis Kerby. "Why MongoDB is the way to go". DZone. Archived from the original on June 12, 2018. Retrieved July 6, 2017.
  34. ^ "Ridiculously fast MongoDB replica recovery Part 1 of 2". ClusterHQ. Archived from the original on October 30, 2017.
  35. ^ a b "MongoDB docs - Replica Set Arbiter". Retrieved April 9, 2021.
  36. ^ "Turning MongoDB Replica Set to a Sharded Cluster". Severalnines. May 11, 2013. Archived from the original on November 25, 2016.
  37. ^ "GridFS & MongoDB: Pros & Cons". Compose. June 5, 2014. Archived from the original on September 10, 2017.
  38. ^ "NGINX plugin for MongoDB source code". GitHub. Archived from the original on April 11, 2016. Retrieved September 10, 2016.
  39. ^ "lighttpd plugin for MongoDB source code". Bitbucket. Archived from the original on August 7, 2011. Retrieved June 28, 2010.
  40. ^ Malick Md. "MongoDB overview". Expertstown. Archived from the original on March 5, 2014. Retrieved February 27, 2014.
  41. ^ "Aggregation — MongoDB Manual". docs.mongodb.com. Archived from the original on November 29, 2018. Retrieved August 14, 2018.
  42. ^ "Map-Reduce — MongoDB Manual". docs.mongodb.com. Archived from the original on August 14, 2018. Retrieved August 14, 2018.
  43. ^ "MongoDB Drives NoSQL More Deeply into Enterprise Opportunities". June 27, 2018. Archived from the original on August 7, 2018. Retrieved August 7, 2018.
  44. ^ MongoDB 4.2.6
  45. ^ "MongoDB Download Center". MongoDB. Archived from the original on August 14, 2018. Retrieved August 14, 2018.
  46. ^ "MongoDB Download Center". MongoDB. Archived from the original on August 14, 2018. Retrieved August 14, 2018.
  47. ^ "MongoDB launches Global Clusters to put geographic data control within reach of anyone". MongoDB. Archived from the original on June 27, 2018. Retrieved June 27, 2018.
  48. ^ "MongoDB will destroy all data of Russians and Belarusians".
  49. ^ MongoDB. "GitHub - mongodb/mongo". GitHub. Archived from the original on July 29, 2017. Retrieved July 6, 2017.
  50. ^ Ma, Jason. "Visualizing Your Data With MongoDB Compass". Dzone. Dzone.com. Archived from the original on May 22, 2018. Retrieved July 6, 2017.
  51. ^ Baer, Tony. "It's MongoDB's turn to change its open source license". ZDNet. Archived from the original on October 31, 2018. Retrieved October 16, 2018.
  52. ^ "MongoDB switches up its open source license". TechCrunch. Archived from the original on October 16, 2018. Retrieved October 16, 2018.
  53. ^ Staff, Ars (October 16, 2019). "In 2019, multiple open source companies changed course—is it the right move?". Ars Technica.
  54. ^ OSI (January 19, 2021). "The SSPL is Not an Open Source License". OSI. Archived from the original on August 20, 2022. Retrieved August 20, 2022.
  55. ^ Vaughan-Nichols, Steven J. "MongoDB "open-source" Server Side Public License rejected". ZDNet. Archived from the original on January 16, 2019. Retrieved January 17, 2019.
  56. ^ "MongoDB's licensing changes led Red Hat to drop the database from the latest version of its server OS". GeekWire. January 16, 2019. Archived from the original on January 17, 2019. Retrieved January 17, 2019.
  57. ^ Krebs, Brian. "Extortionists Wipe Thousands of Databases, Victims Who Pay Up Get Stiffed". krebsonsecurity.com. Brian Krebs. Archived from the original on January 11, 2017. Retrieved January 11, 2017.
  58. ^ Constantin, Lucian (January 6, 2017). "Ransomware groups have deleted over 10,000 MongoDB databases". Computer World. IDG. Archived from the original on January 10, 2017. Retrieved January 11, 2017.
  59. ^ Ottenheimer, Davi. "How to Avoid a Malicious Attack That Ransoms Your Data". www.mongodb.com. Retrieved June 22, 2021.
  60. ^ "MongoDB Bind IP Compatibility". MongoDB. MongoDB. Archived from the original on March 6, 2019. Retrieved March 5, 2019.
  61. ^ Kyle Kingsbury (April 20, 2015). "Call me maybe: MongoDB stale reads". Archived from the original on August 15, 2015. Retrieved July 4, 2015.
  62. ^ "Release Notes for MongoDB 3.4". MongoDB Manual. Archived from the original on August 14, 2018. Retrieved April 6, 2018.
  63. ^ Kingsbury, Kyle (February 7, 2017). "MongoDB 3.4.0-rc3". Jepsen. Archived from the original on October 23, 2017.
  64. ^ "Atomicity, isolation & concurrency in MongoDB". scalegrid.io. Archived from the original on September 10, 2017. Retrieved June 28, 2017.
  65. ^ a b "MongoDB Goes Pluggable with Storage Engines". datanami.com. March 5, 2015. Archived from the original on July 4, 2017. Retrieved June 28, 2017.
  66. ^ Arborian Consulting. "MongoDB, MMAPv1, WiredTiger, Locking, and Queues". Arborian Consulting. Archived from the original on June 19, 2017. Retrieved June 28, 2017.
  67. ^ Kenny Gorman (October 2015). "MongoDB 3.0 WiredTiger Compression and Performance". Objectrocket.com/. Archived from the original on June 16, 2017. Retrieved June 28, 2017.
  68. ^ Mikita Manko. "MongoDB performance bottlenecks, optimization Strategies for MongoDB". mikitamanko.com. Archived from the original on July 19, 2017. Retrieved July 5, 2017.
  69. ^ scalegrid.io (September 12, 2013). "Atomicity, isolation & concurrency in MongoDB". scalegrid.io. Archived from the original on September 10, 2017. Retrieved July 5, 2017.
  70. ^ Glasser, David (June 7, 2016). "MongoDB queries don't always return all matching documents!". Meteor Blog.
  71. ^ "MongoDB Docs". Archived from the original on March 6, 2019. Retrieved March 5, 2019.
  72. ^ "MongoDB and Jepsen". MongoDB. Archived from the original on May 8, 2020. Retrieved August 4, 2023.
  73. ^ Allen, Jonathan (May 22, 2020). "Jepsen Disputes MongoDB's Data Consistency Claims". InfoQ. Archived from the original on June 6, 2023. Retrieved August 4, 2023.
  74. ^ a b Kingsbury, Kyle (May 15, 2020). "Jepsen: MongoDB 4.2.6". Jepsen. Archived from the original on May 29, 2023. Retrieved August 4, 2023.
  75. ^ "MongoDB And Jepsen". MongoDB. Archived from the original on June 10, 2023. Retrieved August 4, 2023.
  76. ^ "MongoDB World". www.mongodb.com. Archived from the original on April 26, 2019. Retrieved April 10, 2019.
  77. ^ "Mongo 2014 Announcement". MongoDB.
  78. ^ "Mongo 2015 Announcement". MongoDB.
  79. ^ "Mongo 2016 Announcement". MongoDB.
  80. ^ "Mongo 2017 Announcement". icrunchdata.
  81. ^ "Mongo 2018 Retrospective". KenWalger. July 7, 2018.
  82. ^ "Mongo 2019 Sneak Peek". MongoDB.
  83. ^ "Mongo 2020 event". Eventil.
  84. ^ "MongoDB.live Returns this Summer". MongoDB.
  85. ^ "MongoDB World 2022". MongoDB.

Bibliography

Wikimedia Commons has media related to MongoDB.
Retrieved from "https://en.wikipedia.org/w/index.php?title=MongoDB&oldid=1178620921"