## Dear Relay Operators
How do you handle scaling out? I want to run a relay but keep it performant no matter what (organic) demand grows to and for that I would require clients to not all communicate through the same proxy and DNS based round-robin seams to also not be optimal to get a relay that is close by. I was thinking of redirecting based on client IP. Do clients gracefully redirects? If wss://a.com redirects to wss://us.a.com, does that work or will half the client not know what to do with that? Are there already relays that do that?
LeoWandersleb / Leo Wandersleb
npub1gm…78rf6
2023-03-21 21:05:46
Author Public Key
npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6Published at
2023-03-21 21:05:46Event JSON
{
"id": "c1ba319dba4690643e9561173947fcdec9b996423ad723319fbe5edbbaa9f242",
"pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
"created_at": 1679432746,
"kind": 1,
"tags": [],
"content": "## Dear Relay Operators\n\nHow do you handle scaling out? I want to run a relay but keep it performant no matter what (organic) demand grows to and for that I would require clients to not all communicate through the same proxy and DNS based round-robin seams to also not be optimal to get a relay that is close by. I was thinking of redirecting based on client IP. Do clients gracefully redirects? If wss://a.com redirects to wss://us.a.com, does that work or will half the client not know what to do with that? Are there already relays that do that?",
"sig": "5b354fdb7758ebee11338c262c0a036d1d1e3c7d1845a3b7e5c1af99af57ad7464e3cab68f426986da232039ba877799facc2287650a4d45c33ae6bf72a0ed9e"
}