Amazon: Not OK – Why we had to change Elastic licensing

Re:Amazon: Not OK – Why we had to change Elastic licensing by srockets on Tuesday January 19, 2021 @12:39PM (#25836103)

> They don't really out-compete, they just use their existing vendor lock-in to gain an advantage.

For the customer, the biggest advantage of AWS' SaaS offerings over a 3rd party's (hosted on AWS) is the billing. AWS Marketplace negates that. Maybe at some cost to the provider, but I just found ScyllaDB and RedisLabs there, so it must be working for some.

[ Parent | on HN ]

Re:Amazon: Not OK – Why we had to change Elastic licensing by hello_moto on Tuesday January 19, 2021 @01:22PM (#25836704)

> but I just found ScyllaDB and RedisLabs there, so it must be working for some.

No, it doesn't work for RedisLabs. Amazon offers managed Redis called AWS EC Redis and recently someone I knew decided to move their entire Redis (multiple) clusters from RedisLabs to AWS EC. RedisLabs lost hundred of thousand dollars.

[ Parent | on HN ]

Re:Amazon: Not OK – Why we had to change Elastic licensing by srockets on Tuesday January 19, 2021 @02:50PM (#25837950)

I would like to think there are other definitions for a successful business than it being a single vendor.

[ Parent | on HN ]

Re:Amazon: Not OK – Why we had to change Elastic licensing by hello_moto on Tuesday January 19, 2021 @03:24PM (#25838405)

RedisLabs is probably the vendor that foot the bill for Redis software development end-to-end.

While I understand that some people viewed a successful OSS project is akin to Wordpress: lots of hosting providers, rich ecosystems, _and_ Wordpress main company is still making good money out of it; this is not apple to apple comparison (can't compare Redis and Wordpress).

Redis belongs to the group of MongoDB, ElasticSearch, etc.

[ Parent | on HN ]