thanks very much for providing your keen input
Right, latency is hit or miss, and when GWs are over cellular it is always worst and can cause issues when the network server is lagging. But I do see your point here, but my current client is a manufacturer of lora devices, and he plans to sell kits globally and I would hate to have him log into different App servers to monitor his devices.
So I am thinking, I will try to setup CHIRPSTACK Gateway Bridge in each region, and keep my network servers in one region, sharing managed database, redis cluster, mqtt broker. Gateway Bridge only requires mqtt so setting up new regions will be easy. and I assume that latency between AWS regions will be minimal. I can probably use t3.nano for each (4usd / month) for each GW until I grow…
In regards to latency and dealing with it,
@brocaar On another LNS server I use for a project, they have a parameter to set network delay per gateway to take network latency into account. So if the GW is averaging 300ms ping, you can play with the delay in the App Server, set it for uplink and downlink, and the LNS will take that into account when handling downlinks to the GW.