3 ms·
For my use case, I see Pushpin or something like it being more of a server that handles client connections, auth, and routing. Kinda like a super load balancer.
by rpedela 13y ago
For my use case, I see Pushpin or something like it being more of a server that handles client connections, auth, and routing. Kinda like a super load balancer. Then you could have a normal load balancer in the front to give clients a single IP to connect to. The whole point being to reduce load on the app server, DB, etc by performing logic (auth, basic validation) that must be performed on every request.
I can understand if that is not the goal of the project since the main focus seems to be realtime over HTTP.
- jkarneges 13y agoI have been considering some special auth support. For example, there could be rules like "if an Authentication header is identical for multiple requests, then assume it is from the same authenticated user entity without necessarily forwarding the request to the origin server again". This alone doesn't buy you anything, but it could be used as the basis of further rules such as a cache layer that caches per-user. These ideas are not totally baked but could help in reducing load to the backend servers, which falls in line with Pushpin's goals.
- rpedela 13y agoSounds great. Definitely an interesting project that I will keep my eye on. Yes I am a cyclops... :)