5 ms·
I'm already maintaining an application written 15 years ago which is almost like this. It's in C++ but it's like they thought they were writing Erlang (without
by phaedrus 6y ago
I'm already maintaining an application written 15 years ago which is almost like this. It's in C++ but it's like they thought they were writing Erlang (without the tools or language support). Every task from the most trivial to the most complex is a separate thread using Windows messages to communicate. It's impossible to follow the plot to understand what is going on because the thread of execution disappears with ever message post to be picked up by a message receive somewhere else. The messages are globally sent/received so there's not even a channel receiver to look for everyone is a sender and receiver peeing in the same pool.
At least it's all in one process / one codebase.
- hinkley 6y agoI had somewhat similar experience with event-driven systems. I figured microservices would flame out a lot faster as they ran into the same class of problems. We do have some slightly better for managing the logistics though. Small force multipliers can add up to quite a lot in aggregate.