By Ammar Khaku IntroductionIn a microservice architecture such as Netflix’s, propagating datasets from a single source to multiple downstream destinations can be challenging. These datasets can represent anything from service configuration to the results of a batch job, are often needed in-memory to optimize access and must be updated as they change over time. One example displaying the need for d
![How Netflix microservices tackle dataset pub-sub](https://cdn-ak-scissors.b.st-hatena.com/image/square/f7b14b6db0b78866fba5462054675b6bca4e2f77/height=288;version=1;width=512/https%3A%2F%2Fmiro.medium.com%2Fv2%2Fresize%3Afit%3A537%2F1%2ARowLptXJ7n29ZF_mWepmKg.png)