Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenSearch: AWS fork of Elasticsearch and Kibana

aws.amazon.com

Post reply on HN
Print view View original

201–210 of 438 posts

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#201

Post by api_or_ipa »

fallat wrote: post #84

So as someone who has heard about Elasticsearch for years and years, and seen all this, right this moment I've decided to see what it really is. On 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.

Elasticsearch is a no-sql database that optimizes for full-text searches, built atop Apache Lucene. If you're doing any kind of full-text search, for example, if you're trying to index a university library and make it searchable, then elasticsearch is for you. If you're not, I'd look elsewhere.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#202

Post by ev1 »

gnfargbl wrote: post #191
ev1 wrote: post #160

Earlier quoted context omitted.

I'm below $100/1Gbps 95% with more than one provider as a small player

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).

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#204

Post by JamesSwift »

fastball wrote: post #177
JamesSwift wrote: post #147

Earlier quoted context omitted.

1) A vast majority of users are relying on managed services to some degree. 2) Permissions as a whole are usually very ingrained into much of what orgs rely on.

What do you mean when you say managed services? Because to me managed services are definitely not vendor lock-in because you can self-host most of those services and just migrate your data over. With regards to permissions, I don't feel like it's possible to permission across an entire platform and not make it difficult to migrate over – do you know of any provider or platform that allows for cross-platform authentic…

I generally think of managed services as anything not run directly on EC2.

I agree about permissions. I'm just illustrating where the lock in occurs.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#206

Post by Graphguy »

bmcahren wrote: post #157
Graphguy wrote: post #129

Earlier quoted context omitted.

Kinda blocked on the compatibility front after the 4.0 API though, eh?

Not if the recent Oracle vs Google supreme court ruling is to be acknowledged. DocumentDB is to MongoDB 4.0+ as Dalvik runtime was to JVM. Here is their 4.0 compatibility update: https://docs.aws.amazon.com/documentdb/latest/developerguide...

Time will tell...MongoDB 4.2 APIs are under SSPL

"Amazon DocumentDB implements the Apache 2.0 open source MongoDB 3.6 and 4.0 APIs by emulating the responses that a MongoDB client expects from a MongoDB server, allowing you to use your existing MongoDB drivers and tools with Amazon DocumentDB."

https://aws.amazon.com/documentdb/

IANAL

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#207

Post by sdesol »

sdesol wrote: post #78

Will be interesting to see the resources that AWS will throw at this. You can get a sense of the resource that elastic.co is throwing at elasticsearch at https://public-001.gitsense.com/insights/github/repos?r=gith... I'm currently indexing the fork, so in about an hour or two, I'll provide the insights for the fork as well.

I can't edit the comment anymore, but you can find the fork at https://public-001.gitsense.com/insights/github/repos?r=gith...

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#208

Post by mikepurvis »

judge2020 wrote: post #174
mikepurvis wrote: post #127

Earlier 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…

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 offer it as a premium-tier feature:

https://docs.gitlab.com/ee/integration/elasticsearch.html

Maybe this really is just a cash grab from the Elastic side, like, "it's too easy to self-host rather than paying for our SaaS offering, so now you need to pay us for many common self-hosting use cases also."

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#209

Post by antpls »

VWWHFSfQ wrote: post #125
catern wrote: post #99

Earlier 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.

Technically it doesn't just prevent from selling SaaS. It prevents from selling SaaS without having the consent of the open source project first, which means negotiating a deal.

Re: OpenSearch: AWS fork of Elasticsearch and Kibana

#210

Post by dijit »

bigtones wrote: post #187
dijit wrote: post #88

Earlier quoted context omitted.

Honestly the amount of negativity towards Elastic in this thread is jarring. I’ve been an ES customer (self hosted, some cloud) for years and have only good things to say about them. Maybe I’m less a fan of the number of features they try to bake in and the direction of the company towards using logs for metrics (which causes heavy disk load instead of just storing metrics in time series) but. Yeah. I truly believe t…

Are you even a customer if you don't pay Elastic any money ? Your a user, sure, but not a customer. These other opinions and negative voices you reference come from actual customers who pay Elastic large sums of money, and they feel they don't get good value and service for that money they're forking over.

You cannot use the cloud systems without paying; how on earth do you figure I’m not a customer from what I wrote?
Post reply on HN