From 628f485a90f17c7da17d57b82874ee268bb9fb6e Mon Sep 17 00:00:00 2001 From: binhnguyennus Date: Mon, 27 May 2019 14:26:14 +0800 Subject: [PATCH] Member Transaction History Architecture at Walmart --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 0440033..8764d10 100644 --- a/README.md +++ b/README.md @@ -681,6 +681,7 @@ An organized reading list for illustrating the patterns behind scalable, reliabl * [Architecture of Following Feed, Interest Feed, and Picked For You at Pinterest](https://medium.com/@Pinterest_Engineering/building-a-dynamic-and-responsive-pinterest-7d410e99f0a9) * [API Specification Workflow at WeWork](https://engineering.wework.com/our-api-specification-workflow-9337448d6ee6) * [Media Database at Netflix](https://medium.com/netflix-techblog/implementing-the-netflix-media-database-53b5a840b42a) +* [Member Transaction History Architecture at Walmart](https://medium.com/walmartlabs/member-transaction-history-architecture-8b6e34b87c21) * [Architectures of Finance and Banking Systems](https://www.sesameindia.com/images/core-banking-system-architecture) * [Reference Architecture For The Open Banking Standard](https://hortonworks.com/blog/reference-architecture-open-banking-standard/) * [Bank Backend at Monzo](https://monzo.com/blog/2016/09/19/building-a-modern-bank-backend/)