How Netflix microservices tackle dataset pub-sub

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

[kwhrtsk]

“At Netflix we use an in-house dataset pub/sub system called Gutenberg.”