Member-only story
Implement Event-driven Architecture With Minimal Effort
Temporal coupling is the most overlooked pitfall
Last time, we explained that temporal coupling can be effectively solved through event-driven architecture. Among them, we discussed the three approaches separately. Starting with the lowest reliability, simply using the event emitter can solve most of the cases with the least effort; secondly, in order to further improve the reliability, a message queue can be introduced to ensure that the event will be executed at least once. Finally, implement event sourcing to ensure that events are not lost at all.
Nevertheless, in organizations with some resource constraints, message queues seem to be out of reach. The resources here include human resources and organizational budget, whether there is no extra manpower to maintain a new messaging service or no extra funds to start a messaging service. Message queuing is one of the high price systems in restricted organizations.
Therefore, in this article, I will introduce how to achieve decoupling through event-driven architecture with minimal resources.
System Overview
Why this topic is born? Because one of our products belongs to this restricted organization. Therefore, in the process of system evolution, we gradually…
