Overview

When we start learning about microservices architecture (and more specifically, event-driven architectures) two very important principles are quickly introduced: service autonomy and asynchronous communication.

As we start developing new interactions between services we soon find out that, in order to comply with the first principle, we need to store local copies (or views) of data that is owned by external services. Asynchronous communication adds another layer of complexity on this matter, specially when our service requries old data, and the events that notified the system about that data are long gone.

Continue reading: DataGathering