Hacker News Reader

Comment by lolinder | Hacker News Reader

Are you the one who makes the call, or are you getting hundreds of customers requesting OpenSearch over Elastic?

If you're making the call then that's really one anecdote, not hundreds.

I let the customers choose by themselves. And guess what they choose every single time after checking license cost from Elastic.

Do you tell them that it's deploy OpenSearch or buy an Elastic license, not mentioning that they could also legally deploy their own Elastic?

If only they had the skills to deploy and maintain it sure. But they don't so they ask services companies/DevOps to do it for them. No need to be AWS to be affected by SSPL

If you're referring to the SSPL (it's unclear), it can be used without obligations when a service uses it as a storage, rather than providing it as a service to the clients. Since the latter case is essentially cloud companies, I'm confused by the business nature of the "hundreds of customers"; if they're not cloud companies, Elasticsearch pre- or post-license change makes no difference.

SSPL is also preventing DevOps/services companies to deploy for their customers, it's not affecting only cloud providers.

> SSPL is also preventing DevOps/services companies to deploy for their customers, it's not affecting only cloud providers.

If a "DevOps" company purely provide deployment services, and doesn't offer a managed Redis service, SSPL makes no difference.

It seems that the term "DevOps/services" is a way to refer to companies that offer Redis as managed service, without calling them "cloud providers". This type of service is what a large part of the IT community is againt, and that licenses like AGPL/SSPL try to prevent.

Reply on news.ycombinator.com