Comment by kfir
4 years ago
> But for ElasticSearch you’re stuck with them.
I am a bit at a loss about that statement, you can run Elasticsearch on your on infrastructure
4 years ago
> But for ElasticSearch you’re stuck with them.
I am a bit at a loss about that statement, you can run Elasticsearch on your on infrastructure
Quoting the comment you're replying to:
> If OpenSearch is truely open then in theory you can find another provider
Those are the key words. With an open source solution someone else can offer a turn-key solution that benefits from economies of scale.
Uh...can they? Who's going to benefit from more "economies of scale" than Amazon, Alibaba?
Can Azure offer an OpenSearch service? Probably.
So the idea is you can move from AWS to Azure if you wanted to with open source services underneath.
That is not entirely true, of course. Not if you don’t want to pay. As proof - just look at Amazon, they can’t (that’s why they forked it).
I don't think it's the freedom to run it anywhere. It's the freedom to run it anywhere and make changes to it that you don't contribute back:
1. Amazon wants to make private changes to the management layer for their cloud offering and not share those.
2. ES doesn't want that, so the 7.11+ license restricts it.
3. Amazon doesn't want to have to explain to their customers why their ES offering is stuck on v7.10, so they're changing the name of it.
4. Elastic was really hoping this wouldn't happen, but they overestimated the value of their brand and Amazon called their bluff.
So yeah, nominally OpenSearch is unrestricted, but realistically few other entities are in a position to make or benefit from the private modifications Amazon will be making. For us normal people, ES and OS are equivalent today, so it's more about how they're going to diverge over time in terms of fixes, features, whatever.
The SSPL directly prohibits offering the software as a service without releasing the source code of your entire operation regardless of if you change it or not:
> If you make the functionality of the Program or a modified version available to third parties as a service, you must make the Service Source Code available via network download to everyone at no charge...
> “Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available.
AKA someone must be able to create aws.example.com if aws uses SSPL code. Not exactly the 'freedom to run it anywhere'.
https://www.mongodb.com/licensing/server-side-public-license....
5 replies →
Err, SSPL which Elasticsearch is licensed under isn't AGPL - it's a viral, proprietary license - not quite the copyleft we'd want if we wanted a fair playing field between all actors working on it.
18 replies →