17 ms·
Hehe, this is very familiar territory. I worked with a team that were making quite a complex multi-part network manager some years ago. Development was going t
by Nursie 10y ago
Hehe, this is very familiar territory.
I worked with a team that were making quite a complex multi-part network manager some years ago. Development was going to be superfast because the lead developer had come up with this new framework (red flag! red flag!) based on publishing events and then subscribers picking them up and acting on them.
The problems began when the subsystem running user interaction started to need replies to specific things so it could tell what was going on with specific user interactions. Then message timeouts where needed so that pieces could react if their response didn't manifest in time.
What this framework unintentionally did, I cynically worked out after a while, was implement UDP multicast over TCP.
What I was watching happen, each time messaging problems come up, was the reimplementation of TCP on top of that. That's about when I bailed!
- mdpopescu 10y ago... damn. I'm a fan of message-driven systems (in theory, never actually worked on them in practice), but I will admit that "UDP multicast over TCP" sounds like a very appropriate description. I need to think about it some more :)
- Nursie 10y agoWell if it's any consolation I don't think it's inevitable, just something to watch out for. In this case I think the problem and solution domains were poorly mapped.