3 ms·
I let the customers choose by themselves. And guess what they choose every single time after checking license cost from Elastic.
by js4ever 2y ago
I let the customers choose by themselves. And guess what they choose every single time after checking license cost from Elastic.
- lolinder 2y agoDo you tell them that it's deploy OpenSearch or buy an Elastic license, not mentioning that they could also legally deploy their own Elastic?
- js4ever 2y agoIf 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
- deleted 2y ago[deleted]
- pizza234 2y agoIf 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.
- js4ever 2y agoSSPL is also preventing DevOps/services companies to deploy for their customers, it's not affecting only cloud providers.
- pizza234 2y ago> 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.