Downstream systems need master changes within minutes, while a reporting warehouse can wait overnight. How should master distribution be designed?
Select an answer to reveal the explanation.
Short Explanation
Not every consumer needs the same delivery truck. Event publish for systems that can’t wait; nightly files for ones that can.
Full Explanation
Integration style should match consumer latency and reliability needs: event publication for near-real-time use cases and batch distribution where overnight freshness suffices. One weekly file for all, manual re-keying, or steward email CSVs are brittle and misaligned patterns.