Elastic Licensing and Elasticsearch Forks
Elastic
Last week saw dramatic and rapid developments around Elastic and their open-source product Elasticsearch.
Elasticsearch is a great product that became widely adopted in the last few years - I’ve seen and used it since probably 2013 or 2014.
I’m not qualified as a customer or user of Elastic and AWS to make a statement on these developments - just don’t have enough open-source exposure on a regular basis yet. But I want to capture these announcements because it feels like a major changefor all parties involved.
If you’re an Elastic customer or Elasticsearch user - please take the time to read through the full posts listed below.
January 2021 Elastic Licensing
- On January 14th Elastic announced a licensing change: Doubling down on open, part II, essentially signalling that going forward they’ll use SSPL
- Logz.io then announced they would start their own fork of Elasticsearch
- On January 21st AWS announced they would maintain their own fork of Elasticsearch as part of Open Distro for Elasticsearch
- Same day, Amazon: NOT OK - why license change
- Elastic: License Change Clarification
- And, finally, on January 22nd Logz.io followed up with further update: Truly Doubling Down on Open Source, Part 2 - confirming that they’ll actually work with AWS on a single fork that both Logz.io and AWS will collaborate on.
That’s it for today.
See Also
Elastic
Last week saw dramatic and rapid developments around Elastic and their open-source product Elasticsearch.
Elasticsearch is a great product that became widely adopted in the last few years - I’ve seen and used it since probably 2013 or 2014.
I’m not qualified as a customer or user of Elastic and AWS to make a statement on these developments - just don’t have enough open-source exposure on a regular basis yet. But I want to capture these announcements because it feels like a major changefor all parties involved.
If you’re an Elastic customer or Elasticsearch user - please take the time to read through the full posts listed below.
January 2021 Elastic Licensing
- On January 14th Elastic announced a licensing change: Doubling down on open, part II, essentially signalling that going forward they’ll use SSPL
- Logz.io then announced they would start their own fork of Elasticsearch
- On January 21st AWS announced they would maintain their own fork of Elasticsearch as part of Open Distro for Elasticsearch
- Same day, Amazon: NOT OK - why license change
- Elastic: License Change Clarification
- And, finally, on January 22nd Logz.io followed up with further update: Truly Doubling Down on Open Source, Part 2 - confirming that they’ll actually work with AWS on a single fork that both Logz.io and AWS will collaborate on.
That’s it for today.