If services are calling back into a domain to get information a lot, you may as well not use EDA at all,. Your domains are too tightly coupled to get any benefit from EDA if they cannot operate independently
@@Tony-dp1rl if each system can run independently, you might as well not use EDA, because event subscriptions are all about dependency trees. If there are no dependencies between systems, you might as well just call each system on its own from the client.
This stuff of microservices with EDA seems like a good idea to "fix" the issue with maintaining monolithic systems but they had soooo much accidental complexity that makes one wonder what's the point...
Nicely done. Like the pace and energy of Mathew's presentation style.
Illuminating. Informative. High Quality. High Density Value Delivered!
This talks is excellent and it has been featured in the last issue of Tech Talks Weekly newsletter 🎉
Congrats Matthew!
If services are calling back into a domain to get information a lot, you may as well not use EDA at all,. Your domains are too tightly coupled to get any benefit from EDA if they cannot operate independently
@@Tony-dp1rl if each system can run independently, you might as well not use EDA, because event subscriptions are all about dependency trees. If there are no dependencies between systems, you might as well just call each system on its own from the client.
This stuff of microservices with EDA seems like a good idea to "fix" the issue with maintaining monolithic systems but they had soooo much accidental complexity that makes one wonder what's the point...