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)
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 am trying to connect to a client's DB2 v7.2 database in Linux.
I am pretty new to DB2 and could not find 7.2 odbc driver in IBM site. The earliest is 9.1 odbc driver. Is this compatible with v7.2 ?
IBM does not make such old legacy drivers publicly available, for good reasons.
Genuine IBM customers always have a way to acquire legacy drivers however, although this is wholly dependent on who you know.
The v9.1 ODBC driver might have trouble accessing v7.2. It rather depends on which fixpacks are deployed (client and server), which operating-system (for client), and what authorization level you have for the target instance, and what rights you have at the workstation end, apart from the level of competence needed. This is not work for beginners.
Keep in mind that legacy drivers may not be able to install on modern workstation operating-system versions (for example , they might need the workstation operating system to be also a legacy version).
Another approach is to have a detailed understanding of exactly how (with which versions and tools) the client currently connects to that legacy database, and then seek to emulate that mix of versions, possibly by cloning.
This is not a programming question so stackoverflow may not be the correct forum. There are IBM specific forums run by IBM which may help.
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).
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()').
What is the difference between Alfresco Community Edition and Alfresco Enterprise Edition ?
Any differences in both features it provides ?
Can we down load Enterprise edition with longer trial license ?
The Enterprise Edition is the commercially supported Edition. In addition to support, you also get patches, updates, indemnity, and access to certified partners. From a functionality standpoint, the software is virtually the same. There are a few things only available to Enterprise such as support for commercial databases and application servers, the XAM connector, and JMX.
Both Enterprise and Community are tested by our QA team. When it is time to distribute an Enterprise release, a branch is created. That branch undergoes additional testing and is frequently patched with fixes. These fixes go into the Enterprise release for that branch and are later merged back into the main code line so that they will be available in a future Community release.
Both Enterprise and Community are 100% open source. Community is distributed under the LGPLv3 license.
If you start an Enterprise Trial and you need to extend beyond your 30 day license you should talk to the account rep you are working with. Extensions can be granted.
Actually, as of the 4.1 releases, HA & clustering is no longer supported at all in the community. Research the forums and you will see that enterprise is the only way to go for enterprise deployments.
They say
Alfresco Enterprise Edition includes Document Management, Web Content Management, Share and the Content Platform. Records Management, as well as Enterprise add-ons such as clustering and a connector for content addressable storage can be added as an additional subscription on top of the base subscription.
Contact us to learn more about pricing for our Alfresco Enterprise Subscription.
thats wrong! the addons such as clustering are included in the community release. the difference is, that the enterprise version is the stable version with support and extensive tests
see: http://storage.pardot.com/1234/46851/Alfresco_Datasheet_Community_Network_eng.pdf
"No High-Availability Cluster Testing"
In my opinion, the Community Edition is generally sufficient to serve about 50 concurrent users. This should be good enough for most usage scenarios. The Community Edition has all the core features that the Enterprise Edition has. The only difference is, you do not get official technical support for the Community Edition from the company. However, Alfresco has a strong users community base that provides assistance when needed.
You can try Alfresco Community Edition by subscribing to hosted services offered at http://www.alfresco-fusion.com
After signing up you will be offered fully functional Alfresco Server at a very affordable monthly cost.