Open BasToTheMax opened 2 years ago
We have a cache API
I know, but I think redis is faster instead of http requests
But our goal isn't to offer redis. You can go to an existing cloud provider for that? Everything we're providing is through a uniform API. To offer redis itself just puts us into infrastructure hosting. Not really our strength. Also not clear how that would work here. What deploys redis?
Should I close this issue?
I'm still thinking about it. I can see how a "redis" API would be well received but would people be happy with just a http API to redis?
I think a HTTP api is good enough
I think we can do it but I would only do it if I have 10 users immediately lined up to try it. Or 1 user willing to pay. Otherwise I'm investing time in something for no reason. Redis is deemed infrastructure so for us to elevate it to be service needs really good reason. As the Cache could just be the better high level representation.
You get your own redis cache instance! (with a memory limit)