3 ms·
Given what I've seen in practice with companies that try to follow this architecture, I can't say I'm very surprised. This type of architecture is really only
by claytongulick 7y ago
Given what I've seen in practice with companies that try to follow this architecture, I can't say I'm very surprised.
This type of architecture is really only suitable for a narrow problem domain, imho. Most people that I've seen attempt it don't understand all of the edge cases that arise from it.
For example, not getting immediate success or failure status from an API call, and having to constantly poll to see what the status of a submitted message is.
- nickserv 7y agoI think an event based system can apply to a wide variety of domains, but that the consequences need to be understood up front. This means doing things differently than the traditional top down controller approach with synchronous responses. For example, an asynchronous API should have a way of pushing notifications to the caller, and the caller then has a way of processing these returns.