Agree on the court, but the wording is super specific. Doesn’t matter if you couldn’t build it without a redis-like component, because of the speed or whatever, it is targeting “offering the program as a service”. There’s even an FAQ on the mongodb (SSPL authors) site regarding this. Unless your program is just a proxy to access redis, you’re fine.
offering a service the value of which entirely or primarily derives from the value of the Program or modified version
Doing it fast is essential and a core part of many services’ value, I’m sure.
You have a point regarding the FAQ but I do not see that written in the license. This is a problem that would only be granted in case MongoDB/ElasticSearch/Redis sues someone for internal use and I think that’s a borderline risk too much to take.
That wording is pointing to reselling the program or the same functionality. Of course if your service is “fast key based data retrieval” it would violate the definition, but something like “low latency gaming notifications” would not, because the value is gaming notifications, something redis doesn’t offer. Same as if your service uses encryption in transit, you’re not just reselling openssl.
I know prohibiting reselling is what they probably intended. But that doesn’t mean they can’t push a different and very valid interpretation when they want to.
you’re not just reselling openssl.
The wording—“primarily derives from”—is much broader than “just”. I believe that Resque’s dependence on Redis is enough to satisfy “primarily”.
Agree on the court, but the wording is super specific. Doesn’t matter if you couldn’t build it without a redis-like component, because of the speed or whatever, it is targeting “offering the program as a service”. There’s even an FAQ on the mongodb (SSPL authors) site regarding this. Unless your program is just a proxy to access redis, you’re fine.
I feel like it qualifies under
Doing it fast is essential and a core part of many services’ value, I’m sure.
You have a point regarding the FAQ but I do not see that written in the license. This is a problem that would only be granted in case MongoDB/ElasticSearch/Redis sues someone for internal use and I think that’s a borderline risk too much to take.
That wording is pointing to reselling the program or the same functionality. Of course if your service is “fast key based data retrieval” it would violate the definition, but something like “low latency gaming notifications” would not, because the value is gaming notifications, something redis doesn’t offer. Same as if your service uses encryption in transit, you’re not just reselling openssl.
I know prohibiting reselling is what they probably intended. But that doesn’t mean they can’t push a different and very valid interpretation when they want to.
The wording—“primarily derives from”—is much broader than “just”. I believe that Resque’s dependence on Redis is enough to satisfy “primarily”.
Well, I don’t believe so, but as you said it’s ultimately for a court to test it.
deleted by creator