You probably mentioned it in the full video, but although this is applicable for any application, keeping the code small and as simple as possible should be the main goal. This solution is good when the coupling interferes with complex business logic and thus causing: bugs, slow development, performance bottleneck.
The title is misleading since the video doesn't directly address any aspect of async or message-based architecture - for a person that doesn't have a priori knowledge of RabbitMQ or async design in general, this video will, at best, confuse them further. A more informative approach might be to split this video into multiple parts: one that covers the single responsibility principle, one that covers asynchronicity and a final one that explains how RabbitMQ can be used to handle the previous two in a very specific scenario
You probably mentioned it in the full video, but although this is applicable for any application, keeping the code small and as simple as possible should be the main goal. This solution is good when the coupling interferes with complex business logic and thus causing: bugs, slow development, performance bottleneck.
Wow nice topic. Could you please let me know where I can get the full video...!
Here: th-cam.com/video/KkmuCRAqEdI/w-d-xo.html
The title is misleading since the video doesn't directly address any aspect of async or message-based architecture - for a person that doesn't have a priori knowledge of RabbitMQ or async design in general, this video will, at best, confuse them further.
A more informative approach might be to split this video into multiple parts: one that covers the single responsibility principle, one that covers asynchronicity and a final one that explains how RabbitMQ can be used to handle the previous two in a very specific scenario