I think their real purpose was to make it impossible for SAAS vendors to operate anything dependent on #MongoDB without buying a commercial license instead of the SSPL.
(Would $CLOUD_VENDOR open source everything, including virtualization configs, systemd units, backup scripts in order to keep using MongoDB? Or would they perhaps fork the last truly free version, and together with others in similar straits, take over maintenance and development, cutting off the MongoDB corporate entity? Or visit #Apache's various #NoSQL projects and try out potential replacements?)
I looked briefly for a comparison of revenue trends pre-SSPL and post-SSPL, but saw nothing. I should probably devote some more time to it, but that will have to be another time.
@Nobody [LinuxWalt (@lnxw48a1)] As Bradley Kuhn has pointed out many times, community license enforcement is aiming for compliance, and getting those who are violating the license into compliance.
License enforcement backed by investors is hoping for non-compliance, and converting license violations into sales.
> Or would they perhaps fork the last truly free version, and together with others in similar straits, take over maintenance and development, cutting off the MongoDB corporate entity? Or visit #Apache's various #NoSQL projects and try out potential replacements?
The answer came less than 3 months after the license change[0]:
> Today we are launching Amazon DocumentDB (with MongoDB compatibility), a fast, scalable, and highly available document database that is designed to be compatible with your existing MongoDB applications and tools.
They slapped a MongoDB API on their Aurora service, the product underneath their RDS (Relational Database Service).