My mongodb is in version 3.0 and run on Linux Redhat 6.
I do not use entreprise options, then I would like to switch enterprise edition to community edition. Any drawback on data? It's much like binary upgrade?
Unless you are using an Enterprise storage engine (eg. Encrypted Storage Engine in MongoDB 3.2+), the data format in MongoDB Community and Enterprise editions is identical and changing between editions is just a change in the MongoDB server binaries. If you need to change storage engines you can do so without downtime on replica sets using a rolling maintenance procedure (see: Your Ultimate Guide to Rolling Upgrades).
I would recommend using matching release versions when changing between MongoDB Enterprise and Community editions to minimize any unexpected issues. The standard upgrade/compatibility caveats (as mentioned in the MongoDB Release Notes) apply if you happen to be upgrading or downgrading between major MongoDB versions (i.e. 3.2 and 3.4).
Related
MongoDB 6.0 is out and seems as if it's a worthy candidate to consider after all the hiccups with 5.0.
With all the marketing messaging I am failing to distinguish which features made it to the Community Edition stream and which are limited to Enterprise Edition and/or Atlas.
For one I see (https://www.mongodb.com/docs/manual/core/queryable-encryption/) that for the queryable encryption the CE is getting the Explicit Encryption where as the Automatic Encryption is reserved for EE/Atlas. Any chance someone has done an analysis of what has made it to CE?
I have been researching using a MongoDB DBaaS provider and I would like to use the latest version of MongoDB. V4.2 at the time of writing
Some providers I took a look at are:
ObjectRocket
ScaleGrid
mLab
MongoDB Atlas
I'm wondering why MongoDB DBaaS providers other then MongoDB itself (with their Atlas service) are not able to offer the latest version of MongoDB? Not even version 4.0 which was released in Aug 2018 can be found.
It's a shame because MongoDB Atlas is not available as deployment on DigitalOcean.
Can somebody explain, thanks!
This is a result of the SSPL license that MongoDB has used for the core server since 2018.
According to the text of the license, specifically section 13, any company that provides MongoDB database "as a service" (which is what you are asking about) is legally required to provide all of the other software involved in running and operating the service under SSPL.
This is an impossible requirement to comply with in most cases since some of the software that a company may be using to provide the service isn't developed by the company providing the service, and is either proprietary or made available under a license other than SSPL. Therefore the company providing the service wouldn't be able to provide that software they use under SSPL.
For example, it is my non-lawyer understanding that someone providing MongoDB-as-a-service using a completely GPL stack, and publishing all of the pieces, would be in violation of SSPL because the pieces would be provided under GPL and not SSPL.
A company could comply with SSPL by developing their own system management software and releasing all of it under SSPL. But there's a weak business case for doing something like this.
MongoDB itself, being the copyright holder of its software, is not bound by SSPL's requirements and does not provide the software it uses to provide MongoDB-as-a-service under SSPL (i.e. MongoDB Atlas is proprietary).
Not even version 4.0 which was released in Aug 2018 can be found.
MongoDB 4.0.3 is the last version licensed under AGPL. This version could be provided as a service without the provider being under SSPL obligations, but users would most likely demand the current 4.0 release (4.0.19 as of this writing) which is under SSPL, plus a provider offering 4.0.3 would be on their own as far as patching any security vulnerabilities found in MongoDB since 2018.
ScaleGrid offers MongoDB on DigitalOcean including 4.2 support. We have a licensing deal in place with MongoDB which allows us to offer MongoDB-as-a-service.
(Disclaimer - I am the founder)
We have an app that uses the C# Mongodb client lib from mongo, version 1.1.0.4184
This code currently runs against mongodb 2.6.4
We would like to stand up a new mongodb server, the current version (3.2.11). Will our code run against newer mongodb?
It really depends what you mean by "will it run". The MongoDB v1.1.0.4184 C# driver was released in June, 2011 and dates to roughly the MongoDB 1.8 server release timeframe. This driver version is certainly no longer tested or supported, and will not be fully compatible with newer server features like the WiredTiger storage engine (default in MongoDB 3.2+) or SCRAM-SHA-1 authentication (default in MongoDB 3.0+).
The MongoDB documentation includes a reference table with recommended version(s) of the drivers for use with a specific version of MongoDB: C#/.NET Driver Compatibility.
If this is a production system I would strongly recommend taking the time to update and test a supported version of the C# driver for use with MongoDB 3.2 (eg. the v1.11 C# driver). I suspect it is very likely you will encounter fixed (or novel) bugs/behaviour using a driver that is more than five years old. Your application won't be able to take advantage of many of the newer server features, and this obsolete driver predates specifications such as standard Server Discovery and Monitoring (SDAM) behaviour.
That said, assuming you aren't using any features the driver isn't aware of your code may continue to run (or at least appear to run) successfully. In my opinion doing so is a high risk deployment strategy.
Yes, i am using it, but however we have to chek on specific features, which you were using. using MongoDB latest driver is much better in terms of latest features and there are few features were removed(like 'eval()').
There is a very good SQL client solution for Linux users DBeaver. In spec, it is said that it supports MongoDB and Redis databases.However, there are no such drivers in "New connection" window. Does anyone know how to connect to Mongo or Redis?
The Enterprise edition has MongoDB and Redis support.
EE download
We have split standalone version on Community and Enterprise editions.
Community edition includes the same extensions as DBeaver 2.x.
Enterprise edition = Community edition + NoSQL support (Cassandra and
MongoDB in 3.0). Both Community and Enterprise editions are free and
open source. New Cassandra and MongoDB extensions are not open source
(but free to use).
Since the EE edition of DBeaver is no longer free you can use MongoDB Compass if you want a GUI utility for MongoDB.
There is also RedisInsight (from Redis self) or the popular AnotherRedisDesktopManager for Redis.
Seems the MongoDB release is a significant performance upgrade - ay idea when Spring Data MongoDB will support this version?
Strictly speaking, the MongoDB 3.0 server can even be used with the latest 2.13 Java driver and thus the currently released Spring Data MongoDB 1.6.2. For a full compatibility overview of the driver and server versions, see this wiki page.
The recently released first release candidate of Spring Data MongoDB 1.7 ships support for the MongoDB 3.0 Java driver. This is mostly a compatibility release, we don't target special 3.0 features yet (although you should be able to benefit from an upgrade nonetheless).
Find more information about this in the release train wiki, the JIRA ticket as well as the corresponding section of the reference documentation.
The GA release of Spring Data MongoDB 1.7 is scheduled to be part of the Fowler release train GA end of March.
Spring Data Mongo has 1.7RC1 -> http://docs.spring.io/spring-data/data-mongo/docs/1.7.0.RC1/ Hopefully that one will be released soon.
As Java Driver github repo says, they released a 2.13.0 version on January 29th and it is stable -> https://github.com/mongodb/mongo-java-driver/releases/tag/r2.13.0 It includes all the features for mongo 3.0, but you need to go through the compatibility to upgrade to this version.
Also, they are working on v. 3.0.0. for Java Driver, you can find it here -> https://github.com/mongodb/mongo-java-driver/releases/tag/r3.0.0-beta3 (its still in beta though)