Earlier quoted context omitted.
> In fact, Amazon contributes very little to open source in general, considering how much they take from it I don’t think this is a fact. Amazon seems to contribute pretty significantly according to the pages [0,1] they put out that describes their contributions. Not to mention their membership in OSS foundations like Linux Foundation. [2] You have the caveat about in relation to benefit they gain, but that’s pretty…
The absolute claim, aside from being at home in a rant on HN, comes from a cursory glance at https://github.com/amzn , weighted by contributors and popularity, and compared to companies of similar size. Google, Microsoft and Facebook all build and maintain multiple open source projects that are hugely popular with people who use them outside of the company sandboxes. For example, people benefit from React without Fac…
OpenSearch: AWS fork of Elasticsearch and Kibana
81–90 of 438 posts
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#82I have mixed feelings about this server side license stuff that mongo db started. Imagine where the internet would be today if the creators of apache and mysql had tried to prevent shared hosting providers in the early days of the web from using their software
Do you remember a time when there were hundreds of hosting providers? Do you remember WebHostingTalk where admins would go to check hosting offers from suppliers around the world?
The monopolies finished that era. So I don't think that software companies trying to adapt now can be seen through the lens of what was 15 years ago.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#83Earlier quoted context omitted.
Is it really price gouging for bandwidth? Or is bandwidth just really expensive in general? I honestly don't know. I would assume if it was actually much cheaper one of the cloud's would undercut the other to get customers.
Why would players in an oligopoly undercut each other when their implicit agreement around pricing makes all of them richer? Also, second tier cloud providers like Oracle give deep discounts and still can't compete with AWAZGO so pricing isn't necessarily a main competitive advantage.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#84On their home page, "Why use Elastic search?", the reasons are basically:
* It's fast!
* It does a lot of stuff!
* It has some tools to visualize data!
* It's distributed!!
I have to say this is not very appealing to me since it sounds like something any database could do.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#85On a different note, recently I was looking to learn AWS concepts through online courses. After so much of research I finally found this e-book on Gumroad which is written by Daniel Vassallo who has worked in AWS team for 10+ years. I found this e-book very helpful as a beginner.
This book covers most of the topics that you need to learn to get started:
If someone is interested, here is the link :)
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#86Naive aside, but why would I want to use ElasticSearch or OpenSearch over Solr? Are ES and Solr not both based on Lucene?
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#87It's hard for me to know whether to feel bad for ES in this case. Did they bring it on themselves? Is Amazon too big and a bully? From my perspective, Amazon has made most of its profit price gouging consumers on bandwidth after vendor locking them into their ecosystem, where they bootstrap new services by wrapping open source software with some provisioning scripts, management dashboards and cookie-cutter API / cons…
Is it really price gouging for bandwidth? Or is bandwidth just really expensive in general? I honestly don't know. I would assume if it was actually much cheaper one of the cloud's would undercut the other to get customers.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#88Earlier quoted context omitted.
As a longtime ElasticSearch cluster admin/developer and Elastic Cloud customer, I don't feel bad for Elastic in the slightest and I'm psyched about this fork. The way they operate their cloud service leaves a lot to be desired and encourages maximum spend if you end up wanting to use it for anything demanding in production.
This is really a shame to hear. There was once a an Elastic SaaS company from Norway called found.io that were pretty sharp and customer-centric. They were acquired be Elastic pretty early on[1]. I believe Elastic Cloud was built from this. I guess found.io's culture of delivering a good product didn't survive? https://www.elastic.co/about/press/elastic-acquires-elastics...
I truly believe the negative voices are coming to the fore in this thread or they are paid Amazon folks (or they have a vested interest in AWS succeeding here).
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#89Naive aside, but why would I want to use ElasticSearch or OpenSearch over Solr? Are ES and Solr not both based on Lucene?
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#90Naive aside, but why would I want to use ElasticSearch or OpenSearch over Solr? Are ES and Solr not both based on Lucene?
I'd probably use ES for any log analytics and Solr for things like website and ecommerce search.
Of course, you could do both with either.