FoundationDB is Apache 2.0 https://github.com/apple/foundationdb/blob/master/LICENSE

It is CP per https://apple.github.io/foundationdb/cap-theorem.html

Ah that's the guy. He drove the new roadster last time. I kept wondering who the guy is. He looked really like Reed Hastings...

For SearchGuard, only the basic auth is Apache 2.0. Anything practical you need to pay to use it.

From a look at the source code, Amazon has Apached 2.0 the entire Floragunn Searchguard codebase (including the commercial part)

It's not just about AWS, other people need to use this as well. Why are security features a paid for addition? Why not make core features a paid for addition instead? I've always hated Elastic (the company) for this decision, please stop trying to give away free things that are not secure, and then charge for security.

I'd recommend browsing the code to find out more about the security module:

https://github.com/opendistro-for-elasticsearch/security/blo...

there's no "they", there's only us. AWS paying to use it means we are paying to use it. Between that and a truly Apache 2.0 project, I think it's a no-brainer for everyone.

Why shouldn't you pay to use it, then?

More generally: why should AWS get to leverage its near-monopolistic position in the SaaS market to perform essentially hostile takeovers of the software projects it packages and runs? Simply because they have the resources to do it?

I'm very glad that they've done this.

The code was open, and the company decided to close it for the new versions, so it forks. Forks are common when people don't like the corporate direction of an OSS project - It's a strength, not a weakness. Openoffice/Libreoffice, Hudson/Jenkins etc.

Imagine if Linus said that the next version of Linux would be paid-only.

Within 15 minutes there'd be a new librelinux repo that people could contribute to instead.

Someone was going to make a new fork anyway - This is Amazon putting their money where their mouth is to fund and support that new fork.

To be clear, no Elasticsearch code or features that were OSS were closed. As new Elasticsearch features are developed, some of them are now released as OSS and others are released with a commercial license.

Okay, are you glad that Amazon now owns Elasticsearch?

If ES didn't do the weird license change thing, we wouldn't be here. Either Amazon wouldn't have used it, or they'd be paying. Including non-com features in the default install was not a good way to play things.

Would you feel the same if AWS built a drop in/api compatible system from scratch?

It is pretty normal in Bay Area. All tech companies package are like that.

Leonardo Dicaprio's interview with Sunita Narain in Before the flood is a very good explanation of why this happens. Here it is: https://www.youtube.com/watch?v=90CkXVF-Q8M (starting from 33:20 for 5 mins).

perhaps taking a look at the negative reviews can reveal a little more secret. This is one of them:

  It is sad that someone published this crap and killed thousands of trees. Do you know how long it will take to regrow those trees? 20-30 years. Your selfish lust for money lead you to get up all your principals.

  SHAME.