Re:Reactive Cloud Actors: No-nonsense micro-services
by mamcx on Sunday April 13, 2014 @09:28PM
(#7584039)
Exactly. Sometimes is necessary to step into the call of another function/actor, see what is is doing, note is necessary to step into more into a deeper function, etc.
Or stop when a certain value arrive, and inspect the code. If this could be done with actor/csp, then is good idea to jump onto it.
No. No, this is terrifyingly incorrect. Making each component do the right thing in isolation is easy. Most of the difficulty in systems - in developing, testing, and debugging them - arises from what the components do when they're together, because it turns out your ideas about how they need to behave in isolation were mistaken.