3 ms·
Very cool service! Question about the architecture though: what were the reasons for using HTTP as opposed to UDP (which is typically how these stats collectio
by nhashem 14y ago
Very cool service!
Question about the architecture though: what were the reasons for using HTTP as opposed to UDP (which is typically how these stats collection servers receive data)? It looks like it's possible to keep system load manageable since you aggregate the data and space out the HTTP requests, but why do this instead of just blasting the server with UDP requests?
- spolu 14y agoSince we are cloud-based, our servers are remote to our customers'... and since there's no UDP availability over WAN... Then we had to find a solution to make it work nicely with HTTP. Does it make sense?
- theatrus2 14y agoSince when does UDP not work over a WAN/the internet?
- spolu 14y agoDefinitely talked too fast! You're right, it definitely works. It's a little bit shadier on WAN but the main reason for the pre-aggregation is that the fire+forget behavior is much harder to scale as a service and would wastefully cost a lot of WAN bandwidth. Once you have a pre-aggregation and only periodic updates... UDP does not make sense anymore. HTTP also good for browser clients which could make sense.