One of the best part of elasticsearch is excellent documentation, hope this project can replicate that well.
OpenSearch: AWS fork of Elasticsearch and Kibana
341–350 of 438 posts
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#342Earlier quoted context omitted.
There's tons of businesses that are happy to charge less for bandwidth; so it's clear Amazon (and some of the other high tier cloud services) are overcharging on this maybe by a factor of 10, although since transit bits are not all equal, someone with more detail could make a case that the overcharging is less. It's easyish to compete on bandwidth costs, but Amazon has a lot of other features many people want; it's h…
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.
No, it's complaining that the water at the fancy restaurant is priced expensively, but people still go there because the many options for food.
And it's easy to replicate the water part (after all VPS providers are dime a dozen), the hard part is the food.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#343Earlier quoted context omitted.
the yearly Stack Overflow survey, for one. Find me a bunch of developers and infrastructure people who are EXCITED about running MongoDB. I guarantee you're going to find a 7-10+ year old infrastructure if you do.
This just isn't true. A large number of companies are building new applications with MongoDB atlas
Yes, because Mongo's license prevents them from using alternatives to Atlas (read: other cloud providers). Of course Atlas growth looks good. It's them or self-hosting.
That's not the same as starting a new product on MongoDB.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#344Earlier quoted context omitted.
no. get it right. if you are not free to run the program without additional stipulations, especially stipulations that dictate how you license _your_ code, then you are not free to use the program as you wish. Literally, "as you wish". Stipulations is "as we wish". And you can read it from the OSI themselves: "The SSPL is Not an Open Source License" https://opensource.org/node/1099
The SSPL conveys no new stipulations not permitted by GPL-based licenses, it is just more inclusive in doing so. If SSPL isn't open source, neither is the GPL.
GPL carries no restrictions if you don't distribute the software.
The AGPL on the other hand, was a huge mistake, IMO.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#345Earlier quoted context omitted.
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...
Perhaps telling that none of the Found team are still at Elastic, from what I can tell on LinkedIn. I pay attention to that kind of stuff because (full disclosure) I operate the _other_ small customer-focused managed Elasticsearch company (bonsai.io) that _didn't_ get acquired by Elastic back in 2015.
There's also logz.io, but that's targeted at a specific customer.
Also virtual beers to you -- I really like Websolr!
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#346It'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…
Coincidentally, AWS hasn't open-sourced anything that they use internally. Zilch. Nada. And yet they are using 'open source' developed by another firm (smaller is inconsequential here) to market themselves. IMO, FOSS licensing is completely broken. Its definitions (of what is free/open) are from a boomer's era that is no longer sustainable. At least I wouldn’t want any of my FOSS projects become “corporate strategy”…
That made me wonder which megacorp did? Google published a lot of papers about their architecture, but no code. They have many open source projects modeled after internal tools (eg. bazel), but there's no search/GFS/mapreduce/monorepo OSS project from them. MS has VSCode, that's great, and they even open sourced .NET. But Azure is a full black box, just like (almost) every Windows component. (Finally calc.exe is OSS!)
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#347Earlier quoted context omitted.
The server side license stuff doesn't prevent shared hosting providers from using software. It just requires hosting providers to open source their infrastructure. I think the internet would be even better today, if shared hosting providers had been sharing infrastructure technology since 25 years ago.
I think that's missing the forest for the trees. The license is designed to prevent hosting providers from selling the software as a service to their customers. The requirement to open source their entire infrastructure and operations is just a means to do that.
The value in AWS is not the software. (What I heard about it a few years ago it's very explicitly not the cobbled together software.) It's the whole enterprise, the structure, the teams, the operations staff.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#348I 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
> Imagine where the internet would be today if the creators of apache and mysql had tried to prevent shared hosting PHP + MySQL was the foundation of the Internet not so long ago , Wordpress is stil the backbone of lots of platform. With SS License definitely this would not have been possible.
Why? Dockerized versions of countless server-side software are there for free. In a lot of cases the value is that someone maintains it and operates it for you.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#349It'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…
The main thing I look at in this situation is their approaches to security. ES decided authentication is a paid-only feature implemented via closed source proprietary code, and the result has been countless PII leaks; now sure you could say that’s the developers’ fault for making the endpoints internet-accessible, but when the system has been designed from the start to both be insecure and hold PII, you have to place some blame on the provider as well.
Amazon on the other hand developed a free and open source auth plugin and anyone is able to deploy it no problem.
Re: OpenSearch: AWS fork of Elasticsearch and Kibana
#350Algolia has won the search race, move on
Eh, far from it. Their per record / per query pricing is extremely prohibitive for any real production use.