- Posted on
Mon Jun 01, 2020 8:19 am
-
FlyingDiver
offline
-
- Posts: 7265
- Joined: Jun 07, 2014
- Location: Southwest Florida, USA
How much data are you polling for? How many REST API calls are you trying to make every 500ms? It's possible that if you reduce the frequency of the updates, and minimize the amount of REST calls you're making, then you MIGHT be able to get this to work acceptably.
But, the reality of the situation is that (1) polling is bad, (2) polling at sub-second intervals is worse, (3) REST API calls are fairly high overhead for a single data item, and (4) network delays from Switzerland to the US are just going to make things worse.
Since you can't do anything about (4), it's probably best to avoid using the Indigo reflector at all for this kind of high traffic volume process.
Going to some sort of Push solution solves (1) and (2). And if you're going to use a Push solution, (3) is moot.
Is there some technical reason you can't use DDNS and port forwarding? Is your application only used on the local LAN with the Indigo server, or does it need to be usable from outside your LAN? Using a VPN to access the LAN remotely would eliminate the need for port forwarding, but has it's own issues.
Do you have a cloud server available to substitute for the Indigo Reflector? Or are you willing to pay for one? The company I use for my cloud-based MQTT server (and a few other things) costs US$5/month. Mine is in a US data center, but European data centers are available.