From 069bca5eb6ae9e3877ef50c42c2d28aab037684a Mon Sep 17 00:00:00 2001 From: binhnguyennus Date: Tue, 18 Jun 2019 20:14:22 +0800 Subject: [PATCH] Event Sourcing at mytaxi --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 7a5311f..b3d6e43 100644 --- a/README.md +++ b/README.md @@ -260,6 +260,7 @@ An organized reading list for illustrating the patterns of scalable, reliable, a * [Scaling Event Sourcing for Netflix Downloads](https://www.infoq.com/presentations/netflix-scale-event-sourcing) * [Scaling Event-Sourcing at Jet.com](https://medium.com/@eulerfx/scaling-event-sourcing-at-jet-9c873cac33b8) * [Event Sourcing (2 parts) at eBay](https://www.ebayinc.com/stories/blogs/tech/event-sourcing-in-action-with-ebays-continuous-delivery-team/) + * [Event Sourcing at mytaxi](https://inside.mytaxi.com/event-sourcing-an-evolutionary-perspective-31e7387aa6f1) * [Pub-Sub Messaging](https://aws.amazon.com/pub-sub-messaging/) * [Pulsar: Pub-Sub Messaging at Scale at Yahoo](https://yahooeng.tumblr.com/post/150078336821/open-sourcing-pulsar-pub-sub-messaging-at-scale) * [Wormhole: Pub-Sub System at Facebook](https://code.facebook.com/posts/188966771280871/wormhole-pub-sub-system-moving-data-through-space-and-time/)