We’re developing a location-based service where clients will ping their location to the server every 30 seconds. This means a lot of pings from a lot of clients.
In general, I would say that REST is better for these kind of use cases, as it does not require a permanent connection. On the other hand, there is some overhead for the TCP connection itself, and for security reasons, it would be better if the client was authenticated (for REST, we could use a kind of token for this, but this would have to be checked as well).
So the more general question is: how big is the overhead on the server side for a pure DDP WebSockets connection? We’re not planning to use subscription, just client => server pings.