I 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
OpenSearch: AWS fork of Elasticsearch and Kibana
31–40 of 438 posts
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#32It'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…
> 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…
To me it looks like they mostly contribute to projects that are SDKs to use AWS.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#33What about the thing that is already named OpenSearch?
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#34Okay... and what's the difference here from Open Distro for ElasticSearch? I guess it's just a rebranding, isn't it?
OpenDistro for ES is the surrounding tools for ES => plugins, index-state-management, basically a suite clone of ES Enterprise offerings (X-pack) because AWS can't ship AWS ES with X-Pack.
OpenSearch is the ES (core) itself.
If I'm not mistaken.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#35What about the thing that is already named OpenSearch?
It’s what Chrome’s tab to search utilizes. If you implement the protocol users can tab-to-search your site even with autocomplete.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#36Earlier quoted context omitted.
I think the claim that Amazon is winning through "vendor lock-in" is pretty silly. Honestly anyone who can't quickly migrate the stuff they're hosting on AWS onto one of the many other cloud platforms is pretty bad at DevOps. If you're using K8S/Docker/etc it should be trivial . But even if you're not, the vast majority of AWS offerings were either built to be API-compatible with other existing tools (e.g. postgres-c…
If you're not using any of the AWS services, that might be true but then you're also leaving a lot of potential on the table. If you're "cloud-agnostic" and could migrate away from AWS in the blink of an eye then you're paying for an overpriced VM offering and should probably migrate to a cheaper hosting provider immediately.
> If you're "cloud-agnostic" and could migrate away from AWS in the blink of an eye then you're paying for an overpriced VM offering and should probably migrate to a cheaper hosting provider immediately.
No this is what everyone suggesting this does not get. The offerings are not equivalent.
There are a baseline of services that the cloud providers offer that can be made functionally-equivalent. It's not just EC2 but more like EC2,S3,Lambda,RDS,DynamoDB,ECS,EKS (plus some others and of course the other cloud's equivalents). The secret sauce is in the APIs and permisioning and all of these available within the same VPC (talking to each other without paying bandwidth costs).
"Cloud-agnostic" has _never_ meant "just VMs". Some of these services are majorly hard to duplicate on your own VMs as well. Feel free to implement "cheap VM hosting + S3" and burn cash on transit costs.
Cheaper hosting providers do not give you this by miles.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#37Okay... and what's the difference here from Open Distro for ElasticSearch? I guess it's just a rebranding, isn't it?
Open Distro for ElasticSearch was not a fork rather an Apache 2.0-licensed distribution of Elasticsearch enhanced with enterprise security, alerting, SQL etc... OpenSearch is a community-driven, open source search and analytics suite derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#38It'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…
> 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…
Yeah and also what about projects like Firecracker?
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#39It'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…
My favorite "conspiracy theory" is that AWS intentionally creates stupidly verbose and numerous headers in all of their APIs just to up the bandwidth usage a few bytes per request at a time.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#40What about the thing that is already named OpenSearch?
Turns out that was developed by Amazon according to Wikipedia. So maybe they’re merging that usage into this offering (since that is a spec for search results)?