Earlier quoted context omitted.
https://aws.amazon.com/opensource/
Yes exactly, you have actually to google it maybe you'll be able to find a useful link that makes Amazon looks good.
I'm not sure what you mean.
OpenSearch: AWS fork of Elasticsearch and Kibana
211–220 of 438 posts
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#212Earlier quoted context omitted.
That is not entirely true, of course. Not if you don’t want to pay. As proof - just look at Amazon, they can’t (that’s why they forked it).
I don't think it's the freedom to run it anywhere. It's the freedom to run it anywhere and make changes to it that you don't contribute back : 1. Amazon wants to make private changes to the management layer for their cloud offering and not share those. 2. ES doesn't want that, so the 7.11+ license restricts it. 3. Amazon doesn't want to have to explain to their customers why their ES offering is stuck on v7.10, so th…
Err, SSPL which Elasticsearch is licensed under isn't AGPL - it's a viral, proprietary license - not quite the copyleft we'd want if we wanted a fair playing field between all actors working on it.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#213Earlier quoted context omitted.
The SSPL directly prohibits offering the software as a service without releasing the source code of your entire operation regardless of if you change it or not: > If you make the functionality of the Program or a modified version available to third parties as a service, you must make the Service Source Code available via network download to everyone at no charge... > “Service Source Code” means the Corresponding Sour…
Doesn't a lot of that hinge on what the "service" is? Like, if I run some generic knowledgebase website and use my own ES installation to provide user-facing search, does Elastic want to see my Ansible scripts? Or just the ones related to the search function? If this interpretation holds, I feel like it could be a pretty big problem for companies like GitLab, who not only have deep integration with ElasticSearch, but…
There's several lawyers who believe the wording would imply the problematic interpretation - /dev/lawyer is one on the internet, one from my anecdotes is the lawyer who advised the company I used to work at.
SSPL doesn't come up under free or open source licenses partly for this reason, actually.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#214Earlier quoted context omitted.
That's sounds like a great deal: you're paying less than half of Hurricane's advertised minimum price. And I had understood HE were a mid/low price carrier. Can I ask, are you in a data center? US or Europe?
What do you mean? Hurricane's current special is $90/1Gbit/m. US. Some of the larger bandwidth transit resellers like FDC will do Cogent for $0.02/Mbps. They have a marketing site at epyc100gig.net (not an affiliate or employee; just a FDC customer).
OK, either I'm getting pretty screwed somewhere or EU prices are well above the US. Probably the former. Thanks for the pointer.
https://he.net/cgi-bin/ip_transit_quote is where I'm seeing the $200 number.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#215Earlier quoted context omitted.
What do you mean? Hurricane's current special is $90/1Gbit/m. US. Some of the larger bandwidth transit resellers like FDC will do Cogent for $0.02/Mbps. They have a marketing site at epyc100gig.net (not an affiliate or employee; just a FDC customer).
OK, either I'm getting pretty screwed somewhere or EU prices are well above the US. Probably the former. Thanks for the pointer. https://he.net/cgi-bin/ip_transit_quote is where I'm seeing the $200 number.
On front page https://www.he.net/ there's a special in the top right :)
I believe that kind of low-for-1G-commit pricing is for their fully owned FMT1/FMT2 US CA facility. You have a lot easier peering in EU (AMSIX, DECIX, etc) that will help compared to the US's love of commercial exchanges like Any2/Coresite/Equinix where peering costs practically more than transit.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#216[deleted]
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#217Earlier quoted context omitted.
I don't think it's the freedom to run it anywhere. It's the freedom to run it anywhere and make changes to it that you don't contribute back : 1. Amazon wants to make private changes to the management layer for their cloud offering and not share those. 2. ES doesn't want that, so the 7.11+ license restricts it. 3. Amazon doesn't want to have to explain to their customers why their ES offering is stuck on v7.10, so th…
Err, SSPL which Elasticsearch is licensed under isn't AGPL - it's a viral, proprietary license - not quite the copyleft we'd want if we wanted a fair playing field between all actors working on it.
It's a viral open source license, it literally requires open sourcing code, there's nothing proprietary about it except that we allow a council of elitist snots to decide what is and isn't Open Source(TM), and they have decided Google and Amazon support is more important than viable businesses which are building open source businesses.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#218Earlier quoted context omitted.
One thing which surprised me: Elastic has a market capitalization of ~$11B. I think that changes some of the more floaty ethical concerns. This is not a David vs Goliath situation. This is Goliath vs Super-Goliath. At this point, I'm much less interested in the drama of which mega-corp is screwing over the other. I'm more interested in: how does it affect me? When the titans are done trampling over the rest of us, wh…
This argument is part of Amazon's PR campaign to tell devs to not feel sorry for Elastic because it's now a big company and they make money in the market. So, if you built a successful OSS and start to make money then it's ethical to clone any OSS and pushes projects out of the market because now it is "Goliath vs Super-Goliath".
Quite a few companies have proprietary products but have learned to make money selling services. One of them even has a 200B market cap and is called Oracle.
Nobody needs to feel sorry for anyone.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#219Is there any good that done by Amazon to support OSS? Like ever. They started with cloning MongoDB and now Elastic with actually zero contribution to the community regardless of their insane profits. This is a clear single. Amazon can always clone and redistribute any open source software then lock it in for AWS. If we've started to witness declining in OSS, well at least we know now who started the wave.
Do people assume that a company as large as AWS would automatically have a lot to contribute to the OSS? Maybe most of Amazon teams have not much to open source yet. Contributing to OSS is a bottom-up effort. An engineer needs to be motivated to generalize her project, to peel the code from Amazon's vast internal infrastructure, and to go through an approval process to open source her project. Given that many teams have razor-sharp focus on delivering features, for good or for bad, I was wondering how many engineers are really motivated enough to open source something internal.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#220Earlier quoted context omitted.
This is like going to a fancy restaurant and being upset that they charge so much for a steak when you can get beef at the supermarket for much less.
If you ask the fancy restaurant to cater a steak dinner for 1000 people they will charge you a lot closer to supermarket beef. The point is that if you charge absurd prices for what has basically no marginal cost your pricing model is broken and 1) you are excluding customers that are particularly sensitive to this price or 2) you are liable to undercharge other customers that primarily use other services for which y…
As I explained in another commented AWS wants to disincentivize dumb bandwidth usage. They want you to use your bandwidth for traffic that needs it to EC2, and you get much better rates for static data from CDNs, S3, etc.