[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-446":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":10,"languages":10,"totalLinesOfCode":10,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":46,"readmeContent":47,"aiSummary":48,"trendingCount":15,"starSnapshotCount":15,"syncStatus":49,"lastSyncTime":50,"discoverSource":51},446,"awesome-scalability","binhnguyennus\u002Fawesome-scalability","binhnguyennus","The Patterns of Scalable, Reliable, and Performant Large-Scale Systems","",null,71654,7013,1886,21,0,27,209,695,111,45,"MIT License",false,"master",true,[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"architecture","awesome","awesome-list","backend","big-data","computer-science","design-patterns","devops","distributed-systems","interview","interview-practice","interview-questions","lists","machine-learning","programming","resources","scalability","system","system-design","web-development","2026-06-12 02:00:13","[![Logo](\u002Flogo.png)](http:\u002F\u002Fawesome-scalability.com\u002F)\n\nAn updated and organized reading list for illustrating the patterns of scalable, reliable, and performant large-scale systems. Concepts are explained in the articles of prominent engineers and credible references. Case studies are taken from battle-tested systems that serve millions to billions of users.\n\n#### If your system goes slow\n> Understand your problems: scalability problem (fast for a single user but slow under heavy load) or performance problem (slow for a single user) by reviewing some [design principles](#principle) and checking how [scalability](#scalability) and [performance](#performance) problems are solved at tech companies. The section of [intelligence](#intelligence) are created for those who work with data and machine learning at big (data) and deep (learning) scale.\n\n#### If your system goes down\n> \"Even if you lose all one day, you can build all over again if you retain your calm!\" - Thuan Pham, former CTO of Uber. So, keep calm and mind the [availability](#availability) and [stability](#stability) matters! \n\n#### If you are having a system design interview\n> Look at some [interview notes](#interview) and [real-world architectures with completed diagrams](#architecture) to get a comprehensive view before designing your system on whiteboard. You can check some [talks](#talk) of engineers from tech giants to know how they build, scale, and optimize their systems. Good luck!\n\n#### If you are building your dream team\n> The goal of scaling team is not growing team size but increasing team output and value. You can find out how tech companies reach that goal in various aspects: hiring, management, organization, culture, and communication in the [organization](#organization) section.\n\n#### Community power\n\n> Contributions are greatly welcome! You may want to take a look at the [contribution guidelines](CONTRIBUTING.md). If you see a link here that is no longer maintained or is not a good fit, please submit a pull request!\n\n> Many long hours of hard work have gone into this project. If you find it helpful, please share on Facebook, [on Twitter](https:\u002F\u002Fctt.ec\u002FV8B2p), [on Weibo](http:\u002F\u002Ft.cn\u002FRnjFLCB), or on your chat groups! Knowledge is power, knowledge shared is power multiplied. Thank you!\n\n## Content\n- [Principle](#principle)\n- [Scalability](#scalability)\n- [Availability](#availability)\n- [Stability](#stability)\n- [Performance](#performance)\n- [Intelligence](#intelligence)\n- [Architecture](#architecture)\n- [Interview](#interview)\n- [Organization](#organization)\n- [Talk](#talk)\n- [Book](#book)\n\n## Principle\n* [Lessons from Giant-Scale Services - Eric Brewer, UC Berkeley & Google](https:\u002F\u002Fpeople.eecs.berkeley.edu\u002F~brewer\u002Fpapers\u002FGiantScale-IEEE.pdf)\n* [Designs, Lessons and Advice from Building Large Distributed Systems - Jeff Dean, Google](https:\u002F\u002Fwww.cs.cornell.edu\u002Fprojects\u002Fladis2009\u002Ftalks\u002Fdean-keynote-ladis2009.pdf)\n* [How to Design a Good API & Why it Matters - Joshua Bloch, CMU & Google](https:\u002F\u002Fwww.infoq.com\u002Fpresentations\u002Feffective-api-design)\n* [On Efficiency, Reliability, Scaling - James Hamilton, VP at AWS](http:\u002F\u002Fmvdirona.com\u002Fjrh\u002Fwork\u002F)\n* [Principles of Chaos Engineering](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon17americas\u002Fprogram\u002Fpresentation\u002Frosenthal)\n* [Finding the Order in Chaos](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon16\u002Fprogram\u002Fpresentation\u002Flueder)\n* [The Twelve-Factor App](https:\u002F\u002F12factor.net\u002F)\n* [Clean Architecture](https:\u002F\u002Fblog.cleancoder.com\u002Funcle-bob\u002F2012\u002F08\u002F13\u002Fthe-clean-architecture.html)\n* [High Cohesion and Low Coupling](http:\u002F\u002Fwww.math-cs.gordon.edu\u002Fcourses\u002Fcs211\u002Flectures-2009\u002FCohesion,Coupling,MVC.pdf)\n* [Monoliths and Microservices](https:\u002F\u002Fmedium.com\u002F@SkyscannerEng\u002Fmonoliths-and-microservices-8c65708c3dbf)\n* [CAP Theorem and Trade-offs](http:\u002F\u002Frobertgreiner.com\u002F2014\u002F08\u002Fcap-theorem-revisited\u002F)\n* [CP Databases and AP Databases](https:\u002F\u002Fblog.andyet.com\u002F2014\u002F10\u002F01\u002Fright-database)\n* [Stateless vs Stateful Scalability](http:\u002F\u002Fithare.com\u002Fscaling-stateful-objects\u002F)\t\n* [Scale Up vs Scale Out: Hidden Costs](https:\u002F\u002Fblog.codinghorror.com\u002Fscaling-up-vs-scaling-out-hidden-costs\u002F)\n* [ACID and BASE](https:\u002F\u002Fneo4j.com\u002Fblog\u002Facid-vs-base-consistency-models-explained\u002F)\n* [Blocking\u002FNon-Blocking and Sync\u002FAsync](https:\u002F\u002Fblogs.msdn.microsoft.com\u002Fcsliu\u002F2009\u002F08\u002F27\u002Fio-concept-blockingnon-blocking-vs-syncasync\u002F)\n* [Performance and Scalability of Databases](https:\u002F\u002Fuse-the-index-luke.com\u002Fsql\u002Ftesting-scalability)\n* [Database Isolation Levels and Effects on Performance and Scalability](http:\u002F\u002Fhighscalability.com\u002Fblog\u002F2011\u002F2\u002F10\u002Fdatabase-isolation-levels-and-their-effects-on-performance-a.html)\n* [The Probability of Data Loss in Large Clusters](https:\u002F\u002Fmartin.kleppmann.com\u002F2017\u002F01\u002F26\u002Fdata-loss-in-large-clusters.html)\n* [Data Access for Highly-Scalable Solutions: Using SQL, NoSQL, and Polyglot Persistence](https:\u002F\u002Fdocs.microsoft.com\u002Fen-us\u002Fprevious-versions\u002Fmsp-n-p\u002Fdn271399(v=pandp.10))\n* [SQL vs NoSQL](https:\u002F\u002Fwww.upwork.com\u002Fhiring\u002Fdata\u002Fsql-vs-nosql-databases-whats-the-difference\u002F)\n* [SQL vs NoSQL - Lesson Learned at Salesforce](https:\u002F\u002Fengineering.salesforce.com\u002Fsql-or-nosql-9eaf1d92545b)\n* [NoSQL Databases: Survey and Decision Guidance](https:\u002F\u002Fmedium.baqend.com\u002Fnosql-databases-a-survey-and-decision-guidance-ea7823a822d)\n* [How Sharding Works](https:\u002F\u002Fmedium.com\u002F@jeeyoungk\u002Fhow-sharding-works-b4dec46b3f6)\n* [Consistent Hashing](http:\u002F\u002Fwww.tom-e-white.com\u002F2007\u002F11\u002Fconsistent-hashing.html)\n* [Consistent Hashing: Algorithmic Tradeoffs](https:\u002F\u002Fmedium.com\u002F@dgryski\u002Fconsistent-hashing-algorithmic-tradeoffs-ef6b8e2fcae8)\n* [Don’t be tricked by the Hashing Trick](https:\u002F\u002Fbooking.ai\u002Fdont-be-tricked-by-the-hashing-trick-192a6aae3087)\n* [Uniform Consistent Hashing at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fdistributing-content-to-open-connect-3e3e391d4dc9)\n* [Eventually Consistent - Werner Vogels, CTO at Amazon](https:\u002F\u002Fwww.allthingsdistributed.com\u002F2008\u002F12\u002Feventually_consistent.html)\n* [Cache is King](https:\u002F\u002Fwww.stevesouders.com\u002Fblog\u002F2012\u002F10\u002F11\u002Fcache-is-king\u002F)\n* [Anti-Caching](https:\u002F\u002Fwww.the-paper-trail.org\u002Fpost\u002F2014-06-06-paper-notes-anti-caching\u002F)\n* [Understand Latency](http:\u002F\u002Fhighscalability.com\u002Flatency-everywhere-and-it-costs-you-sales-how-crush-it)\n* [Latency Numbers Every Programmer Should Know](http:\u002F\u002Fnorvig.com\u002F21-days.html#answers)\n* [The Calculus of Service Availability](https:\u002F\u002Fqueue.acm.org\u002Fdetail.cfm?id=3096459&__s=dnkxuaws9pogqdnxmx8i)\n* [Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO](http:\u002F\u002Fhighscalability.com\u002Fblog\u002F2014\u002F5\u002F12\u002F4-architecture-issues-when-scaling-web-applications-bottlene.html)\t\n* [Common Bottlenecks](http:\u002F\u002Fhighscalability.com\u002Fblog\u002F2012\u002F5\u002F16\u002Fbig-list-of-20-common-bottlenecks.html)\n* [Life Beyond Distributed Transactions](https:\u002F\u002Fqueue.acm.org\u002Fdetail.cfm?id=3025012)\n* [Relying on Software to Redirect Traffic Reliably at Various Layers](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon15\u002Fprogram\u002Fpresentation\u002Ftaveira)\n* [Breaking Things on Purpose](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon17americas\u002Fprogram\u002Fpresentation\u002Fandrus)\n* [Avoid Over Engineering](https:\u002F\u002Fmedium.com\u002F@rdsubhas\u002F10-modern-software-engineering-mistakes-bc67fbef4fc8)\n* [Scalability Worst Practices](https:\u002F\u002Fwww.infoq.com\u002Farticles\u002Fscalability-worst-practices)\n* [Use Solid Technologies - Don’t Re-invent the Wheel - Keep It Simple!](https:\u002F\u002Fmedium.com\u002F@DataStax\u002Finstagram-engineerings-3-rules-to-a-scalable-cloud-application-architecture-c44afed31406)\n* [Simplicity by Distributing Complexity](https:\u002F\u002Fengineering.zalando.com\u002Fposts\u002F2018\u002F01\u002Fsimplicity-by-distributing-complexity.html)\n* [Why Over-Reusing is Bad](http:\u002F\u002Ftech.transferwise.com\u002Fwhy-over-reusing-is-bad\u002F)\n* [Performance is a Feature](https:\u002F\u002Fblog.codinghorror.com\u002Fperformance-is-a-feature\u002F)\n* [Make Performance Part of Your Workflow](https:\u002F\u002Fcodeascraft.com\u002F2014\u002F12\u002F11\u002Fmake-performance-part-of-your-workflow\u002F)\n* [The Benefits of Server Side Rendering over Client Side Rendering](https:\u002F\u002Fmedium.com\u002Fwalmartlabs\u002Fthe-benefits-of-server-side-rendering-over-client-side-rendering-5d07ff2cefe8)\n* [Automate and Abstract: Lessons at Facebook](https:\u002F\u002Farchitecht.io\u002Flessons-from-facebook-on-engineering-for-scale-f5716f0afc7a)\n* [AWS Do's and Don'ts](https:\u002F\u002F8thlight.com\u002Fblog\u002Fsarah-sunday\u002F2017\u002F09\u002F15\u002Faws-dos-and-donts.html)\n* [(UI) Design Doesn’t Scale - Stanley Wood, Design Director at Spotify](https:\u002F\u002Fmedium.com\u002F@hellostanley\u002Fdesign-doesnt-scale-4d81e12cbc3e)\n* [Linux Performance](http:\u002F\u002Fwww.brendangregg.com\u002Flinuxperf.html)\n* [Building Fast and Resilient Web Applications - Ilya Grigorik](https:\u002F\u002Fwww.igvita.com\u002F2016\u002F05\u002F20\u002Fbuilding-fast-and-resilient-web-applications\u002F)\n* [Accept Partial Failures, Minimize Service Loss](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon17asia\u002Fprogram\u002Fpresentation\u002Fwang_daxin)\n* [Design for Resiliency](http:\u002F\u002Fhighscalability.com\u002Fblog\u002F2012\u002F12\u002F31\u002Fdesigning-for-resiliency-will-be-so-2013.html)\n* [Design for Self-healing](https:\u002F\u002Fdocs.microsoft.com\u002Fen-us\u002Fazure\u002Farchitecture\u002Fguide\u002Fdesign-principles\u002Fself-healing)\n* [Design for Scaling Out](https:\u002F\u002Fdocs.microsoft.com\u002Fen-us\u002Fazure\u002Farchitecture\u002Fguide\u002Fdesign-principles\u002Fscale-out)\t\n* [Design for Evolution](https:\u002F\u002Fdocs.microsoft.com\u002Fen-us\u002Fazure\u002Farchitecture\u002Fguide\u002Fdesign-principles\u002Fdesign-for-evolution)\n* [Learn from Mistakes](http:\u002F\u002Fhighscalability.com\u002Fblog\u002F2013\u002F8\u002F26\u002Freddit-lessons-learned-from-mistakes-made-scaling-to-1-billi.html)\n\n## Scalability\n* [Microservices and Orchestration](https:\u002F\u002Fmartinfowler.com\u002Fmicroservices\u002F)\n\t* [Domain-Oriented Microservice Architecture at Uber](https:\u002F\u002Feng.uber.com\u002Fmicroservice-architecture\u002F)\n\t* [Service Architecture (3 parts: Domain Gateways, Value-Added Services, BFF) at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Fservice-architecture-3)\n\t* [Container (8 parts) at Riot Games](https:\u002F\u002Fengineering.riotgames.com\u002Fnews\u002Fthinking-inside-container)\n\t* [Containerization at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fcontainerization-at-pinterest-92295347f2f3)\n\t* [Evolution of Container Usage at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fthe-evolution-of-container-usage-at-netflix-3abfc096781b)\n\t* [Dockerizing MySQL at Uber](https:\u002F\u002Feng.uber.com\u002Fdockerizing-mysql\u002F)\n\t* [Testing of Microservices at Spotify](https:\u002F\u002Flabs.spotify.com\u002F2018\u002F01\u002F11\u002Ftesting-of-microservices\u002F)\n\t* [Docker in Production at Treehouse](https:\u002F\u002Fmedium.com\u002Ftreehouse-engineering\u002Flessons-learned-running-docker-in-production-5dce99ece770)\n\t* [Microservice at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Finside-a-soundcloud-microservice)\n\t* [Operate Kubernetes Reliably at Stripe](https:\u002F\u002Fstripe.com\u002Fblog\u002Foperating-kubernetes)\n\t* [Cross-Cluster Traffic Mirroring with Istio at Trivago](https:\u002F\u002Ftech.trivago.com\u002F2020\u002F06\u002F10\u002Fcross-cluster-traffic-mirroring-with-istio\u002F)\n\t* [Agrarian-Scale Kubernetes (3 parts) at New York Times](https:\u002F\u002Fopen.nytimes.com\u002Fagrarian-scale-kubernetes-part-3-ee459887ed7e)\n\t* [Nanoservices at BBC](https:\u002F\u002Fmedium.com\u002Fbbc-design-engineering\u002Fpowering-bbc-online-with-nanoservices-727840ba015b)\n\t* [PowerfulSeal: Testing Tool for Kubernetes Clusters at Bloomberg](https:\u002F\u002Fwww.techatbloomberg.com\u002Fblog\u002Fpowerfulseal-testing-tool-kubernetes-clusters\u002F)\n\t* [Conductor: Microservices Orchestrator at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fnetflix-conductor-a-microservices-orchestrator-2e8d4771bf40)\n\t* [Docker Containers that Power Over 100.000 Online Shops at Shopify](https:\u002F\u002Fshopifyengineering.myshopify.com\u002Fblogs\u002Fengineering\u002Fdocker-at-shopify-how-we-built-containers-that-power-over-100-000-online-shops)\n\t* [Microservice Architecture at Medium](https:\u002F\u002Fmedium.engineering\u002Fmicroservice-architecture-at-medium-9c33805eb74f)\n\t* [From bare-metal to Kubernetes at Betabrand](https:\u002F\u002Fboxunix.com\u002Fpost\u002Fbare_metal_to_kube\u002F)\n\t* [Kubernetes at Tinder](https:\u002F\u002Fmedium.com\u002Ftinder-engineering\u002Ftinders-move-to-kubernetes-cda2a6372f44)\n\t* [Kubernetes at Quora](https:\u002F\u002Fwww.quora.com\u002Fq\u002Fquoraengineering\u002FAdopting-Kubernetes-at-Quora)\t\n\t* [Kubernetes Platform at Pinterest](https:\u002F\u002Fmedium.com\u002Fpinterest-engineering\u002Fbuilding-a-kubernetes-platform-at-pinterest-fb3d9571c948)\n\t* [Microservices at Nubank](https:\u002F\u002Fmedium.com\u002Fbuilding-nubank\u002Fmicroservices-at-nubank-an-overview-2ebcb336c64d)\n\t* [Payment Transaction Management in Microservices at Mercari](https:\u002F\u002Fengineering.mercari.com\u002Fen\u002Fblog\u002Fentry\u002F20210831-2019-06-07-155849\u002F)\n\t* [Service Mesh at Snap](https:\u002F\u002Feng.snap.com\u002Fmonolith-to-multicloud-microservices-snap-service-mesh)\n\t* [GRIT: Protocol for Distributed Transactions across Microservices at eBay](https:\u002F\u002Ftech.ebayinc.com\u002Fengineering\u002Fgrit-a-protocol-for-distributed-transactions-across-microservices\u002F)\n\t* [Rubix: Kubernetes at Palantir](https:\u002F\u002Fmedium.com\u002Fpalantir\u002Fintroducing-rubix-kubernetes-at-palantir-ab0ce16ea42e)\n\t* [CRISP: Critical Path Analysis for Microservice Architectures at Uber](https:\u002F\u002Feng.uber.com\u002Fcrisp-critical-path-analysis-for-microservice-architectures\u002F)\n* [Distributed Caching](https:\u002F\u002Fwww.wix.engineering\u002Fpost\u002Fscaling-to-100m-to-cache-or-not-to-cache)\n\t* [EVCache: Distributed In-memory Caching at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fcaching-for-a-global-netflix-7bcc457012f1)\n\t* [EVCache Cache Warmer Infrastructure at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fcache-warming-agility-for-a-stateful-service-2d3b1da82642)\n\t* [Memsniff: Robust Memcache Traffic Analyzer at Box](https:\u002F\u002Fblog.box.com\u002Fblog\u002Fintroducing-memsniff-robust-memcache-traffic-analyzer\u002F)\n\t* [Caching with Consistent Hashing and Cache Smearing at Etsy](https:\u002F\u002Fcodeascraft.com\u002F2017\u002F11\u002F30\u002Fhow-etsy-caches\u002F)\n\t* [Analysis of Photo Caching at Facebook](https:\u002F\u002Fcode.facebook.com\u002Fposts\u002F220956754772273\u002Fan-analysis-of-facebook-photo-caching\u002F)\n\t* [Cache Efficiency Exercise at Facebook](https:\u002F\u002Fcode.facebook.com\u002Fposts\u002F964122680272229\u002Fweb-performance-cache-efficiency-exercise\u002F)\n\t* [tCache: Scalable Data-aware Java Caching at Trivago](http:\u002F\u002Ftech.trivago.com\u002F2015\u002F10\u002F15\u002Ftcache\u002F)\n\t* [Pycache: In-process Caching at Quora](https:\u002F\u002Fquoraengineering.quora.com\u002FPycache-lightning-fast-in-process-caching)\n\t* [Reduce Memcached Memory Usage by 50% at Trivago](http:\u002F\u002Ftech.trivago.com\u002F2017\u002F12\u002F19\u002Fhow-trivago-reduced-memcached-memory-usage-by-50\u002F)\n\t* [Caching Internal Service Calls at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2018\u002F03\u002Fcaching-internal-service-calls-at-yelp.html)\n\t* [Estimating the Cache Efficiency using Big Data at Allegro](https:\u002F\u002Fallegro.tech\u002F2017\u002F01\u002Festimating-the-cache-efficiency-using-big-data.html)\n\t* [Distributed Cache at Zalando](https:\u002F\u002Fengineering.zalando.com\u002Fposts\u002F2018\u002F04\u002Fdistributed-cache-akka-kubernetes.html)\n\t* [Distributed Cache for S3 at ClickHouse](https:\u002F\u002Fclickhouse.com\u002Fblog\u002Fbuilding-a-distributed-cache-for-s3)\n\t* [Application Data Caching from RAM to SSD at NetFlix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fevolution-of-application-data-caching-from-ram-to-ssd-a33d6fa7a690)\n\t* [Tradeoffs of Replicated Cache at Skyscanner](https:\u002F\u002Fmedium.com\u002F@SkyscannerEng\u002Fthe-tradeoffs-of-a-replicated-cache-b6680c722f58)\n\t* [Location Caching with Quadtrees at Yext](http:\u002F\u002Fengblog.yext.com\u002Fpost\u002Fgeolocation-caching)\n\t* [Video Metadata Caching at Vimeo](https:\u002F\u002Fmedium.com\u002Fvimeo-engineering-blog\u002Fvideo-metadata-caching-at-vimeo-a54b25f0b304)\n\t* [Scaling Redis at Twitter](http:\u002F\u002Fhighscalability.com\u002Fblog\u002F2014\u002F9\u002F8\u002Fhow-twitter-uses-redis-to-scale-105tb-ram-39mm-qps-10000-ins.html)\n\t* [Scaling Job Queue with Redis at Slack](https:\u002F\u002Fslack.engineering\u002Fscaling-slacks-job-queue-687222e9d100)\n\t* [Moving persistent data out of Redis at Github](https:\u002F\u002Fgithubengineering.com\u002Fmoving-persistent-data-out-of-redis\u002F)\n\t* [Storing Hundreds of Millions of Simple Key-Value Pairs in Redis at Instagram](https:\u002F\u002Fengineering.instagram.com\u002Fstoring-hundreds-of-millions-of-simple-key-value-pairs-in-redis-1091ae80f74c)\n\t* [Redis at Trivago](http:\u002F\u002Ftech.trivago.com\u002F2017\u002F01\u002F25\u002Flearn-redis-the-hard-way-in-production\u002F)\n\t* [Optimizing Redis Storage at Deliveroo](https:\u002F\u002Fdeliveroo.engineering\u002F2017\u002F01\u002F19\u002Foptimising-membership-queries.html)\n\t* [Memory Optimization in Redis at Wattpad](http:\u002F\u002Fengineering.wattpad.com\u002Fpost\u002F23244724794\u002Fstore-more-stuff-memory-optimization-in-redis)\n\t* [Redis Fleet at Heroku](https:\u002F\u002Fblog.heroku.com\u002Frolling-redis-fleet)\n\t* [Solving Remote Build Cache Misses (2 parts) at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Fgradle-remote-build-cache-misses-part-2)\n\t* [Ratings & Reviews (2 parts) at Flipkart](https:\u002F\u002Fblog.flipkart.tech\u002Fratings-reviews-flipkart-part-2-574ab08e75cf)\n\t* [Prefetch Caching of Items at eBay](https:\u002F\u002Ftech.ebayinc.com\u002Fengineering\u002Fprefetch-caching-of-ebay-items\u002F)\n\t* [Cross-Region Caching Library at Wix](https:\u002F\u002Fwww.wix.engineering\u002Fpost\u002Fhow-we-built-a-cross-region-caching-library)\n\t* [Improving Distributed Caching Performance and Efficiency at Pinterest](https:\u002F\u002Fmedium.com\u002Fpinterest-engineering\u002Fimproving-distributed-caching-performance-and-efficiency-at-pinterest-92484b5fe39b)\n\t* [Standardize and Improve Microservices Caching at DoorDash](https:\u002F\u002Fdoordash.engineering\u002F2023\u002F10\u002F19\u002Fhow-doordash-standardized-and-improved-microservices-caching\u002F)\n    * [HTTP Caching and CDN](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FCaching)\n        * [Zynga Geo Proxy: Reducing Mobile Game Latency at Zynga](https:\u002F\u002Fwww.zynga.com\u002Fblogs\u002Fengineering\u002Fzynga-geo-proxy-reducing-mobile-game-latency)\n        * [Google AMP at Condé Nast](https:\u002F\u002Ftechnology.condenast.com\u002Fstory\u002Fthe-why-and-how-of-google-amp-at-conde-nast)\n        * [A\u002FB Tests on Hosting Infrastructure (CDNs) at Deliveroo](https:\u002F\u002Fdeliveroo.engineering\u002F2016\u002F09\u002F19\u002Fab-testing-cdns.html)\n        * [HAProxy with Kubernetes for User-facing Traffic at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Fhow-soundcloud-uses-haproxy-with-kubernetes-for-user-facing-traffic)\n        * [Bandaid: Service Proxy at Dropbox](https:\u002F\u002Fdropbox.tech\u002Finfrastructure\u002Fmeet-bandaid-the-dropbox-service-proxy)\n\t\t* [Service Workers at Slack](https:\u002F\u002Fslack.engineering\u002Fservice-workers-at-slack-our-quest-for-faster-boot-times-and-offline-support-3492cf79c88)\n\t\t* [CDN Services at Spotify](https:\u002F\u002Flabs.spotify.com\u002F2020\u002F02\u002F24\u002Fhow-spotify-aligned-cdn-services-for-a-lightning-fast-streaming-experience\u002F)\n* [Distributed Locking](https:\u002F\u002Fmartin.kleppmann.com\u002F2016\u002F02\u002F08\u002Fhow-to-do-distributed-locking.html)\n\t* [Chubby: Lock Service for Loosely Coupled Distributed Systems at Google](https:\u002F\u002Fblog.acolyer.org\u002F2015\u002F02\u002F13\u002Fthe-chubby-lock-service-for-loosely-coupled-distributed-systems\u002F)\n\t* [Distributed Locking at Uber](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=MDuagr729aU)\n\t* [Distributed Locks using Redis at GoSquared](https:\u002F\u002Fengineering.gosquared.com\u002Fdistributed-locks-using-redis)\n\t* [ZooKeeper at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Ftopics\u002Finfrastructure\u002F2018\u002Fzookeeper-at-twitter.html)\n\t* [Eliminating Duplicate Queries using Distributed Locking at Chartio](https:\u002F\u002Fchartio.com\u002Fblog\u002Feliminating-duplicate-queries-using-distributed-locking\u002F)\n* [Distributed Tracking, Tracing, and Measuring](https:\u002F\u002Fwww.oreilly.com\u002Fideas\u002Funderstanding-the-value-of-distributed-tracing)\n\t* [Zipkin: Distributed Systems Tracing at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Fa\u002F2012\u002Fdistributed-systems-tracing-with-zipkin.html)\n\t* [Improve Zipkin Traces using Kubernetes Pod Metadata at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Fusing-kubernetes-pod-metadata-to-improve-zipkin-traces)\n\t* [Canopy: Scalable Distributed Tracing & Analysis at Facebook](https:\u002F\u002Fwww.infoq.com\u002Fpresentations\u002Fcanopy-scalable-tracing-analytics-facebook)\n\t* [Pintrace: Distributed Tracing at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fdistributed-tracing-at-pinterest-with-new-open-source-tools-a4f8a5562f6b)\n\t* [XCMetrics: All-in-One Tool for Tracking Xcode Build Metrics at Spotify](https:\u002F\u002Fengineering.atspotify.com\u002F2021\u002F01\u002F20\u002Fintroducing-xcmetrics-our-all-in-one-tool-for-tracking-xcode-build-metrics\u002F)\n\t* [Real-time Distributed Tracing at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fdistributed-service-call-graph\u002Freal-time-distributed-tracing-website-performance-and-efficiency)\t\n\t* [Tracking Service Infrastructure at Scale at Shopify](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon17americas\u002Fprogram\u002Fpresentation\u002Farthorne)\t\n\t* [Distributed Tracing at HelloFresh](https:\u002F\u002Fengineering.hellofresh.com\u002Fscaling-hellofresh-distributed-tracing-7b182928247d)\n\t* [Analyzing Distributed Trace Data at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fanalyzing-distributed-trace-data-6aae58919949)\n\t* [Distributed Tracing at Uber](https:\u002F\u002Feng.uber.com\u002Fdistributed-tracing\u002F)\n\t* [JVM Profiler: Tracing Distributed JVM Applications at Uber](https:\u002F\u002Feng.uber.com\u002Fjvm-profiler\u002F)\n\t* [Data Checking at Dropbox](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon17asia\u002Fprogram\u002Fpresentation\u002Fmah)\n\t* [Tracing Distributed Systems at Showmax](https:\u002F\u002Ftech.showmax.com\u002F2016\u002F10\u002Ftracing-distributed-systems-at-showmax\u002F)\n\t* [osquery Across the Enterprise at Palantir](https:\u002F\u002Fmedium.com\u002F@palantir\u002Fosquery-across-the-enterprise-3c3c9d13ec55)\n\t* [StatsD at Etsy](https:\u002F\u002Fcodeascraft.com\u002F2011\u002F02\u002F15\u002Fmeasure-anything-measure-everything\u002F)\n* [Distributed Scheduling](https:\u002F\u002Fwww.csee.umbc.edu\u002Fcourses\u002Fgraduate\u002FCMSC621\u002Ffall02\u002Flectures\u002Fch11.pdf)\n\t* [Distributed Task Scheduling (3 parts) at PagerDuty](https:\u002F\u002Fwww.pagerduty.com\u002Feng\u002Fdistributed-task-scheduling-3\u002F)\n    * [Building Cron at Google](https:\u002F\u002Flanding.google.com\u002Fsre\u002Fsre-book\u002Fchapters\u002Fdistributed-periodic-scheduling\u002F)\n    * [Distributed Cron Architecture at Quora](https:\u002F\u002Fquoraengineering.quora.com\u002FQuoras-Distributed-Cron-Architecture)\n    * [Chronos: A Replacement for Cron at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fchronos-a-replacement-for-cron-f05d7d986a9d)\n    * [Scheduler at Nextdoor](https:\u002F\u002Fengblog.nextdoor.com\u002Fwe-don-t-run-cron-jobs-at-nextdoor-6f7f9cc62040)\n    * [Peloton: Unified Resource Scheduler for Diverse Cluster Workloads at Uber](https:\u002F\u002Feng.uber.com\u002Fpeloton\u002F)\n    * [Fenzo: OSS Scheduler for Apache Mesos Frameworks at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Ffenzo-oss-scheduler-for-apache-mesos-frameworks-5c340e77e543)\n    * [Airflow - Workflow Orchestration](https:\u002F\u002Fairflow.apache.org\u002F)\n\t\t* [Airflow at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fairflow-a-workflow-management-platform-46318b977fd8)\n\t\t* [Airflow at Adyen](https:\u002F\u002Fwww.adyen.com\u002Fknowledge-hub\u002Fapache-airflow-at-adyen)\n\t\t* [Airflow at Pandora](https:\u002F\u002Fengineering.pandora.com\u002Fapache-airflow-at-pandora-1d7a844d68ee)\n        * [Airflow at Robinhood](https:\u002F\u002Fmedium.com\u002Frobinhood-engineering\u002Fwhy-robinhood-uses-airflow-aed13a9a90c8)\n        * [Airflow at Lyft](https:\u002F\u002Feng.lyft.com\u002Frunning-apache-airflow-at-lyft-6e53bb8fccff)\n        * [Airflow at Drivy](https:\u002F\u002Fdrivy.engineering\u002Fairflow-architecture\u002F)\n\t\t* [Airflow at Grab](https:\u002F\u002Fengineering.grab.com\u002Fexperimentation-platform-data-pipeline)\n\t\t* [Airflow at Adobe](https:\u002F\u002Fmedium.com\u002Fadobetech\u002Fadobe-experience-platform-orchestration-service-with-apache-airflow-952203723c0b)\n        * [Auditing Airflow Job Runs at Walmart](https:\u002F\u002Fmedium.com\u002Fwalmartlabs\u002Fauditing-airflow-batch-jobs-73b45100045)\n        * [MaaT: DAG-based Distributed Task Scheduler at Alibaba](https:\u002F\u002Fhackernoon.com\u002Fmeet-maat-alibabas-dag-based-distributed-task-scheduler-7c9cf0c83438)\n        * [boundary-layer: Declarative Airflow Workflows at Etsy](https:\u002F\u002Fwww.etsy.com\u002Fcodeascraft\u002Fboundary-layer-declarative-airflow-workflows)\n* [Distributed Monitoring and Alerting](https:\u002F\u002Fwww.oreilly.com\u002Fideas\u002Fmonitoring-distributed-systems)\n\t* [Unicorn: Remediation System at eBay](https:\u002F\u002Fwww.ebayinc.com\u002Fstories\u002Fblogs\u002Ftech\u002Funicorn-rheos-remediation-center\u002F)\n\t* [M3: Metrics and Monitoring Platform at Uber](https:\u002F\u002Feng.uber.com\u002Foptimizing-m3\u002F)\n\t* [Athena: Automated Build Health Management System at Dropbox](https:\u002F\u002Fdropbox.tech\u002Finfrastructure\u002Fathena-our-automated-build-health-management-system)\n\t* [Vortex: Monitoring Server Applications at Dropbox](https:\u002F\u002Fdropbox.tech\u002Finfrastructure\u002Fmonitoring-server-applications-with-vortex)\n\t* [Nuage: Cloud Management Service at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2019\u002Fsolving-manageability-challenges-with-nuage)\n\t* [Telltale: Application Monitoring at Netflix](https:\u002F\u002Fnetflixtechblog.com\u002Ftelltale-netflix-application-monitoring-simplified-5c08bfa780ba)\n\t* [ThirdEye: Monitoring Platform at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2019\u002F06\u002Fsmart-alerts-in-thirdeye--linkedins-real-time-monitoring-platfor)\n\t* [Periskop: Exception Monitoring Service at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Fperiskop-exception-monitoring-service)\n    * [Securitybot: Distributed Alerting Bot at Dropbox](https:\u002F\u002Fdropbox.tech\u002Fsecurity\u002Fmeet-securitybot-open-sourcing-automated-security-at-scale)\n    * [Monitoring System at Alibaba](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon18asia\u002Fpresentation\u002Fxinchi)\n    * [Real User Monitoring at Dailymotion](https:\u002F\u002Fmedium.com\u002Fdailymotion\u002Freal-user-monitoring-1948375f8be5)\n    * [Alerting Ecosystem at Uber](https:\u002F\u002Feng.uber.com\u002Fobservability-at-scale\u002F)\n\t* [Alerting Framework at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Falerting-framework-at-airbnb-35ba48df894f)\n\t* [Alerting on Service-Level Objectives (SLOs) at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Falerting-on-slos)\n    * [Job-based Forecasting Workflow for Observability Anomaly Detection at Uber](https:\u002F\u002Feng.uber.com\u002Fobservability-anomaly-detection\u002F)\n\t* [Monitoring and Alert System using Graphite and Cabot at HackerEarth](http:\u002F\u002Fengineering.hackerearth.com\u002F2017\u002F03\u002F21\u002Fmonitoring-and-alert-system-using-graphite-and-cabot\u002F)\n    * [Observability (2 parts) at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Fa\u002F2016\u002Fobservability-at-twitter-technical-overview-part-ii.html)\n    * [Distributed Security Alerting at Slack](https:\u002F\u002Fslack.engineering\u002Fdistributed-security-alerting-c89414c992d6)\n    * [Real-Time News Alerting at Bloomberg](https:\u002F\u002Fwww.infoq.com\u002Fpresentations\u002Fnews-alerting-bloomberg)\n\t* [Data Pipeline Monitoring System at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2019\u002Fan-inside-look-at-linkedins-data-pipeline-monitoring-system-)\n\t* [Monitoring and Observability at Picnic](https:\u002F\u002Fblog.picnic.nl\u002Fmonitoring-and-observability-at-picnic-684cefd845c4)\n* [Distributed Security](https:\u002F\u002Fmsdn.microsoft.com\u002Fen-us\u002Flibrary\u002Fcc767123.aspx)\n\t* [Aardvark and Repokid: AWS Least Privilege for Distributed, High-Velocity Development at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fintroducing-aardvark-and-repokid-53b081bf3a7e)\t\n\t* [LISA: Distributed Firewall at LinkedIn](https:\u002F\u002Fwww.slideshare.net\u002FMikeSvoboda\u002F2017-lisa-linkedins-distributed-firewall-dfw)\n\t* [Secure Infrastructure To Store Bitcoin In The Cloud at Coinbase](https:\u002F\u002Fengineering.coinbase.com\u002Fhow-coinbase-builds-secure-infrastructure-to-store-bitcoin-in-the-cloud-30a6504e40ba)\n\t* [BinaryAlert: Real-time Serverless Malware Detection at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fbinaryalert-real-time-serverless-malware-detection-ca44370c1b90)\n\t* [Scalable IAM Architecture to Secure Access to 100 AWS Accounts at Segment](https:\u002F\u002Fsegment.com\u002Fblog\u002Fsecure-access-to-100-aws-accounts\u002F)\n\t* [OAuth Audit Toolbox at Indeed](http:\u002F\u002Fengineering.indeedblog.com\u002Fblog\u002F2018\u002F04\u002Foaudit-toolbox\u002F)\n\t* [Active Directory Password Blacklisting at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2018\u002F04\u002Fad-password-blacklisting.html)\t\n\t* [Syscall Auditing at Scale at Slack](https:\u002F\u002Fslack.engineering\u002Fsyscall-auditing-at-scale-e6a3ca8ac1b8)\n\t* [Athenz: Fine-Grained, Role-Based Access Control at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F160481899076\u002Fopen-sourcing-athenz-fine-grained-role-based)\n\t* [Security Development Lifecycle at Slack](https:\u002F\u002Fslack.engineering\u002Fmoving-fast-and-securing-things-540e6c5ae58a)\n\t* [Unprivileged Container Builds at Kinvolk](https:\u002F\u002Fkinvolk.io\u002Fblog\u002F2018\u002F04\u002Ftowards-unprivileged-container-builds\u002F)\n\t* [Diffy: Differencing Engine for Digital Forensics in the Cloud at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fnetflix-sirt-releases-diffy-a-differencing-engine-for-digital-forensics-in-the-cloud-37b71abd2698)\n\t* [Detecting Credential Compromise in AWS at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fnetflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)\n\t* [Scalable User Privacy at Spotify](https:\u002F\u002Flabs.spotify.com\u002F2018\u002F09\u002F18\u002Fscalable-user-privacy\u002F)\n\t* [AVA: Audit Web Applications at Indeed](https:\u002F\u002Fengineering.indeedblog.com\u002Fblog\u002F2018\u002F09\u002Fapplication-scanning\u002F)\n\t* [TTL as a Service: Automatic Revocation of Stale Privileges at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2018\u002F11\u002Fttl-as-a-service.html)\n\t* [Enterprise Key Management at Slack](https:\u002F\u002Fslack.engineering\u002Fengineering-dive-into-slack-enterprise-key-management-1fce471b178c)\t\n\t* [Scalability and Authentication at Twitch](https:\u002F\u002Fblog.twitch.tv\u002Fen\u002F2019\u002F03\u002F15\u002Fhow-twitch-addresses-scalability-and-authentication\u002F)\n\t* [Edge Authentication and Token-Agnostic Identity Propagation at Netflix](https:\u002F\u002Fnetflixtechblog.com\u002Fedge-authentication-and-token-agnostic-identity-propagation-514e47e0b602)\n\t* [Hardening Kubernetes Infrastructure with Cilium at Palantir](https:\u002F\u002Fblog.palantir.com\u002Fhardening-palantirs-kubernetes-infrastructure-with-cilium-1c40d4c7ef0)\n\t* [Improving Web Vulnerability Management through Automation at Lyft](https:\u002F\u002Feng.lyft.com\u002Fimproving-web-vulnerability-management-through-automation-2631570d8415)\n\t* [Clock Skew when Syncing Password Payloads at Drobbox](https:\u002F\u002Fdropbox.tech\u002Fapplication\u002Fdropbox-passwords-clock-skew-payload-sync-merge)\n* [Distributed Messaging, Queuing, and Event Streaming](https:\u002F\u002Farxiv.org\u002Fpdf\u002F1704.00411.pdf)\n\t* [Cape: Event Stream Processing Framework at Dropbox](https:\u002F\u002Fdropbox.tech\u002Finfrastructure\u002Fintroducing-cape)\n\t* [Brooklin: Distributed Service for Near Real-Time Data Streaming at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2019\u002Fbrooklin-open-source)\n\t* [Samza: Stream Processing System for Latency Insighs at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2018\u002F04\u002Fsamza-aeon--latency-insights-for-asynchronous-one-way-flows)\t\n\t* [Bullet: Forward-Looking Query Engine for Streaming Data at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F161855616651\u002Fopen-sourcing-bullet-yahoos-forward-looking)\n\t* [EventHorizon: Tool for Watching Events Streaming at Etsy](https:\u002F\u002Fcodeascraft.com\u002F2018\u002F05\u002F29\u002Fthe-eventhorizon-saga\u002F)\n\t* [Qmessage: Distributed, Asynchronous Task Queue at Quora](https:\u002F\u002Fquoraengineering.quora.com\u002FQmessage-Handling-Billions-of-Tasks-Per-Day)\n\t* [Cherami: Message Queue System for Transporting Async Tasks at Uber](https:\u002F\u002Feng.uber.com\u002Fcherami\u002F)\n\t* [Dynein: Distributed Delayed Job Queueing System at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fdynein-building-a-distributed-delayed-job-queueing-system-93ab10f05f99)\n\t* [Timestone: Queueing System for Non-Parallelizable Workloads at Netflix](https:\u002F\u002Fnetflixtechblog.com\u002Ftimestone-netflixs-high-throughput-low-latency-priority-queueing-system-with-built-in-support-1abf249ba95f)\n\t* [Messaging Service at Riot Games](https:\u002F\u002Fengineering.riotgames.com\u002Fnews\u002Friot-messaging-service)\n\t* [Messaging System Model at Dropbox](https:\u002F\u002Fdropbox.tech\u002Finfrastructure\u002Finfrastructure-messaging-system-model-async-platform-evolution)\n\t* [Debugging Production with Event Logging at Zillow](https:\u002F\u002Fwww.zillow.com\u002Fengineering\u002Fdebugging-production-event-logging\u002F)\n\t* [Cross-platform In-app Messaging Orchestration Service at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fbuilding-a-cross-platform-in-app-messaging-orchestration-service-86ba614f92d8)\n\t* [Video Gatekeeper at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fre-architecting-the-video-gatekeeper-f7b0ac2f6b00)\n\t* [Scaling Push Messaging for Millions of Devices at Netflix](https:\u002F\u002Fwww.infoq.com\u002Fpresentations\u002Fneflix-push-messaging-scale)\n\t* [Delaying Asynchronous Message Processing with RabbitMQ at Indeed](http:\u002F\u002Fengineering.indeedblog.com\u002Fblog\u002F2017\u002F06\u002Fdelaying-messages\u002F)\t\n\t* [Benchmarking Streaming Computation Engines at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F135321837876\u002Fbenchmarking-streaming-computation-engines-at)\n\t* [Improving Stream Data Quality With Protobuf Schema Validation at Deliveroo](https:\u002F\u002Fdeliveroo.engineering\u002F2019\u002F02\u002F05\u002Fimproving-stream-data-quality-with-protobuf-schema-validation.html)\n\t* [Scaling Email Infrastructure at Medium](https:\u002F\u002Fmedium.engineering\u002Fscaling-email-infrastructure-for-medium-digest-254223c883b8)\n\t* [Real-time Messaging at Slack](https:\u002F\u002Fslack.engineering\u002Freal-time-messaging\u002F)\n\t* [Event Stream Database at Nike](https:\u002F\u002Fmedium.com\u002Fnikeengineering\u002Fmoving-faster-with-aws-by-creating-an-event-stream-database-dedec8ca3eeb)\n\t* [Event Tracking System at Udemy](https:\u002F\u002Fmedium.com\u002Fudemy-engineering\u002Fdesigning-the-new-event-tracking-system-at-udemy-a45e502216fd)\n    * [Event-Driven Messaging](https:\u002F\u002Fmartinfowler.com\u002Farticles\u002F201701-event-driven.html)\n        * [Domain-Driven Design at Alibaba](https:\u002F\u002Fmedium.com\u002Fswlh\u002Fcreating-coding-excellence-with-domain-driven-design-88f73d2232c3)\n        * [Domain-Driven Design at Weebly](https:\u002F\u002Fmedium.com\u002Fweebly-engineering\u002Fhow-to-organize-your-monolith-before-breaking-it-into-services-69cbdb9248b0)\n        * [Domain-Driven Design at Moonpig](https:\u002F\u002Fengineering.moonpig.com\u002Fdevelopment\u002Fmodelling-for-domain-driven-design)\n        * [Scaling Event Sourcing for Netflix Downloads](https:\u002F\u002Fwww.infoq.com\u002Fpresentations\u002Fnetflix-scale-event-sourcing)\n        * [Scaling Event-Sourcing at Jet.com](https:\u002F\u002Fmedium.com\u002F@eulerfx\u002Fscaling-event-sourcing-at-jet-9c873cac33b8)\n        * [Event Sourcing (2 parts) at eBay](https:\u002F\u002Fwww.ebayinc.com\u002Fstories\u002Fblogs\u002Ftech\u002Fevent-sourcing-in-action-with-ebays-continuous-delivery-team\u002F)\n\t\t* [Event Sourcing at FREE NOW](https:\u002F\u002Fmedium.com\u002Finside-freenow\u002Fevent-sourcing-an-evolutionary-perspective-31e7387aa6f1)\n\t\t* [Scalable content feed using Event Sourcing and CQRS patterns at Brainly](https:\u002F\u002Fmedium.com\u002Fengineering-brainly\u002Fscalable-content-feed-using-event-sourcing-and-cqrs-patterns-e09df98bf977)\n    * [Pub-Sub Messaging](https:\u002F\u002Faws.amazon.com\u002Fpub-sub-messaging\u002F)\n\t\t* [Pulsar: Pub-Sub Messaging at Scale at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F150078336821\u002Fopen-sourcing-pulsar-pub-sub-messaging-at-scale)\n\t\t* [Wormhole: Pub-Sub System at Facebook](https:\u002F\u002Fcode.facebook.com\u002Fposts\u002F188966771280871\u002Fwormhole-pub-sub-system-moving-data-through-space-and-time\u002F)\n\t\t* [MemQ: Cloud Native Pub-Sub System at Pinterest](https:\u002F\u002Fmedium.com\u002Fpinterest-engineering\u002Fmemq-an-efficient-scalable-cloud-native-pubsub-system-4402695dd4e7)\n\t\t* [Pub-Sub in Microservices at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fhow-netflix-microservices-tackle-dataset-pub-sub-4a068adcc9a)\n\t* [Kafka - Message Broker](https:\u002F\u002Fmartin.kleppmann.com\u002Fpapers\u002Fkafka-debull15.pdf)\t\n\t\t* [Kafka at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fkafka\u002Frunning-kafka-scale)\n\t\t* [Kafka at Pinterest](https:\u002F\u002Fmedium.com\u002Fpinterest-engineering\u002Fhow-pinterest-runs-kafka-at-scale-ff9c6f735be)\n\t\t* [Kafka at Trello](https:\u002F\u002Ftech.trello.com\u002Fwhy-we-chose-kafka\u002F)\t\n\t\t* [Kafka at Salesforce](https:\u002F\u002Fengineering.salesforce.com\u002Fhow-apache-kafka-inspired-our-platform-events-architecture-2f351fe4cf63)\n\t\t* [Kafka at The New York Times](https:\u002F\u002Fopen.nytimes.com\u002Fpublishing-with-apache-kafka-at-the-new-york-times-7f0e3b7d2077)\n\t\t* [Kafka at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2016\u002F07\u002Fbillions-of-messages-a-day-yelps-real-time-data-pipeline.html)\n\t\t* [Kafka at Criteo](https:\u002F\u002Fmedium.com\u002Fcriteo-labs\u002Fupgrading-kafka-on-a-large-infra-3ee99f56e970)\n\t\t* [Kafka on Kubernetes at Shopify](https:\u002F\u002Fshopifyengineering.myshopify.com\u002Fblogs\u002Fengineering\u002Frunning-apache-kafka-on-kubernetes-at-shopify)\n\t\t* [Kafka on PaaSTA: Running Kafka on Kubernetes at Yelp (2 parts)](https:\u002F\u002Fengineeringblog.yelp.com\u002F2022\u002F03\u002Fkafka-on-paasta-part-two.html)\n\t\t* [Migrating Kafka's Zookeeper with No Downtime at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2019\u002F01\u002Fmigrating-kafkas-zookeeper-with-no-downtime.html)\n\t\t* [Reprocessing and Dead Letter Queues with Kafka at Uber](https:\u002F\u002Feng.uber.com\u002Freliable-reprocessing\u002F)\n\t\t* [Chaperone: Audit Kafka End-to-End at Uber](https:\u002F\u002Feng.uber.com\u002Fchaperone\u002F)\n\t\t* [Finding Kafka throughput limit in infrastructure at Dropbox](https:\u002F\u002Fdropbox.tech\u002Finfrastructure\u002Ffinding-kafkas-throughput-limit-in-dropbox-infrastructure)\n\t\t* [Cost Orchestration at Walmart](https:\u002F\u002Fmedium.com\u002Fwalmartlabs\u002Fcost-orchestration-at-walmart-f34918af67c4)\n\t\t* [InfluxDB and Kafka to Scale to Over 1 Million Metrics a Second at Hulu](https:\u002F\u002Fmedium.com\u002Fhulu-tech-blog\u002Fhow-hulu-uses-influxdb-and-kafka-to-scale-to-over-1-million-metrics-a-second-1721476aaff5)\n\t\t* [Scaling Kafka to Support Data Growth at PayPal](https:\u002F\u002Fmedium.com\u002Fpaypal-tech\u002Fscaling-kafka-to-support-paypals-data-growth-a0b4da420fab)\n\t* [Stream Data Deduplication](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FData_deduplication)\n\t\t* [Exactly-once Semantics with Kafka](https:\u002F\u002Fwww.confluent.io\u002Fblog\u002Fexactly-once-semantics-are-possible-heres-how-apache-kafka-does-it\u002F)\n\t\t* [Real-time Deduping at Tapjoy](http:\u002F\u002Feng.tapjoy.com\u002Fblog-list\u002Freal-time-deduping-at-scale)\n\t\t* [Deduplication at Segment](https:\u002F\u002Fsegment.com\u002Fblog\u002Fexactly-once-delivery\u002F)\n\t\t* [Deduplication at Mail.Ru](https:\u002F\u002Fmedium.com\u002F@andrewsumin\u002Fefficient-storage-how-we-went-down-from-50-pb-to-32-pb-99f9c61bf6b4)\n\t\t* [Petabyte Scale Data Deduplication at Mixpanel](https:\u002F\u002Fmedium.com\u002Fmixpaneleng\u002Fpetabyte-scale-data-deduplication-mixpanel-engineering-e808c70c99f8)\n* [Distributed Logging](https:\u002F\u002Fblog.codinghorror.com\u002Fthe-problem-with-logging\u002F)\n\t* [Logging at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fdistributed-systems\u002Flog-what-every-software-engineer-should-know-about-real-time-datas-unifying)\n\t* [Scalable and Reliable Log Ingestion at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fscalable-and-reliable-data-ingestion-at-pinterest-b921c2ee8754)\n\t* [High-performance Replicated Log Service at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Ftopics\u002Finfrastructure\u002F2015\u002Fbuilding-distributedlog-twitter-s-high-performance-replicated-log-servic.html)\n\t* [Logging Service with Spark at CERN Accelerator](https:\u002F\u002Fdatabricks.com\u002Fblog\u002F2017\u002F12\u002F14\u002Fthe-architecture-of-the-next-cern-accelerator-logging-service.html)\n\t* [Logging and Aggregation at Quora](https:\u002F\u002Fquoraengineering.quora.com\u002FLogging-and-Aggregation-at-Quora)\n\t* [Collection and Analysis of Daemon Logs at Badoo](https:\u002F\u002Fbadoo.com\u002Ftechblog\u002Fblog\u002F2016\u002F06\u002F06\u002Fcollection-and-analysis-of-daemon-logs-at-badoo\u002F)\n\t* [Log Parsing with Static Code Analysis at Palantir](https:\u002F\u002Fmedium.com\u002Fpalantir\u002Fusing-static-code-analysis-to-improve-log-parsing-18f0d1843965)\t\t\n\t* [Centralized Application Logging at eBay](https:\u002F\u002Ftech.ebayinc.com\u002Fengineering\u002Flow-latency-and-high-throughput-cal-ingress\u002F)\n\t* [Enrich VPC Flow Logs at Hyper Scale to provide Network Insight at Netflix](https:\u002F\u002Fnetflixtechblog.com\u002Fhyper-scale-vpc-flow-logs-enrichment-to-provide-network-insight-e5f1db02910d)\t\n\t* [BookKeeper: Distributed Log Storage at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F109908973316\u002Fbookkeeper-yahoos-distributed-log-storage-is)\n\t* [LogDevice: Distributed Data Store for Logs at Facebook](https:\u002F\u002Fcode.facebook.com\u002Fposts\u002F357056558062811\u002Flogdevice-a-distributed-data-store-for-logs\u002F)\n\t* [LogFeeder: Log Collection System at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2018\u002F03\u002Fintroducing-logfeeder.html)\n\t* [DBLog: Generic Change-Data-Capture Framework at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fdblog-a-generic-change-data-capture-framework-69351fb9099b)\t\n* [Distributed Searching](http:\u002F\u002Fnwds.cs.washington.edu\u002Ffiles\u002Fnwds\u002Fpdf\u002FDistributed-WR.pdf)\n\t* [Search Architecture at Instagram](https:\u002F\u002Finstagram-engineering.com\u002Fsearch-architecture-eeb34a936d3a)\n\t* [Search Architecture at eBay](http:\u002F\u002Fwww.cs.otago.ac.nz\u002Fhomepages\u002Fandrew\u002Fpapers\u002F2017-8.pdf)\n\t* [Search Architecture at Box](https:\u002F\u002Fmedium.com\u002Fbox-tech-blog\u002Fscaling-box-search-using-lumos-22d9e0cb4175)\n\t* [Search Discovery Indexing Platform at Coupang](https:\u002F\u002Fmedium.com\u002Fcoupang-tech\u002Fthe-evolution-of-search-discovery-indexing-platform-fa43e41305f9)\n\t* [Universal Search System at Pinterest](https:\u002F\u002Fmedium.com\u002Fpinterest-engineering\u002Fbuilding-a-universal-search-system-for-pinterest-e4cb03a898d4)\n\t* [Improving Search Engine Efficiency by over 25% at eBay](https:\u002F\u002Fwww.ebayinc.com\u002Fstories\u002Fblogs\u002Ftech\u002Fmaking-e-commerce-search-faster\u002F)\t\n\t* [Indexing and Querying Telemetry Logs with Lucene at Palantir](https:\u002F\u002Fmedium.com\u002Fpalantir\u002Findexing-and-querying-telemetry-logs-with-lucene-234c5ce3e5f3)\n\t* [Query Understanding at TripAdvisor](https:\u002F\u002Fwww.tripadvisor.com\u002Fengineering\u002Fquery-understanding-at-tripadvisor\u002F)\n\t* [Search Federation Architecture at LinkedIn (2018)](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2018\u002F03\u002Fsearch-federation-architecture-at-linkedin)\n\t* [Search at Slack](https:\u002F\u002Fslack.engineering\u002Fsearch-at-slack-431f8c80619e)\n\t* [Search Engine at DoorDash](https:\u002F\u002Fcareersatdoordash.com\u002Fblog\u002Fintroducing-doordashs-in-house-search-engine\u002F)\n\t* [Stability and Scalability for Search at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Ftopics\u002Finfrastructure\u002F2022\u002Fstability-and-scalability-for-search)\n\t* [Search Service at Twitter (2014)](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Fa\u002F2014\u002Fbuilding-a-complete-tweet-index.html)\n\t* [Autocomplete Search (2 parts) at Traveloka](https:\u002F\u002Fmedium.com\u002Ftraveloka-engineering\u002Fhigh-quality-autocomplete-search-part-2-d5b15bb0dadf)\n\t* [Data-Driven Autocorrection System at Canva](https:\u002F\u002Fproduct.canva.com\u002Fbuilding-a-data-driven-autocorrection-system\u002F)\n\t* [Adapting Search to Indian Phonetics at Flipkart](https:\u002F\u002Fblog.flipkart.tech\u002Fadapting-search-to-indian-phonetics-cdbe65259686)\n\t* [Nautilus: Search Engine at Dropbox](https:\u002F\u002Fdropbox.tech\u002Fmachine-learning\u002Farchitecture-of-nautilus-the-new-dropbox-search-engine)\n\t* [Galene: Search Architecture of LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fsearch\u002Fdid-you-mean-galene)\n\t* [Manas: High Performing Customized Search System at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fmanas-a-high-performing-customized-search-system-cf189f6ca40f)\n\t* [Sherlock: Near Real Time Search Indexing at Flipkart](https:\u002F\u002Fblog.flipkart.tech\u002Fsherlock-near-real-time-search-indexing-95519783859d)\n\t* [Nebula: Storage Platform to Build Search Backends at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fnebula-as-a-storage-platform-to-build-airbnbs-search-backends-ecc577b05f06)\n\t* [ELK (Elasticsearch, Logstash, Kibana) Stack](https:\u002F\u002Flogz.io\u002Fblog\u002F15-tech-companies-chose-elk-stack\u002F)\n\t\t* [Predictions in Real Time with ELK at Uber](https:\u002F\u002Feng.uber.com\u002Felk\u002F)\n\t\t* [Building a scalable ELK stack at Envato](https:\u002F\u002Fwebuild.envato.com\u002Fblog\u002Fbuilding-a-scalable-elk-stack\u002F)\n\t\t* [ELK at Robinhood](https:\u002F\u002Frobinhood.engineering\u002Ftaming-elk-4e1349f077c3)\n\t\t* [Scaling Elasticsearch Clusters at Uber](https:\u002F\u002Fwww.infoq.com\u002Fpresentations\u002Fuber-elasticsearch-clusters?utm_source=presentations_about_Case_Study&utm_medium=link&utm_campaign=Case_Study)\n\t\t* [Elasticsearch Performance Tuning Practice at eBay](https:\u002F\u002Fwww.ebayinc.com\u002Fstories\u002Fblogs\u002Ftech\u002Felasticsearch-performance-tuning-practice-at-ebay\u002F)\n\t\t* [Improve Performance using Elasticsearch Plugins (2 parts) at Tinder](https:\u002F\u002Fmedium.com\u002Ftinder-engineering\u002Fhow-we-improved-our-performance-using-elasticsearch-plugins-part-2-b051da2ee85b)\n\t\t* [Elasticsearch at Kickstarter](https:\u002F\u002Fkickstarter.engineering\u002Felasticsearch-at-kickstarter-db3c487887fc)\n\t\t* [Log Parsing with Logstash and Google Protocol Buffers at Trivago](https:\u002F\u002Ftech.trivago.com\u002F2016\u002F01\u002F19\u002Flogstash_protobuf_codec\u002F)\n\t\t* [Fast Order Search using Data Pipeline and Elasticsearch at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2018\u002F06\u002Ffast-order-search.html)\n\t\t* [Moving Core Business Search to Elasticsearch at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2017\u002F06\u002Fmoving-yelps-core-business-search-to-elasticsearch.html)\n\t\t* [Sharding out Elasticsearch at Vinted](http:\u002F\u002Fengineering.vinted.com\u002F2017\u002F06\u002F05\u002Fsharding-out-elasticsearch\u002F)\n\t\t* [Self-Ranking Search with Elasticsearch at Wattpad](http:\u002F\u002Fengineering.wattpad.com\u002Fpost\u002F146216619727\u002Fself-ranking-search-with-elasticsearch-at-wattpad)\n\t\t* [Vulcanizer: a library for operating Elasticsearch at Github](https:\u002F\u002Fgithub.blog\u002F2019-03-05-vulcanizer-a-library-for-operating-elasticsearch\u002F)\t\n* [Distributed Storage](http:\u002F\u002Fhighscalability.com\u002Fblog\u002F2011\u002F11\u002F1\u002Ffinding-the-right-data-solution-for-your-application-in-the.html)\n\t* [In-memory Storage](https:\u002F\u002Fmedium.com\u002F@denisanikin\u002Fwhat-an-in-memory-database-is-and-how-it-persists-data-efficiently-f43868cff4c1)\n\t\t* [MemSQL Architecture - The Fast (MVCC, InMem, LockFree, CodeGen) And Familiar (SQL)](http:\u002F\u002Fhighscalability.com\u002Fblog\u002F2012\u002F8\u002F14\u002Fmemsql-architecture-the-fast-mvcc-inmem-lockfree-codegen-and.html)\n\t\t* [Optimizing Memcached Efficiency at Quora](https:\u002F\u002Fquoraengineering.quora.com\u002FOptimizing-Memcached-Efficiency)\n\t\t* [Real-Time Data Warehouse with MemSQL on Cisco UCS](https:\u002F\u002Fblogs.cisco.com\u002Fdatacenter\u002Fmemsql)\n\t\t* [Moving to MemSQL at Tapjoy](http:\u002F\u002Feng.tapjoy.com\u002Fblog-list\u002Fmoving-to-memsql)\n\t\t* [MemSQL and Kinesis for Real-time Insights at Disney](https:\u002F\u002Fconferences.oreilly.com\u002Fstrata\u002Fstrata-ca\u002Fpublic\u002Fschedule\u002Fdetail\u002F68131)\n\t\t* [MemSQL to Query Hundreds of Billions of Rows in a Dashboard at Pandora](https:\u002F\u002Fengineering.pandora.com\u002Fusing-memsql-at-pandora-79a86cb09b57)\n\t* [Object Storage](http:\u002F\u002Fwww.datacenterknowledge.com\u002Farchives\u002F2013\u002F10\u002F04\u002Fobject-storage-the-future-of-scale-out)\n\t\t* [Scaling HDFS at Uber](https:\u002F\u002Feng.uber.com\u002Fscaling-hdfs\u002F)\n\t\t* [Reasons for Choosing S3 over HDFS at Databricks](https:\u002F\u002Fdatabricks.com\u002Fblog\u002F2017\u002F05\u002F31\u002Ftop-5-reasons-for-choosing-s3-over-hdfs.html)\n\t\t* [File System on Amazon S3 at Quantcast](https:\u002F\u002Fwww.quantcast.com\u002Fblog\u002Fquantcast-file-system-on-amazon-s3\u002F)\n\t\t* [Image Recovery at Scale Using S3 Versioning at Trivago](https:\u002F\u002Ftech.trivago.com\u002F2018\u002F09\u002F03\u002Fefficient-image-recovery-at-scale-using-amazon-s3-versioning\u002F)\n\t\t* [Cloud Object Store at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F116391291701\u002Fyahoo-cloud-object-store-object-storage-at)\n\t\t* [Ambry: Distributed Immutable Object Store at LinkedIn](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon17americas\u002Fprogram\u002Fpresentation\u002Fshenoy)\n\t\t* [Dynamometer: Scale Testing HDFS on Minimal Hardware with Maximum Fidelity at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2018\u002F02\u002Fdynamometer--scale-testing-hdfs-on-minimal-hardware-with-maximum)\n\t\t* [Hammerspace: Persistent, Concurrent, Off-heap Storage at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fhammerspace-persistent-concurrent-off-heap-storage-3db39bb04472)\n\t\t* [MezzFS: Mounting Object Storage in Media Processing Platform at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fmezzfs-mounting-object-storage-in-netflixs-media-processing-platform-cda01c446ba)\t\n\t\t* [Magic Pocket: In-house Multi-exabyte Storage System at Dropbox](https:\u002F\u002Fdropbox.tech\u002Finfrastructure\u002Finside-the-magic-pocket)\n* [Relational Databases](https:\u002F\u002Fwww.mysql.com\u002Fproducts\u002Fcluster\u002Fscalability.html)\n\t* [MySQL at Uber](https:\u002F\u002Fwww.uber.com\u002Fen-SG\u002Fblog\u002Fmysql-at-uber\u002F)\n\t* [MySQL at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Flearn-to-stop-using-shiny-new-things-and-love-mysql-3e1613c2ce14)\n\t* [PostgreSQL at Twitch](https:\u002F\u002Fblog.twitch.tv\u002Fen\u002F2016\u002F10\u002F11\u002Fhow-twitch-uses-postgresql-c34aa9e56f58)\n\t* [Scaling MySQL-based Financial Reporting System at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Ftracking-the-money-scaling-financial-reporting-at-airbnb-6d742b80f040)\n\t* [Scaling MySQL at Wix](https:\u002F\u002Fwww.wix.engineering\u002Fpost\u002Fscaling-to-100m-mysql-is-a-better-nosql)\n\t* [Building and Deploying MySQL Raft at Meta](https:\u002F\u002Fengineering.fb.com\u002F2023\u002F05\u002F16\u002Fdata-infrastructure\u002Fmysql-raft-meta\u002F)\n\t* [MaxScale (MySQL) Database Proxy at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Funlocking-horizontal-scalability-in-our-web-serving-tier-d907449cdbcf)\n\t* [Switching from Postgres to MySQL at Uber](https:\u002F\u002Fwww.uber.com\u002Fen-NL\u002Fblog\u002Fpostgres-to-mysql-migration\u002F)\n\t* [Handling Growth with Postgres at Instagram](https:\u002F\u002Fengineering.instagram.com\u002Fhandling-growth-with-postgres-5-tips-from-instagram-d5d7e7ffdfcb)\n\t* [Scaling the Analytics Database (Postgres) at TransferWise](http:\u002F\u002Ftech.transferwise.com\u002Fscaling-our-analytics-database\u002F)\n\t* [Updating a 50 Terabyte PostgreSQL Database at Adyen](https:\u002F\u002Fmedium.com\u002Fadyen\u002Fupdating-a-50-terabyte-postgresql-database-f64384b799e7)\n\t* [Scaling Database Access for 100s of Billions of Queries per Day at PayPal](https:\u002F\u002Fmedium.com\u002Fpaypal-engineering\u002Fscaling-database-access-for-100s-of-billions-of-queries-per-day-paypal-introducing-hera-e192adacda54)\n\t* [Minimizing Read-Write MySQL Downtime at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2020\u002F11\u002Fminimizing-read-write-mysql-downtime.html)\n\t* [Migrating MySQL from 5.6 to 8.0 at Facebook](https:\u002F\u002Fengineering.fb.com\u002F2021\u002F07\u002F22\u002Fdata-infrastructure\u002Fmysql\u002F)\n\t* [Migration from HBase to MyRocks at Quora](https:\u002F\u002Fquoraengineering.quora.com\u002FMigration-from-HBase-to-MyRocks-at-Quora)\n\t* [Replication](https:\u002F\u002Fdocs.microsoft.com\u002Fen-us\u002Fsql\u002Frelational-databases\u002Freplication\u002Ftypes-of-replication)\n\t\t* [MySQL Parallel Replication (4 parts) at Booking.com](https:\u002F\u002Fmedium.com\u002Fbooking-com-infrastructure\u002Fevaluating-mysql-parallel-replication-part-4-annex-under-the-hood-eb456cf8b2fb)\n\t\t* [Mitigating MySQL Replication Lag and Reducing Read Load at Github](https:\u002F\u002Fgithubengineering.com\u002Fmitigating-replication-lag-and-reducing-read-load-with-freno\u002F)\n\t\t* [Read Consistency with Database Replicas at Shopify](https:\u002F\u002Fshopify.engineering\u002Fread-consistency-database-replicas)\n\t\t* [Black-Box Auditing: Verifying End-to-End Replication Integrity between MySQL and Redshift at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2018\u002F04\u002Fblack-box-auditing.html)\n\t\t* [Partitioning Main MySQL Database at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fhow-we-partitioned-airbnb-s-main-database-in-two-weeks-55f7e006ff21)\n\t\t* [Herb: Multi-DC Replication Engine for Schemaless Datastore at Uber](https:\u002F\u002Feng.uber.com\u002Fherb-datacenter-replication\u002F)\n\t* [Sharding](https:\u002F\u002Fquabase.sei.cmu.edu\u002Fmediawiki\u002Findex.php\u002FShard_data_set_across_multiple_servers_(Range-based))\n\t\t* [Sharding MySQL at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fsharding-pinterest-how-we-scaled-our-mysql-fleet-3f341e96ca6f)\n\t\t* [Sharding MySQL at Twilio](https:\u002F\u002Fwww.twilio.com\u002Fengineering\u002F2014\u002F06\u002F26\u002Fhow-we-replaced-our-data-pipeline-with-zero-downtime)\n\t\t* [Sharding MySQL at Square](https:\u002F\u002Fmedium.com\u002Fsquare-corner-blog\u002Fsharding-cash-10280fa3ef3b)\n\t\t* [Sharding MySQL at Quora](https:\u002F\u002Fwww.quora.com\u002Fq\u002Fquoraengineering\u002FMySQL-sharding-at-Quora)\n\t\t* [Sharding Layer of Schemaless Datastore at Uber](https:\u002F\u002Feng.uber.com\u002Fschemaless-rewrite\u002F)\n\t\t* [Sharding & IDs at Instagram](https:\u002F\u002Finstagram-engineering.com\u002Fsharding-ids-at-instagram-1cf5a71e5a5c)\n\t\t* [Sharding Postgres at Notion](https:\u002F\u002Fwww.notion.so\u002Fblog\u002Fsharding-postgres-at-notion)\n\t\t* [Sharding Postgres at Figma](https:\u002F\u002Fwww.figma.com\u002Fblog\u002Fhow-figmas-databases-team-lived-to-tell-the-scale\u002F)\n\t\t* [Solr: Improving Performance for Batch Indexing at Box](https:\u002F\u002Fblog.box.com\u002Fblog\u002Fsolr-improving-performance-batch-indexing\u002F)\t\n\t\t* [Geosharded Recommendations (3 parts) at Tinder](https:\u002F\u002Fmedium.com\u002Ftinder-engineering\u002Fgeosharded-recommendations-part-3-consistency-2d2cb2f0594b)\n\t\t* [Scaling Services with Shard Manager at Facebook](https:\u002F\u002Fengineering.fb.com\u002Fproduction-engineering\u002Fscaling-services-with-shard-manager\u002F)\n\t* [Presto the Distributed SQL Query Engine](https:\u002F\u002Fresearch.fb.com\u002Fwp-content\u002Fuploads\u002F2019\u002F03\u002FPresto-SQL-on-Everything.pdf?)\n\t\t* [Presto at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fpresto-at-pinterest-a8bda7515e52)\n\t\t* [Presto Infrastructure at Lyft](https:\u002F\u002Feng.lyft.com\u002Fpresto-infrastructure-at-lyft-b10adb9db01)\n\t\t* [Presto at Grab](https:\u002F\u002Fengineering.grab.com\u002Fscaling-like-a-boss-with-presto)\n\t\t* [Engineering Data Analytics with Presto and Apache Parquet at Uber](https:\u002F\u002Feng.uber.com\u002Fpresto\u002F)\n\t\t* [Data Wrangling at Slack](https:\u002F\u002Fslack.engineering\u002Fdata-wrangling-at-slack-f2e0ff633b69)\n\t\t* [Presto in Big Data Platform on AWS at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fusing-presto-in-our-big-data-platform-on-aws-938035909fd4)\n\t\t* [Presto Auto Scaling at Eventbrite](https:\u002F\u002Fwww.eventbrite.com\u002Fengineering\u002Fbig-data-workloads-presto-auto-scaling\u002F)\n\t\t* [Speed Up Presto with Alluxio Local Cache at Uber](https:\u002F\u002Fwww.uber.com\u002Fen-MY\u002Fblog\u002Fspeed-up-presto-with-alluxio-local-cache\u002F)\n* [NoSQL Databases](https:\u002F\u002Fwww.thoughtworks.com\u002Finsights\u002Fblog\u002Fnosql-databases-overview)\n\t* [Key-Value Databases](http:\u002F\u002Fwww.cs.ucsb.edu\u002F~agrawal\u002Ffall2009\u002Fdynamo.pdf)\n\t\t* [DynamoDB at Nike](https:\u002F\u002Fmedium.com\u002Fnikeengineering\u002Fbecoming-a-nimble-giant-how-dynamo-db-serves-nike-at-scale-4cc375dbb18e)\n\t\t* [DynamoDB at Segment](https:\u002F\u002Fsegment.com\u002Fblog\u002Fthe-million-dollar-eng-problem\u002F)\n\t\t* [DynamoDB at Mapbox](https:\u002F\u002Fblog.mapbox.com\u002Fscaling-mapbox-infrastructure-with-dynamodb-streams-d53eabc5e972)\n\t\t* [Manhattan: Distributed Key-Value Database at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Fa\u002F2014\u002Fmanhattan-our-real-time-multi-tenant-distributed-database-for-twitter-scale.html)\n\t\t* [Sherpa: Distributed NoSQL Key-Value Store at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F120730204806\u002Fsherpa-scales-new-heights)\n\t\t* [HaloDB: Embedded Key-Value Storage Engine at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F178262468576\u002Fintroducing-halodb-a-fast-embedded-key-value)\n\t\t* [MPH: Fast and Compact Immutable Key-Value Stores at Indeed](http:\u002F\u002Fengineering.indeedblog.com\u002Fblog\u002F2018\u002F02\u002Findeed-mph\u002F)\n\t\t* [Venice: Distributed Key-Value Database at Linkedin](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2017\u002F02\u002Fbuilding-venice-with-apache-helix)\n\t* [Columnar Databases](https:\u002F\u002Faws.amazon.com\u002Fnosql\u002Fcolumnar\u002F)\n\t\t* [Cassandra](http:\u002F\u002Fwww.cs.cornell.edu\u002Fprojects\u002Fladis2009\u002Fpapers\u002Flakshman-ladis2009.pdf)\n\t\t\t* [Cassandra at Instagram](https:\u002F\u002Fwww.slideshare.net\u002FDataStax\u002Fcassandra-at-instagram-2016)\n\t\t\t* [Storing Images in Cassandra at Walmart](https:\u002F\u002Fmedium.com\u002Fwalmartlabs\u002Fbuilding-object-store-storing-images-in-cassandra-walmart-scale-a6b9c02af593)\n\t\t\t* [Storing Messages with Cassandra at Discord](https:\u002F\u002Fblog.discordapp.com\u002Fhow-discord-stores-billions-of-messages-7fa6ec7ee4c7)\n\t\t\t* [Scaling Cassandra Cluster at Walmart](https:\u002F\u002Fmedium.com\u002Fwalmartlabs\u002Favoid-pitfalls-in-scaling-your-cassandra-cluster-lessons-and-remedies-a71ca01f8c04)\n\t\t\t* [Scaling Ad Analytics with Cassandra at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2016\u002F08\u002Fhow-we-scaled-our-ad-analytics-with-cassandra.html)\n\t\t\t* [Scaling to 100+ Million Reads\u002FWrites using Spark and Cassandra at Dream11](https:\u002F\u002Fmedium.com\u002Fdream11-tech-blog\u002Fleaderboard-dream11-4efc6f93c23e)\t\t\n\t\t\t* [Moving Food Feed from Redis to Cassandra at Zomato](https:\u002F\u002Fwww.zomato.com\u002Fblog\u002Fhow-we-moved-our-food-feed-from-redis-to-cassandra)\n\t\t\t* [Benchmarking Cassandra Scalability on AWS at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fbenchmarking-cassandra-scalability-on-aws-over-a-million-writes-per-second-39f45f066c9e)\n\t\t\t* [Service Decomposition at Scale with Cassandra at Intuit QuickBooks](https:\u002F\u002Fquickbooks-engineering.intuit.com\u002Fservice-decomposition-at-scale-70405ac2f637)\n\t\t\t* [Cassandra for Keeping Counts In Sync at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Fkeeping-counts-in-sync)\n\t\t\t* [Cassandra Driver Configuration for Improved Performance and Load Balancing at Glassdoor](https:\u002F\u002Fmedium.com\u002Fglassdoor-engineering\u002Fcassandra-driver-configuration-for-improved-performance-and-load-balancing-1b0106ce12bb)\n\t\t\t* [cstar: Cassandra Orchestration Tool at Spotify](https:\u002F\u002Flabs.spotify.com\u002F2018\u002F09\u002F04\u002Fintroducing-cstar-the-spotify-cassandra-orchestration-tool-now-open-source\u002F)\n\t\t* [HBase](https:\u002F\u002Fhbase.apache.org\u002F)\n\t\t\t* [HBase at Salesforce](https:\u002F\u002Fengineering.salesforce.com\u002Finvesting-in-big-data-apache-hbase-b9d98661a66b)\n\t\t\t* [HBase in Facebook Messages](https:\u002F\u002Fwww.facebook.com\u002Fnotes\u002Ffacebook-engineering\u002Fthe-underlying-technology-of-messages\u002F454991608919\u002F)\n\t\t\t* [HBase in Imgur Notification](https:\u002F\u002Fblog.imgur.com\u002F2015\u002F09\u002F15\u002Ftech-tuesday-imgur-notifications-from-mysql-to-hbase\u002F)\n\t\t\t* [Improving HBase Backup Efficiency at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fimproving-hbase-backup-efficiency-at-pinterest-86159da4b954)\n\t\t\t* [HBase at Xiaomi](https:\u002F\u002Fwww.slideshare.net\u002FHBaseCon\u002Fhbase-practice-at-xiaomi)\n\t\t* [Redshift](https:\u002F\u002Fwww.allthingsdistributed.com\u002F2018\u002F11\u002Famazon-redshift-performance-optimization.html)\n\t\t\t* [Redshift at GIPHY](https:\u002F\u002Fengineering.giphy.com\u002Fscaling-redshift-without-scaling-costs\u002F)\n\t\t\t* [Redshift at Hudl](https:\u002F\u002Fwww.hudl.com\u002Fbits\u002Fthe-low-hanging-fruit-of-redshift-performance)\n\t\t\t* [Redshift at Drivy](https:\u002F\u002Fdrivy.engineering\u002Fredshift_tips_ticks_part_1\u002F)\n\t* [Document Databases](https:\u002F\u002Fmsdn.microsoft.com\u002Fen-us\u002Fmagazine\u002Fhh547103.aspx)\n\t\t* [eBay: Building Mission-Critical Multi-Data Center Applications with MongoDB](https:\u002F\u002Fwww.mongodb.com\u002Fblog\u002Fpost\u002Febay-building-mission-critical-multi-data-center-applications-with-mongodb)\n\t\t* [MongoDB at Baidu: Multi-Tenant Cluster Storing 200+ Billion Documents across 160 Shards](https:\u002F\u002Fwww.mongodb.com\u002Fblog\u002Fpost\u002Fmongodb-at-baidu-powering-100-apps-across-600-nodes-at-pb-scale)\n\t\t* [Migrating Mongo Data at Addepar](https:\u002F\u002Fmedium.com\u002Fbuild-addepar\u002Fmigrating-mountains-of-mongo-data-63e530539952)\n\t\t* [The AWS and MongoDB Infrastructure of Parse (acquired by Facebook)](https:\u002F\u002Fmedium.baqend.com\u002Fparse-is-gone-a-few-secrets-about-their-infrastructure-91b3ab2fcf71)\n\t\t* [Migrating Mountains of Mongo Data at Addepar](https:\u002F\u002Fmedium.com\u002Fbuild-addepar\u002Fmigrating-mountains-of-mongo-data-63e530539952)\n\t\t* [Couchbase Ecosystem at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2017\u002F12\u002Fcouchbase-ecosystem-at-linkedin)\n\t\t* [SimpleDB at Zendesk](https:\u002F\u002Fmedium.com\u002Fzendesk-engineering\u002Fresurrecting-amazon-simpledb-9404034ec506)\n\t\t* [Espresso: Distributed Document Store at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fespresso\u002Fintroducing-espresso-linkedins-hot-new-distributed-document-store)\n\t* [Graph Databases](https:\u002F\u002Fwww.eecs.harvard.edu\u002Fmargo\u002Fpapers\u002Fsystor13-bench\u002F)\n\t\t* [FlockDB: Distributed Graph Database at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Fa\u002F2010\u002Fintroducing-flockdb.html)\n\t\t* [TAO: Distributed Data Store for the Social Graph at Facebook](https:\u002F\u002Fwww.cs.cmu.edu\u002F~pavlo\u002Fcourses\u002Ffall2013\u002Fstatic\u002Fpapers\u002F11730-atc13-bronson.pdf)\n\t\t* [Akutan: Distributed Knowledge Graph Store at eBay](https:\u002F\u002Ftech.ebayinc.com\u002Fengineering\u002Fakutan-a-distributed-knowledge-graph-store\u002F)\n* [Time Series Databases](https:\u002F\u002Fwww.influxdata.com\u002Ftime-series-database\u002F)\n\t* [Beringei: High-performance Time Series Storage Engine at Facebook](https:\u002F\u002Fcode.facebook.com\u002Fposts\u002F952820474848503\u002Fberingei-a-high-performance-time-series-storage-engine\u002F)\n\t* [MetricsDB: TimeSeries Database for storing metrics at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Ftopics\u002Finfrastructure\u002F2019\u002Fmetricsdb.html)\t\n\t* [Atlas: In-memory Dimensional Time Series Database at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fintroducing-atlas-netflixs-primary-telemetry-platform-bd31f4d8ed9a)\n\t* [Heroic: Time Series Database at Spotify](https:\u002F\u002Flabs.spotify.com\u002F2015\u002F11\u002F17\u002Fmonitoring-at-spotify-introducing-heroic\u002F)\n\t* [Roshi: Distributed Storage System for Time-Series Event at SoundCloud](https:\u002F\u002Fdevelopers.soundcloud.com\u002Fblog\u002Froshi-a-crdt-system-for-timestamped-events)\n\t* [Goku: Time Series Database at Pinterest](https:\u002F\u002Fmedium.com\u002F@Pinterest_Engineering\u002Fgoku-building-a-scalable-and-high-performant-time-series-database-system-a8ff5758a181)\n\t* [Scaling Time Series Data Storage (2 parts) at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Fscaling-time-series-data-storage-part-ii-d67939655586)\n\t* [Time Series Data Abstraction Layer at Netflix](https:\u002F\u002Fnetflixtechblog.com\u002Fintroducing-netflix-timeseries-data-abstraction-layer-31552f6326f8)\n\t* [Druid - Real-time Analytics Database](https:\u002F\u002Fdruid.apache.org\u002F)\n\t\t* [Druid at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fdruid-airbnb-data-platform-601c312f2a4c)\n\t\t* [Druid at Walmart](https:\u002F\u002Fmedium.com\u002Fwalmartlabs\u002Fevent-stream-analytics-at-walmart-with-druid-dcf1a37ceda7)\n\t\t* [Druid at eBay](https:\u002F\u002Ftech.ebayinc.com\u002Fengineering\u002Fmonitoring-at-ebay-with-druid\u002F)\n\t\t* [Druid at Netflix](https:\u002F\u002Fnetflixtechblog.com\u002Fhow-netflix-uses-druid-for-real-time-insights-to-ensure-a-high-quality-experience-19e1e8568d06)\n* [Distributed Repositories, Dependencies, and Configurations Management](https:\u002F\u002Fbetterexplained.com\u002Farticles\u002Fintro-to-distributed-version-control-illustrated\u002F)\n\t* [DGit: Distributed Git at Github](https:\u002F\u002Fgithubengineering.com\u002Fintroducing-dgit\u002F)\n\t* [Stemma: Distributed Git Server at Palantir](https:\u002F\u002Fmedium.com\u002F@palantir\u002Fstemma-distributed-git-server-70afbca0fc29)\n\t* [Configuration Management for Distributed Systems at Flickr](https:\u002F\u002Fcode.flickr.net\u002F2016\u002F03\u002F24\u002Fconfiguration-management-for-distributed-systems-using-github-and-cfg4j\u002F)\n\t* [Git Repository at Microsoft](https:\u002F\u002Fblogs.msdn.microsoft.com\u002Fbharry\u002F2017\u002F05\u002F24\u002Fthe-largest-git-repo-on-the-planet\u002F)\n\t* [Solve Git Problem with Large Repositories at Microsoft](https:\u002F\u002Fwww.infoq.com\u002Fnews\u002F2017\u002F02\u002FGVFS)\t\n\t* [Single Repository at Google](https:\u002F\u002Fcacm.acm.org\u002Fmagazines\u002F2016\u002F7\u002F204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository\u002Ffulltext)\t\n\t* [Scaling Infrastructure and (Git) Workflow at Adyen](https:\u002F\u002Fmedium.com\u002Fadyen\u002Ffrom-0-100-billion-scaling-infrastructure-and-workflow-at-adyen-7b63b690dfb6)\t\n\t* [Dotfiles Distribution at Booking.com](https:\u002F\u002Fmedium.com\u002Fbooking-com-infrastructure\u002Fdotfiles-distribution-dedb69c66a75)\n\t* [Secret Detector: Preventing Secrets in Source Code at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2018\u002F06\u002Fyelps-secret-detector.html)\n\t* [Managing Software Dependency at Scale at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2018\u002F09\u002Fmanaging-software-dependency-at-scale)\n\t* [Merging Code in High-velocity Repositories at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2020\u002Fcontinuous-integration)\n\t* [Dynamic Configuration at Twitter](https:\u002F\u002Fblog.twitter.com\u002Fengineering\u002Fen_us\u002Ftopics\u002Finfrastructure\u002F2018\u002Fdynamic-configuration-at-twitter.html)\n\t* [Dynamic Configuration at Mixpanel](https:\u002F\u002Fmedium.com\u002Fmixpaneleng\u002Fdynamic-configuration-at-mixpanel-94bfcf97d6b8)\n\t* [Dynamic Configuration at GoDaddy](https:\u002F\u002Fsg.godaddy.com\u002Fengineering\u002F2019\u002F03\u002F06\u002Fdynamic-configuration-for-nodejs\u002F)\n\t* [Fleet Management (3 parts) at Spotify](https:\u002F\u002Fengineering.atspotify.com\u002F2023\u002F5\u002Ffleet-management-at-spotify-part-3-fleet-wide-refactoring)\n* [Scaling Continuous Integration and Continuous Delivery](https:\u002F\u002Fwww.synopsys.com\u002Fblogs\u002Fsoftware-security\u002Fagile-cicd-devops-glossary\u002F)\n\t* [Continuous Integration Stack at Facebook](https:\u002F\u002Fcode.fb.com\u002Fweb\u002Frapid-release-at-massive-scale\u002F)\n\t* [Continuous Integration with Distributed Repositories and Dependencies at Netflix](https:\u002F\u002Fmedium.com\u002Fnetflix-techblog\u002Ftowards-true-continuous-integration-distributed-repositories-and-dependencies-2a2e3108c051)\n\t* [Continuous Integration and Deployment with Bazel at Dropbox](https:\u002F\u002Fdropbox.tech\u002Finfrastructure\u002Fcontinuous-integration-and-deployment-with-bazel)\n\t* [Adopting Bazel for Web at Airbnb](https:\u002F\u002Fmedium.com\u002Fairbnb-engineering\u002Fadopting-bazel-for-web-at-scale-a784b2dbe325)\n\t* [Continuous Deployments at BuzzFeed](https:\u002F\u002Ftech.buzzfeed.com\u002Fcontinuous-deployments-at-buzzfeed-d171f76c1ac4)\n\t* [Screwdriver: Continuous Delivery Build System for Dynamic Infrastructure at Yahoo](https:\u002F\u002Fyahooeng.tumblr.com\u002Fpost\u002F155765242061\u002Fopen-sourcing-screwdriver-yahoos-continuous)\n\t* [CI\u002FCD at Betterment](https:\u002F\u002Fwww.betterment.com\u002Fresources\u002Fci-cd-shortening-the-feedback-loop\u002F)\n\t* [CI\u002FCD at Brainly](https:\u002F\u002Fmedium.com\u002Fengineering-brainly\u002Fci-cd-at-scale-fdfb0f49e031)\n\t* [Scaling iOS CI with Anka at Shopify](https:\u002F\u002Fengineering.shopify.com\u002Fblogs\u002Fengineering\u002Fscaling-ios-ci-with-anka)\n\t* [Scaling Jira Server at Yelp](https:\u002F\u002Fengineeringblog.yelp.com\u002F2019\u002F04\u002FScaling-Jira-Server-Administration-For-The-Enterprise.html)\n\t* [Auto-scaling CI\u002FCD cluster at Flexport](https:\u002F\u002Fflexport.engineering\u002Fhow-flexport-halved-testing-costs-with-an-auto-scaling-ci-cd-cluster-8304297222f)\n\n## Availability\n* [Resilience Engineering: Learning to Embrace Failure](https:\u002F\u002Fqueue.acm.org\u002Fdetail.cfm?id=2371297)\t\n\t* [Resilience Engineering with Project Waterbear at LinkedIn](https:\u002F\u002Fengineering.linkedin.com\u002Fblog\u002F2017\u002F11\u002Fresilience-engineering-at-linkedin-with-project-waterbear)\n\t* [Resiliency against Traffic Oversaturation at iHeartRadio](https:\u002F\u002Ftech.iheart.com\u002Fresiliency-against-traffic-oversaturation-77c5ed92a5fb)\n\t* [Resiliency in Distributed Systems at GO-JEK](https:\u002F\u002Fblog.gojekengineering.com\u002Fresiliency-in-distributed-systems-efd30f74baf4)\n\t* [Practical NoSQL Resilience Design Pattern for the Enterprise at eBay](https:\u002F\u002Fwww.ebayinc.com\u002Fstories\u002Fblogs\u002Ftech\u002Fpractical-nosql-resilience-design-pattern-for-the-enterprise\u002F)\n\t* [Ensuring Resilience to Disaster at Quora](https:\u002F\u002Fquoraengineering.quora.com\u002FEnsuring-Quoras-Resilience-to-Disaster)\n\t* [Site Resiliency at Expedia](https:\u002F\u002Fwww.infoq.com\u002Fpresentations\u002Fexpedia-website-resiliency?utm_source=presentations_about_Case_Study&utm_medium=link&utm_campaign=Case_Study)\n\t* [Resiliency and Disaster Recovery with Kafka at eBay](https:\u002F\u002Ftech.ebayinc.com\u002Fengineering\u002Fresiliency-and-disaster-recovery-with-kafka\u002F)\n\t* [Disaster Recovery for Multi-Region Kafka at Uber](https:\u002F\u002Feng.uber.com\u002Fkafka\u002F)\n* [Failover](http:\u002F\u002Fcloudpatterns.org\u002Fmechanisms\u002Ffailover_system)\n\t* [The Evolution of Global Traffic Routing and Failover](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon16\u002Fprogram\u002Fpresentation\u002Fheady)\n\t* [Testing for Disaster Recovery Failover Testing](https:\u002F\u002Fwww.usenix.org\u002Fconference\u002Fsrecon17asia\u002Fprogram\u002Fpresentation\u002Fliu_zehua)\n\t* [Designing a Microservices Architecture for Failure](https:\u002F\u002Fblog.risingstack.com\u002Fdesigning-microservices-architecture-for-failure\u002F)\n\t* [ELB for Automatic Failover at GoSquared](https:\u002F\u002Fengineering.gosquared.com\u002Fuse-elb-automatic-failover)\n\t* [Eliminate the Database for Higher Availability at American Exp","awesome-scalability 是一个专注于大规模系统可扩展性、可靠性和性能模式的资源列表。该项目汇集了业界知名工程师的文章和真实案例研究，涵盖设计原则、可扩展性、可用性、稳定性、性能优化及智能系统构建等多个方面。它适合需要解决系统性能瓶颈或高并发问题的技术团队参考，也适用于准备系统设计面试的个人学习。此外，对于希望了解如何有效管理技术团队以提高产出的企业管理者来说，其中关于组织架构的内容也非常有价值。",2,"2026-06-11 02:35:57","top_all"]