The problem/use-case that the feature addresses
The future is going serverless, and a lot of serverless functions don't support the TCP protocol (Cloudflare, Vercel, Cloud Run for example).
This means it is impossible to connect to a redis instance. There could be a work around using HTTP and a proxy server, but that ultimately requires extra configurations, and gets rid of the advantages of a CDN.
A description of the problem that the feature will solve, or the use-case with which the feature will be used.
Allow the ability to connect to redis using HTTP.
Description of the feature
It seems Upstash has added this ability, probably by hosting their own proxy. Upstash, however, doesn't support RedisSearch, RedisGraph, etc.
A description of what you want to happen.
Simple. Allow HTTP connections instead of TCP to a Redis Database (like Upstash for example).
Alternatives you've considered
Maybe Redis Cloud could just add this feature if you guys don't build it into the core code. However, every self-hosting or cloud provider would need to create their own proxy as well.
Additional information
Here is my original question reguarding node-redis while trying to figure this out.
https://github.com/redis/node-redis/issues/2438#event-8744889853
Thanks!
J
Comment From: hpatro
https://webd.is/ is a proxy in front of Redis supporting HTTP, that's a solution which exists not sure how mature it is though.
Bringing in HTTP native support to Redis would be really interesting. One other use case which would fit in easily is having a Web Sockets server out of the box by plugging into Pub/Sub. Of course, there will be a lot of security related tightening which needs to be done to expose it directly over the internet.
Comment From: jdgamble555
This just requires you to create a proxy. You could create a proxy that can connect to tcp without this package.
The point is to allow a direct connection though http.
J