4 ms·
They could, but would they? That would mean their offering is less competitive vs anyone providing fully featured Redis.
by Reedx 8y ago
They could, but would they? That would mean their offering is less competitive vs anyone providing fully featured Redis.
- ecnahc515 8y agoBecause it's more profitable to fork it, pay 2-3 engineers to maintain their fork, than to pay royalties forever.
- silentsea90 8y agoThat's true now, but maintaining isn't the same as building new stuff. Amazon would have to invest more to build new functionality that Elasticsearch has devs and community helping them build. This assumes the ecosystem of devs has no importance?
- dingo_bat 8y ago2-3 dedicated high-quality devs in a company like Amazon can run circles around 200-300 random github PR contributors when it comes to implementation of features.
- dhd415 8y agoSure they would. AWS's Elasticsearch offering has fewer features than Elastic's offering but is still competitive due to its integration into AWS's other service offerings. The same is true for AWS's Redis offering.
- scarface74 8y agoYes. They did it with ElasticSearch https://aws.amazon.com/blogs/aws/new-open-distro-for-elasticsearch/ https://aws.amazon.com/blogs/aws/new-open-distro-for-elastic... And Java https://aws.amazon.com/blogs/opensource/amazon-corretto-no-cost-distribution-openjdk-long-term-support/ https://aws.amazon.com/blogs/opensource/amazon-corretto-no-c... And something similar with Mongo DB. https://aws.amazon.com/blogs/aws/new-amazon-documentdb-with-mongodb-compatibility-fast-scalable-and-highly-available/ https://aws.amazon.com/blogs/aws/new-amazon-documentdb-with-...