Hacker News new | past | comments | ask | show | jobs | submit login

The author lays out a dozen different, terrible ways to discover services, only one of which is even remotely suitable. I associate that kind of stream-of-consciousness documentation with people who are making it up as they go along.

Anyway, the proposed solution of a full-mesh FE-to-BE heartbeat network over UDP, switching to TCP in case of idleness, is not going to scale. That just guarantees that you are going to run out of file descriptors in case of a packet loss event, as everyone upgrades their heartbeat protocol to TCP.




What, in your opinion, is the correct way to implement heartbeats in such a message oriented system?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: