Hacker News Reader

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.

View on HN

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...

AWS ES has major problems, have been a pain us for years. Pretty sure they cannot be competitive with a hard fork

My guess, from AWS experience, is that you're right. What specific pain points did you experience?

Other services are great. Aws es is just put together. It goes down, blue green updates take forever, arbitrary disk limits etc.

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.

Reply on news.ycombinator.com