StackExchange / StackExchange/StackExchange.Redis
Resolution of DNS address records and client-side load balancing
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Hi,
Have we considered implementing resolution of DNS to get multiple addresses (with some periodic updating of list)?
In the same spirit of this: https://learn.microsoft.com/en-us/aspnet/core/grpc/loadbalancing?view=aspnetcore-6.0#configure-resolver
(It could be highly inspired or copied from this Grpc library implementation)
This would be an amazing addition to anyone using Kubernetes or trying to have a simple setup where all servers are in a single DNS address.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked ASP.NET Core gRPC resolver and load-balancing example. Then assess how DNS resolution could return multiple addresses and periodically refresh them for StackExchange.Redis, with client-side load balancing for Kubernetes-style deployments. Done would require an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100