Re:Licensing changes to Elasticsearch and Kibana
by nopzor on Thursday January 14, 2021 @10:41AM
(#25777652)
they’d still be able to innovate their own fork, but they will no longer be able to pull future upstream elastic code into it. so it becomes more of a hard fork. if elastic continues to innovate it will be difficult for open distro to remain competitive with it.
[ Parent
| on HN ]
Re:Licensing changes to Elasticsearch and Kibana
by ta988 on Thursday January 14, 2021 @11:17PM
(#25786946)
I don't think AWS really cares. They "bought" (the devs of), and killed, blazegraph to make Neptune. And since, Neptune doesn't really evolve much either so both projects are stagnating. Enough to say they can do "graphs" but not enough to really do anything useful...
Re:Licensing changes to Elasticsearch and Kibana
by CSDude on Thursday January 14, 2021 @04:20PM
(#25782753)
AWS ES has major problems, have been a pain us for years. Pretty sure they cannot be competitive with a hard fork
Re:Licensing changes to Elasticsearch and Kibana
by jamesblonde on Thursday January 14, 2021 @05:32PM
(#25783742)
My guess, from AWS experience, is that you're right. What specific pain points did you experience?
Re:Licensing changes to Elasticsearch and Kibana
by CSDude on Thursday January 14, 2021 @09:36PM
(#25786274)
Other services are great. Aws es is just put together. It goes down, blue green updates take forever, arbitrary disk limits etc.
Re:Licensing changes to Elasticsearch and Kibana
by __blockcipher__ on Thursday January 14, 2021 @10:43PM
(#25786752)
Yeah at my last gig we used AWS’ offering. Blue green deployments would hit a race condition and the new cluster would never come up, requiring a ticket to be filed. Important APIs and settings were disallowed.
Horrible service. That’s why it’s ironic that Elastic just shot themselves in the foot with this licensing change. So foolish.