├── .gitignore ├── AWS Architecture └── README.md ├── Airbnb Engineering └── README.md ├── Architecture-In-Practice └── README.md ├── Backend Systems Stuff └── README.md ├── Blockchain Architecture └── README.md ├── Bloggging (Medium, ..) Architecture └── README.md ├── C1B Problem └── README.md ├── CD-CI-OPs-Prod-Systems └── README.md ├── Chrome Design └── README.md ├── Content Delivery Network └── README.md ├── DB-Data Engineering └── README.md ├── Decentralized App (DApps) └── README.md ├── Design Patterns └── README.md ├── Discord Engineering └── README.md ├── Distributed Systems └── README.md ├── Dropbox Engineering └── README.md ├── E-Commerce Architecture └── README.md ├── Facebook Architecture └── README.md ├── Financial Systems & Algo-Trading └── README.md ├── Flipkart Engineering └── README.md ├── GitHub Engineering └── README.md ├── Hotstar Engineering └── README.md ├── IDEs-Architecture └── README.md ├── Instagram Architecture └── README.md ├── Instant Messaging └── README.md ├── Intuit Engineering └── README.md ├── LICENSE ├── ML-NN Architectures └── README.md ├── Netflix Architecture └── README.md ├── Payment Architectures └── README.md ├── Platform Reliablility └── README.md ├── PubSub Architecture └── README.md ├── README.md ├── Scalability └── README.md ├── Secure Design └── README.md ├── Serverless Architecture └── README.md ├── Slack Engineering └── README.md ├── Snapdeal Engineering └── README.md ├── Software Architecture Patterns └── README.md ├── Spotify Engineering └── README.md ├── Swiggy Engineering └── README.md ├── System Design Basics └── README.md ├── Twitch Engineering └── README.md ├── Twitter Architecture └── README.md ├── Uber Engineering └── README.md ├── Web-App-Engineering └── README.md ├── Webhook Architecture └── README.md ├── Yelp Architecture └── README.md ├── Youtube Architecture └── README.md ├── Zomato Engineering └── README.md ├── _config.yml └── system-design.PNG /.gitignore: -------------------------------------------------------------------------------- 1 | # Prerequisites 2 | *.d 3 | 4 | # Compiled Object files 5 | *.slo 6 | *.lo 7 | *.o 8 | *.obj 9 | 10 | # Precompiled Headers 11 | *.gch 12 | *.pch 13 | 14 | # Compiled Dynamic libraries 15 | *.so 16 | *.dylib 17 | *.dll 18 | 19 | # Fortran module files 20 | *.mod 21 | *.smod 22 | 23 | # Compiled Static libraries 24 | *.lai 25 | *.la 26 | *.a 27 | *.lib 28 | 29 | # Executables 30 | *.exe 31 | *.out 32 | *.app 33 | -------------------------------------------------------------------------------- /AWS Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Amazon/AWS Engineering Posts : 2 | 3 | * [Scaling to a Million Users](http://highscalability.com/blog/2016/1/11/a-beginners-guide-to-scaling-to-11-million-users-on-amazons.html) 4 | * [How Software is developed at Amazon?](http://highscalability.com/blog/2019/3/4/how-is-software-developed-at-amazon.html) 5 | * [Why Amazon Retail Went To A Service Oriented Architecture?](http://highscalability.com/blog/2016/7/13/why-amazon-retail-went-to-a-service-oriented-architecture.html) 6 | * [Discovering Hot Topics using Machine Learning](https://aws.amazon.com/blogs/architecture/discovering-hot-topics-using-machine-learning/) 7 | * [Building a Serverless Outbreak Management Solution with AWS Data Lab](https://aws.amazon.com/blogs/architecture/building-a-serverless-outbreak-management-solution-with-aws-data-lab/) 8 | * [How Amazon Is Using AI To Better Understand Customer Search Queries](https://analyticsindiamag.com/how-amazon-is-using-ai-to-better-understand-customer-search-queries/) 9 | * [Snap Optimizes Cost Savings While Storing Over 1.5 Trillion Photos and Videos on Amazon S3 Glacier Instant Retrieval](https://aws.amazon.com/solutions/case-studies/snap-case-study/?did=cr_card&trk=cr_card) 10 | * [AWS RDS Readable Standby -- InfoQ](https://www.infoq.com/news/2022/01/aws-rds-readable-standby) 11 | * [Lumos: Amazon’s internal, large-scale serverless payments system](https://www.youtube.com/watch?v=8DkwUeZeVHo) 12 | * [Netflix Realizes Multi-Region Resiliency on Amazon Route 53](https://www.youtube.com/watch?v=WDDkLOT8SCk&list=PLhr1KZpdzukdeX8mQ2qO73bg6UKQHYsHb&index=12) 13 | * [Netflix & Amazon SES Case Study](https://aws.amazon.com/ses/netflix-ses-case-study/) 14 | * [Fix This Podcast](https://aws.amazon.com/solutions/case-studies/fix-this/?podcast-list.sort-by=item.additionalFields.DatePublished&podcast-list.sort-order=desc&awsf.tech-category-filter=*all&awsf.industry-filter=*all) 15 | * [Formula 1: Using Amazon SageMaker to Deliver Real-Time Insights to Fans](https://aws.amazon.com/blogs/architecture/formula-1-using-amazon-sagemaker-to-deliver-real-time-insights-to-fans-live/) 16 | * [Dream11: Scaling a Fantasy Sports Platform with 5M Daily Active Users](https://aws.amazon.com/blogs/architecture/scaling-fantasy-sports-platform/) 17 | -------------------------------------------------------------------------------- /Airbnb Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Airbnb Engineering Links 2 | 3 | - [How Airbnb is Moving 10x Faster at Scale with GraphQL and Apollo](https://medium.com/airbnb-engineering/how-airbnb-is-moving-10x-faster-at-scale-with-graphql-and-apollo-aa4ec92d69e2) 4 | - [A Deep Dive into Airbnb’s Server-Driven UI System](https://medium.com/airbnb-engineering/a-deep-dive-into-airbnbs-server-driven-ui-system-842244c5f5) 5 | - [How We Enable Airbnb Team Members to Code Like a Mobile Engineer](https://medium.com/airbnb-engineering/how-we-enable-airbnb-team-members-to-code-like-a-mobile-engineer-d7181a20399f) 6 | - [Improving Deep Learning for Ranking Stays at Airbnb](https://medium.com/airbnb-engineering/improving-deep-learning-for-ranking-stays-at-airbnb-959097638bde) 7 | - [How Airbnb Standardized Metric Computation at Scale](https://medium.com/airbnb-engineering/airbnb-metric-computation-with-minerva-part-2-9afe6695b486) 8 | - [How Airbnb Achieved Metric Consistency at Scale](https://medium.com/airbnb-engineering/how-airbnb-achieved-metric-consistency-at-scale-f23cc53dea70) 9 | - [How to Tame Your Service APIs: Evolving Airbnb’s Architecture](https://www.youtube.com/watch?v=yI91FSghAL4) 10 | - [The Human Side of Airbnb’s Microservice Architecture](https://www.youtube.com/watch?v=yGOtTd-l_3E) 11 | - [Airbnb, From Monolith to Microservices: How to Scale Your Architecture](https://www.youtube.com/watch?v=N1BWMW9NEQc) 12 | - [Airbnb Streamlines the Development Process with a Unified Architecture for Collaborative Hosting](https://www.infoq.com/news/2021/12/airbnb-unified-architecture/) 13 | - [Graph Machine Learning at Airbnb](https://medium.com/airbnb-engineering/graph-machine-learning-at-airbnb-f868d65f36ee) 14 | - [Unified Payments Data Read at Airbnb](https://medium.com/airbnb-engineering/unified-payments-data-read-at-airbnb-e613e7af1a39) 15 | - [Automated Incident Management Through Slack](https://medium.com/airbnb-engineering/incident-management-ae863dc5d47f) 16 | - [Beyond A/B Test : Speeding up Airbnb Search Ranking Experimentation through Interleaving](https://medium.com/airbnb-engineering/beyond-a-b-test-speeding-up-airbnb-search-ranking-experimentation-through-interleaving-7087afa09c8e) 17 | - [Mussel — Airbnb’s Key-Value Store for Derived Data](https://medium.com/airbnb-engineering/mussel-airbnbs-key-value-store-for-derived-data-406b9fa1b296) 18 | -------------------------------------------------------------------------------- /Architecture-In-Practice/README.md: -------------------------------------------------------------------------------- 1 | # Some Backend Tools/Languages/Frameworks 2 | 3 | I am mentioning those with which I am familiar with (have atleast worked with them in one or more projects). 4 | 5 | - Languages: Golang, Nodejs, Python 6 | - IaaS Platforms: AWS, OpenStack, DigitalOcean, etc. 7 | - Service Mesh: Linkerd, Istio 8 | - API Gateways: Gloo, Ambassador, Contour, Envoy, Nginx, etc. 9 | - Distributed Tracing: Jaeger, Honeycomb, OpenTelemetry, OpenCensus, OpenTracing, Zipkin, Lightstep 10 | - Visualization and Monitoring: Grafana, PagerDuty 11 | - Logging: FluentD, FluentBit, Sumo Logic, Rollbar, Splunk, etc. 12 | - Continuous/Progressive Deployment: Flux/GitOps, Argo, Flagger 13 | - Continuous Integration: JenkinsX, TravisCI, CircleCI, Jenkins, GitHub Actions, etc. 14 | - Scripting: Jsonnet, Bash, Python, etc. 15 | - Networking: DNS, Routing, Firewalls, Load balancers, etc. 16 | - Databases: MongoDB or other NoSQL database, PostgreSQL, MySQL, Time Series Database 17 | 18 | Short description of tools and links. 19 | 20 | - [Postman](https://www.youtube.com/watch?v=VywxIQ2ZXw4&list=RDCMUC8butISFwT-Wl7EV0hUK0BQ&index=4) 21 | - [Kong](https://konghq.com/) 22 | - [Heroku](https://www.heroku.com/products) 23 | - [Netlify](https://www.netlify.com/products/) 24 | - [Terraform](https://www.terraform.io/) 25 | - [Superbase](https://supabase.io/docs) 26 | - [Insomnia](https://insomnia.rest/) 27 | - [Docker](https://docs.docker.com/) 28 | 29 | ## Emerging Trends 30 | 31 | - [Emerging Trends in Software Architecture](https://www.oreilly.com/library/view/software-architecture-a/9788131707494/ch07.html) 32 | - [Software Architecture and Design InfoQ Trends Report—April 2020](https://www.infoq.com/articles/architecture-trends-2020/) 33 | - [AWS Code Catalyst: A ‘Low-Code’ Approach for the Dev Lifecycle](https://thenewstack.io/aws-code-catalyst-a-low-code-approach-for-the-dev-lifecycle) 34 | -------------------------------------------------------------------------------- /Backend Systems Stuff/README.md: -------------------------------------------------------------------------------- 1 | ## Backend Systems 2 | 3 | - [Manage Your APIs Like a 4-Star Restaurant](https://thenewstack.io/manage-your-apis-like-a-4-star-restaurant/) 4 | - [SerenityOS: Building an Operating System from Scratch](https://thenewstack.io/building-an-operating-system-from-scratch-serenityos/) 5 | - [Splunk Platform with Spiros Xanthos](https://softwareengineeringdaily.com/2022/02/22/splunk-platform-with-spiros/) 6 | - [Why We Switched from Python to Go](https://softwareengineeringdaily.com/2021/03/03/why-we-switched-from-python-to-go/) 7 | - [The Rise of Platform Engineering](https://softwareengineeringdaily.com/2020/02/13/setting-the-stage-for-platform-engineering/) 8 | - [System Design — Google Maps](https://mecha-mind.medium.com/system-design-google-maps-c9dddca72df5) 9 | - [System Design — Design a distributed job scheduler (KISS Interview series)](https://medium.com/@raxshah/system-design-design-a-distributed-job-scheduler-kiss-interview-series-753107c0104c) 10 | - [SE Daily - Knowledge-Based Programming with Stephen Wolfram](https://softwareengineeringdaily.com/2015/11/10/knowledge-based-programming-with-stephen-wolfram/) 11 | - [TV Input Format Architecture -- Hardware*](https://source.android.com/devices/tv) 12 | - [What Is Cloud Computing? According To ChatGPT.](http://highscalability.com/blog/2022/12/16/what-is-cloud-computing-according-to-chatgpt.html) 13 | - [Metrics, Logs and Traces: More Similar Than They Appear?](https://thenewstack.io/metrics-logs-and-traces-more-similar-than-they-appear/) 14 | 15 | ### Eventual Consistency & CAP Theorem 16 | 17 | - [Building High Scale Backend Systems](https://www.youtube.com/watch?v=8lHr8T5JIJs) 18 | - [https://www.allthingsdistributed.com/2008/12/eventually_consistent.html](https://www.allthingsdistributed.com/2008/12/eventually_consistent.html) 19 | - [https://levelup.gitconnected.com/eventual-consistency-what-how-and-why-50c942472a0c](https://levelup.gitconnected.com/eventual-consistency-what-how-and-why-50c942472a0c) 20 | - [https://medium.com/swlh/go-microservice-with-clean-architecture-a-major-upgrade-34a4cedb0b06](https://medium.com/swlh/go-microservice-with-clean-architecture-a-major-upgrade-34a4cedb0b06) 21 | - [https://stackoverflow.com/questions/3414277/cqrs-eventual-consistencyhttps://stackoverflow.com/questions/3414277/cqrs-eventual-consistency](https://stackoverflow.com/questions/3414277/cqrs-eventual-consistencyhttps://stackoverflow.com/questions/3414277/cqrs-eventual-consistency) 22 | - [https://docs.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/microservice-application-design](https://docs.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/microservice-application-design) 23 | - [https://stackoverflow.com/questions/5466012/nosql-and-eventual-consistency-real-world-examples](https://stackoverflow.com/questions/5466012/nosql-and-eventual-consistency-real-world-examples) 24 | - [https://medium.com/dev-genius/microservices-design-api-gateway-pattern-980e8d02bdd5](https://medium.com/dev-genius/microservices-design-api-gateway-pattern-980e8d02bdd5) 25 | - [https://www.youtube.com/watch?v=LAsMrghdFP0](https://www.youtube.com/watch?v=LAsMrghdFP0) 26 | - [Cap Theorem : https://mwhittaker.github.io/blog/an_illustrated_proof_of_the_cap_theorem/](https://mwhittaker.github.io/blog/an_illustrated_proof_of_the_cap_theorem/) 27 | - [Yahoo! CAP](https://edisciplinas.usp.br/pluginfile.php/2541318/mod_resource/content/1/TeoremaDeBrewer.pdf) 28 | - [Consistent Hashing Algorithm](http://highscalability.com/blog/2023/2/22/consistent-hashing-algorithm.html) 29 | -------------------------------------------------------------------------------- /Blockchain Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Dear Blockchain Engineer 2 | 3 | - Read and get a fair understanding of the Bitcoin whitepaper. The next is a bit daunting but do it in your free time, clone the Bitcoin repo and go over 4 | the source code, see if you can co-relate with paper and code in the repo. 5 | - Learn Solidity Programming Language and move to truffle or brownie based systems for easy code, build and testing infrastructure. 6 | - [Advanced] Give a through read to Ethereum white paper. Understand EVM, stack, bytecode, gas computation. 7 | - There are a few standards that one must be aware of, ERC-721 and ERC-1155 token standards are absolutely necessary. 8 | - Learn about the Byzantine Generals Problem and how it was solved. Learn about consensus problem and ask `Is Blockchain necessary?` when you encounter a similar problem? 9 | - Proof of Work is absolutely necessary, Proof-of-stake maybe. 10 | 11 | ## What is Blockchain ? 12 | 13 | - [Bitcoin Original Paper](https://bitcoin.org/bitcoin.pdf) 14 | - [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf) 15 | - [Crypto and NFTs Dominate the Headlines, but Smart Money Bets on Web3](https://thenewstack.io/crypto-and-nfts-dominate-the-headlines-but-smart-money-bets-on-web3/) 16 | - [Modular Blockchain Architecture with Nader Dabit](https://softwareengineeringdaily.com/2022/08/29/modular-blockchain-architecture/) 17 | - [Solana White Paper](https://solana.com/solana-whitepaper.pdf) 18 | - [Solana blockchain and the Proof of History](https://www.infoworld.com/article/3666736/solana-blockchain-and-the-proof-of-history.html#:~:text=Solana%20is%20considered%20the%20fastest,2022%203%3A00%20am%20PDT) 19 | - [**SE Daily - Web3 & Stuff**](https://softwareengineeringdaily.com/category/web3/) 20 | - [Blockchain for Govt.](https://www.mitre.org/sites/default/files/publications/blockchain-technology-for-government-18-1069.pdf) 21 | - [Understanding Blockchain Fundamentals, Part 1: Byzantine Fault Tolerance](https://medium.com/loom-network/understanding-blockchain-fundamentals-part-1-byzantine-fault-tolerance-245f46fe8419) 22 | - [Consensus Algorithms: The Root Of Blockchain Technology](https://101blockchains.com/consensus-algorithms-blockchain/) 23 | - [https://blog.coinbase.com/blockchain-infrastructure-at-coinbase-366c09dbcef4](https://blog.coinbase.com/blockchain-infrastructure-at-coinbase-366c09dbcef4) 24 | - [The Raft Consensus Algorithm](https://raft.github.io/) 25 | - [Why Web3 Needs a Real-Time Data Layer Now More Than Ever](https://thenewstack.io/why-web3-needs-a-real-time-data-layer-now-more-than-ever/) 26 | - [Cryptocurrency Price Prediction Using Deep Learning](https://towardsdatascience.com/cryptocurrency-price-prediction-using-deep-learning-70cfca50dd3a) 27 | - [Cryptocurrency Prediction with LSTM](https://towardsdatascience.com/cryptocurrency-prediction-with-lstm-4cc369c43d1b) 28 | - [Bittrex API Docs](https://bittrex.github.io/api/v3) 29 | - [Automated Crypto Trading](https://github.com/gkovacs/cs230-cryptocurrency-trading-lstm) 30 | - [Blockchain Architecture @Coinbase](https://blog.coinbase.com/blockchain-infrastructure-at-coinbase-366c09dbcef4) 31 | - [https://www.infoq.com/news/2020/07/coinbase-kubernetes/](https://www.infoq.com/news/2020/07/coinbase-kubernetes/) 32 | - [Coinbase Case Study](https://aws.amazon.com/solutions/case-studies/coinbase/) 33 | - [https://blog.coinbase.com/how-coinbase-builds-secure-infrastructure-to-store-bitcoin-in-the-cloud-b1ba6c3f2c11](https://blog.coinbase.com/how-coinbase-builds-secure-infrastructure-to-store-bitcoin-in-the-cloud-b1ba6c3f2c11) 34 | - [Steamit Blockchain Intro-Paper](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=9261418) 35 | - [Blockchain Solutions & COVID-19](https://www.blockchain-council.org/blockchain/blockchain-based-app-to-make-travel-during-the-pandemic-easier/) 36 | - [the-architecture-of-a-web-3-0-application](https://preethikasireddy.com/post/the-architecture-of-a-web-3-0-application) 37 | - [BEPRO : Network & Testnet Release](https://bepronetwork.medium.com/network-testnet-release-13cbfd1fe50d) 38 | - [**Byzantine General's Problem**](https://river.com/learn/what-is-the-byzantine-generals-problem/) 39 | - [RAFT Protocol](https://raft.github.io/) 40 | - [RAFT Explained – Part 1/3: Introduction to the Consensus Problem](https://blog.container-solutions.com/raft-explained-part-1-the-consenus-problem) 41 | - [**Eth : Ethereum Virtual Machine**](https://ethereum.org/en/developers/docs/evm/) 42 | - [**Eth | Mining POW**](https://ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining/) 43 | - [Dandelion: Redesigning the Bitcoin Network for Anonymity](https://medium.com/mit-security-seminar/dandelion-redesigning-the-bitcoin-network-for-anonymity-eee144b7f51) 44 | - [The Ins and Outs of Decentralized Exchanges](https://hedera.com/learning/decentralized-finance/decentralized-exchanges) 45 | - [A Security Reference Architecture for Blockchains](https://arxiv.org/pdf/1904.06898.pdf) 46 | - [Web 3.0 (BuzzWord for some!)](https://coinmarketcap.com/alexandria/article/what-is-web-3-0) 47 | - [Arweave with Sam Williams](https://softwareengineeringdaily.com/2022/05/12/arweave-with-sam-williams/) 48 | - [How Terra Works?](https://docs.terra.money/docs/learn/protocol.html) 49 | - [Automated Trading with Coinrule: https://coinrule.com/](https://coinrule.com/) 50 | - [Web 3.0 versus the previous stacks.](https://www.linkedin.com/posts/alexxubyte_systemdesign-coding-interviewtips-activity-6985263220735234048-3cBl?utm_source=share&utm_medium=member_desktop) 51 | - [Blockchain architecture for trusted transactions](https://www.ibm.com/cloud/architecture/architectures/blockchainArchitecture/) 52 | -------------------------------------------------------------------------------- /Bloggging (Medium, ..) Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Posts 2 | 3 | * [Medium Engineering](https://medium.engineering/) 4 | * [Notion -- Notion API](https://www.notion.so/blog/api-ga) 5 | * [GraphQL Server Design @ Medium](https://medium.engineering/graphql-server-design-medium-34862677b4b8) 6 | * [2 Fast 2 Furious: migrating Medium’s codebase without slowing down](https://medium.engineering/2-fast-2-furious-migrating-mediums-codebase-without-slowing-down-84b1e33d81f4) 7 | * [Microservice Architecture at Medium](https://medium.engineering/microservice-architecture-at-medium-9c33805eb74f) 8 | * [Rex: Medium’s Go Recommendations Microservice](https://medium.engineering/rex-mediums-go-recommendation-microservice-e077bc9582a) 9 | * [SE Daily : Substack with Chris Best](https://softwareengineeringdaily.com/2022/03/16/substack-with-chris-best/) 10 | -------------------------------------------------------------------------------- /C1B Problem/README.md: -------------------------------------------------------------------------------- 1 | # What is `epoll` & `C1M` problem? 2 | 3 | E-poll is an answer to the ```C1M``` definitely, `C10M`? Eh! But does it solve ```C1B```? 4 | 5 | * [Epoll Madness](https://medium.com/@copyconstruct/the-method-to-epolls-madness-d9d2d6378642) 6 | * [Async on E-Poll](https://jvns.ca/blog/2017/06/03/async-io-on-linux--select--poll--and-epoll/) 7 | * [The epoll alternative you've never heard about](https://blog.cloudflare.com/io_submit-the-epoll-alternative-youve-never-heard-about/) 8 | * [Using E-Poll Experience at KOINEX](https://medium.com/koinex-crunch/pushman-the-koinex-standard-for-realtime-experience-4122d2715c92) 9 | * [C1M : Troll or Real](https://news.ycombinator.com/item?id=2288301) 10 | * [C10M : How & What](http://highscalability.com/blog/2013/5/13/the-secret-to-10-million-concurrent-connections-the-kernel-i.html) 11 | * [PF_RING C10M Blog](http://c10m.robertgraham.com/) 12 | * [Describing C10M](https://github.com/espoal/C10M) 13 | * [Scalling the Cloud](http://highscalability.com/blog/2010/10/21/machine-vm-cloud-api-rewriting-the-cloud-from-scratch.html) 14 | * [The Secret To 10 Million Concurrent Connections -The Kernel Is The Problem, Not The Solution](http://highscalability.com/blog/2013/5/13/the-secret-to-10-million-concurrent-connections-the-kernel-i.html) 15 | 16 | -------------------------------------------------------------------------------- /CD-CI-OPs-Prod-Systems/README.md: -------------------------------------------------------------------------------- 1 | ## Deployments 2 | 3 | - [What is build automation? Must know for CD/CI](https://en.wikipedia.org/wiki/Build_automation) 4 | - [Introducing Skynet: Infrastructure as Code for Gojek](https://blog.gojek.io/introducing-skynet/) 5 | - [SE Daily : Software Supply Chain with Barak Schoster](https://softwareengineeringdaily.com/2022/03/10/software-supply-chain-with-barak-schoster/) 6 | - https://docs.travis-ci.com/user/for-beginners/ 7 | - https://buddy.works/ 8 | - https://travis-ci.org/ 9 | - [What Is Platform Engineering?](https://www.gartner.com/en/articles/what-is-platform-engineering) 10 | - [The Rise of Platform Engineering](https://softwareengineeringdaily.com/2020/02/13/setting-the-stage-for-platform-engineering/) 11 | - [Building Containerized GO applications.](https://www.youtube.com/watch?v=eFQIHyuVYoc) 12 | - [Ninja Build System (C/C++/Go)](https://www.aosabook.org/en/posa/ninja.html) 13 | - https://circleci.com/docs/2.0/concepts/ 14 | - https://circleci.com/docs/2.0/deployment-integrations/#using-orbs-to-simplify-deployment 15 | - [TypeForm's Production : Deep Purple](https://medium.com/typeforms-engineering-blog/typeforms-production-smoke-testing-building-our-tool-deep-purple-8d3ff85d3438) 16 | - [Semaphore CD/CI](https://semaphoreci.com/blog/cicd-pipeline#:~:text=CI%2C%20short%20for%20Continuous%20Integration,the%20entire%20software%20release%20process.) 17 | - [Failing Forward — How We Grow from Incidents](https://engineering.atspotify.com/2022/05/failing-forward-how-we-grow-from-incidents/) 18 | - [SE Daily : Union.ai with Ketan Umare](https://softwareengineeringdaily.com/2022/03/23/union-ai-with-ketan-umare/) 19 | - https://www.freecodecamp.org/news/what-i-learned-during-production-deployment-fe037a6ee4db 20 | - https://cloud.google.com/appengine/docs/standard/nodejs/building-app/deploying-web-service 21 | - https://docs.oracle.com/cd/E19199-01/817-5759/dep_architect.html 22 | - https://www.algoexpert.io/systems/workspace/Design%20A%20Code-Deployment%20System 23 | - https://www.youtube.com/watch?v=uEVmD6n8Il0 24 | - https://softwareengineeringdaily.com/2018/01/13/the-gravity-of-kubernetes/ 25 | - https://thenewstack.io/what-you-can-learn-from-the-aws-tokyo-outage/ 26 | - https://analyticsindiamag.com/a-beginners-guide-to-mlops/ 27 | - https://www.youtube.com/watch?v=j7VZsCCnptM 28 | - https://www.youtube.com/watch?v=X3F3El_yvFg 29 | - https://www.youtube.com/watch?v=fqMOX6JJhGo 30 | - [Discord and Spotify Downtime](https://www.youtube.com/watch?v=JcKEnhNQHYY) 31 | - https://www.nginx.com/resources/library/microservices-up-and-running/?utm_medium=paid-display&utm_source=infoq&utm_campaign=ww-nx_pgkub&utm_content=eb-sponsoredupdate 32 | - [Increase Your DevOps Productivity Using Infrastructure as Low Code](https://dzone.com/articles/increase-your-devops-productivity-using-infrastruc) 33 | - [Implementing smoke testing in production and staging. DIY vs Ad-Hoc Tool](https://frontendrobot.com/blog/implementing-smoke-testing-in-production/) 34 | - [GitOps on Kubernetes: Deciding Between Argo CD and Flux](https://thenewstack.io/gitops-on-kubernetes-deciding-between-argo-cd-and-flux/) 35 | - [LightSys: Lightweight and Efficient CI System for Improving Integration Speed of Software](https://www.youtube.com/watch?v=i_iSo1lwJJk&t=253s) 36 | - [A simple yet effective approach to network monitoring](https://www.digitalocean.com/blog/a-glimpse-into-network-availability) 37 | - [Infrastructure as Code with Rob Hirschfeld](https://softwareengineeringdaily.com/2022/01/14/infrastructure-as-code-with-rob/) 38 | - [SE Daily: Flowdash with Nick Gervasi](https://softwareengineeringdaily.com/2022/01/19/flowdash-with-nick-gervasi/) 39 | - [SE Daily: Rackspace with Jeff DeVerter](https://softwareengineeringdaily.com/2022/01/26/rackspace-with-jeff-deverter/) 40 | - [SE Daily: Warp Terminal for all(DevOps Eng.)](https://softwareengineeringdaily.com/2022/04/07/warp-terminal-with-zach-lloyd/) 41 | - [SE Daily: [Kubernetes Spend with Webb Brown](https://softwareengineeringdaily.com/2022/06/16/kubernetes-spend-with-webb-brown/)] 42 | 43 | ## Topics 44 | 45 | - [Infrastructure-as-Code: 6 Best Practices for Securing Applications](https://thenewstack.io/infrastructure-as-code-6-best-practices-for-securing-applications/) 46 | - [Infrastructure-as-Code is the building block for scalable technology](https://blogs.oracle.com/startup/post/infrastructure-as-code-is-the-building-block-for-scalable-technology) 47 | - [Decision Making on Prices : Taloflow with LV Jadavji](https://softwareengineeringdaily.com/2022/03/02/taloflow-with-lv-jadavji/) 48 | - [SE Daily : GitOps and Policy Management with Alexis Richardson and Mohamed Ahmed](https://softwareengineeringdaily.com/2022/03/30/gitops-and-policy-management-with-alexis-richardson-and-mohamed-ahmed/) 49 | - [Machine Learning Pipeline: Architecture of ML Platform in Production](https://www.altexsoft.com/blog/machine-learning-pipeline/) 50 | -------------------------------------------------------------------------------- /Chrome Design/README.md: -------------------------------------------------------------------------------- 1 | ## Google Chrome/ Browsers / JavaScript 2 | 3 | How do browsers works? (with some JS topics) 4 | 5 | - [Inside look at modern web browser (part 1)](https://developers.google.com/web/updates/2018/09/inside-browser-part1) 6 | - [Inside look at modern web browser (part 2)](https://developers.google.com/web/updates/2018/09/inside-browser-part2) 7 | - [Inside look at modern web browser (part 3)](https://developers.google.com/web/updates/2018/09/inside-browser-part3) 8 | - [Inside look at modern web browser (part 4)](https://developers.google.com/web/updates/2018/09/inside-browser-part4) 9 | - [JavaScript Event Loop](https://developer.mozilla.org/en-US/docs/Web/JavaScript/EventLoop) 10 | - [Event Loop & Async JS : Intro](https://www.youtube.com/watch?v=8zKuNo4ay8E) 11 | - [Some more Tech Stuff on Chrome](https://www.chromium.org/developers/design-documents) 12 | - [Chrome UI Source](https://source.chromium.org/chromium#chromium/src/ui/views/) 13 | - [Chromium : Multi-Process Architecture](https://www.chromium.org/developers/design-documents/multi-process-architecture) 14 | - [Security vulnerabilities in modern web browser architecture](https://www.researchgate.net/publication/224163004_Security_vulnerabilities_in_modern_web_browser_architecture) 15 | - [Improve Largest Contentful Paint (LCP) on Your Website With Ease](https://css-tricks.com/improve-largest-contentful-paint-lcp-on-your-website-with-ease/) 16 | - [How JavaScript Works🔥 🤖 [Visually Explained]](https://dev.to/narottam04/how-javascript-works-visually-explained-269j) 17 | - [Internals of Firefox](https://fullyoptimized.files.wordpress.com/2011/09/conceptualarchitectureoffirefox6.pdf) 18 | - [Explore the Magic Behind Google Chrome](https://zicodeng.medium.com/explore-the-magic-behind-google-chrome-c3563dbd2739) 19 | -------------------------------------------------------------------------------- /Content Delivery Network/README.md: -------------------------------------------------------------------------------- 1 | ## CDN Architectures 2 | 3 | Trust Akamai! 4 | 5 | - [What is a CDN?](https://www.imperva.com/learn/performance/what-is-cdn-how-it-works#how-cdn-works) 6 | - [Akamai -- What is a CDN?](https://learn.akamai.com/en-us/webhelp/cloud-embed/cloud-embed-implementation-guide/GUID-17593129-056B-4B39-983A-3D0DD25CC06D.html) 7 | - [CDN Basics](https://www.imperva.com/learn/performance/cdn-architecture/) 8 | - [Frontend Optimizations : File Compression](https://www.imperva.com/learn/performance/front-end-optimization-feo/#file-compression) 9 | - [Reverse Proxy](https://www.f5.com/services/resources/glossary/reverse-proxy) 10 | - [An Analysis of Internet Content Delivery Systems](https://research.cs.washington.edu/networking/websys/pubs/osdi_2002/osdi.pdf) 11 | - [Attacking a Macro Security Problem with Micro-segmentation](https://www.akamai.com/blog/security/attacking-a-macro-security-problem-with-micro-segmentation) 12 | - [System Design: Design a URL Shortener like TinyURL](https://www.youtube.com/watch?v=zgIyzEEXfiA) 13 | -------------------------------------------------------------------------------- /DB-Data Engineering/README.md: -------------------------------------------------------------------------------- 1 | ## Database Systems 2 | 3 | - [Apache Cassandra Architecture Fundamentals](https://blog.yugabyte.com/apache-cassandra-architecture-how-it-works-lightweight-transactions/) 4 | - [Database Content On InfoQ](https://www.infoq.com/database/?itm_source=infoq&itm_medium=header_graybar&itm_campaign=topic_clk) 5 | - [SE Daily : Couchbase Architecture with Ravi Mayuram](https://softwareengineeringdaily.com/2022/01/28/couchbase-architecture-with-ravi/) 6 | - [SE Daily : RudderStack Engineering with Soumaydeb Mitra](https://softwareengineeringdaily.com/2022/03/16/rudderstack-engineering-with-soumaydeb-mitra/) 7 | - [10 Things You Should Know About Running MongoDB At Scale](http://highscalability.com/blog/2014/3/5/10-things-you-should-know-about-running-mongodb-at-scale.html) 8 | - [What is a Vector Database?](https://www.pinecone.io/learn/vector-database/?utm_medium=link&utm_source=high-scalability&utm_campaign=sponsored) 9 | - [Design patterns. Short and clear. Part 5: Database Patterns.](https://it.badykov.com/blog/2018/11/05/database-patterns/) 10 | - [Scaling PlanetScale with Sugu Sougoumarane](https://softwareengineeringdaily.com/2022/01/31/scaling-planetscale-with-sugu-sougoumarane/) 11 | - [6 Data Import Challenges Facing Software Developers](https://softwareengineeringdaily.com/2022/01/15/6-data-import-challenges-facing-software-developers/) 12 | - [The growing pains of database architecture](https://www.figma.com/blog/how-figma-scaled-to-multiple-databases/) 13 | - [SE Daily : DuckDB with Hannes Muleisen](https://softwareengineeringdaily.com/2022/03/18/duckdb-with-hannes-muleisen/) 14 | - [Massive Scale Databases](https://itnext.io/massive-scale-databases-5b5917ed94e5) 15 | - [Swiggy’s Generative AI Journey: A Peek Into the Future](https://blog.swiggy.com/2023/07/20/swiggys-generative-ai-journey-a-peek-into-the-future/) 16 | - [Aggregates, Entities and Value Objects in Domain-Driven Design](https://www.infoq.com/news/2015/01/aggregates-value-objects-ddd/?itm_source=presentations_about_DesignPattern&itm_medium=link&itm_campaign=DesignPattern) 17 | - [Domain-Driven Design with Onion Architecture](https://www.infoq.com/news/2014/10/ddd-onion-architecture/?itm_source=presentations_about_DesignPattern&itm_medium=link&itm_campaign=DesignPattern) 18 | - [PayPal Adopts GraphQL: Gains Increased Developer Productivity](https://www.infoq.com/news/2021/10/paypal-graphql/?itm_source=presentations_about_Case_Study&itm_medium=link&itm_campaign=Case_Study) 19 | - [Netlify Graph Aims to Simplify External API Integration in Web Apps](https://www.infoq.com/news/2022/02/netlify-graph-web-apps-api/?itm_campaign=rightbar_v2&itm_source=infoq&itm_medium=news_link&itm_content=link_text) 20 | - [InfluxData with Zoe Steinkamp](https://softwareengineeringdaily.com/2021/12/15/influxdata-with-zoe-steinkamp/) 21 | - [SE Daily : Why Everyone Needs a Data Privacy Vault](https://softwareengineeringdaily.com/2022/03/12/why-everyone-needs-a-data-privacy-vault/) 22 | - [SE Daily : Apache Hudi](https://softwareengineeringdaily.com/2022/03/08/apache-hudi-with-vinoth-chandar/) 23 | - [SingleStore with Jordan Tigani](https://softwareengineeringdaily.com/2022/03/28/singlestore-with-jordan-tigani/) 24 | - [Data Engineering Trends with Lior Gavish and James Densmore](https://softwareengineeringdaily.com/2022/04/04/data-engineering-trends-with-lior-gavish-and-james-densmore/) 25 | - [GraphQL, meet LiveGraph: a real-time data system at scale](https://www.figma.com/blog/livegraph-real-time-data-fetching-at-figma/) 26 | - [Redis Data Types: The Basics](https://thenewstack.io/redis-data-types-the-basics/) 27 | - [SE Daily : TimeSeries InfluxDB](https://softwareengineeringdaily.com/2022/04/14/time-series-iot-on-influxdb-with-brian-gilmore/) 28 | - [Airbyte Engineering with Michel Tricot](https://softwareengineeringdaily.com/2022/04/26/airbyte-engineering-with-michel-tricot/) 29 | - [Starburst Infrastructure with Justin Borgman](https://softwareengineeringdaily.com/2022/04/28/starburst-infrastructure-with-justin-borgman/) 30 | - [SE Daily : CloudGraph with Tyson Kunovsky](https://softwareengineeringdaily.com/2022/05/21/cloudgraph-with-tyson-kunovsky/) 31 | - [Ballerina: a Data-Oriented Programming Language](https://www.infoq.com/articles/ballerina-data-oriented-language/?topicPageSponsorship=2db34777-a828-4199-8777-865da05e8838&itm_source=articles_about_architecture-design&itm_medium=link&itm_campaign=architecture-design) 32 | - [https://www.scylladb.com/2022/04/27/shaving-40-off-googles-b-tree-implementation-with-go-generics/](https://www.scylladb.com/2022/04/27/shaving-40-off-googles-b-tree-implementation-with-go-generics/) 33 | - [A Golang-based, scalable, high-performance, high availability distributed time series database](https://github.com/lindb/lindb) 34 | -------------------------------------------------------------------------------- /Decentralized App (DApps)/README.md: -------------------------------------------------------------------------------- 1 | # DApps Architecture 2 | 3 | - [https://decrypt.co/resources/dapps](https://decrypt.co/resources/dapps) 4 | - [https://www.stateofthedapps.com/](https://www.stateofthedapps.com/) 5 | - [https://www.zastrin.com/courses/ethereum-primer/lessons/1-5](https://www.zastrin.com/courses/ethereum-primer/lessons/1-5) 6 | - [Architecture for DApps](https://www.freecodecamp.org/news/how-to-design-a-secure-backend-for-your-decentralized-application-9541b5d8bddb/) 7 | - [Tron DApps](https://tron.network/) 8 | - [How Uniswap works?](https://docs.uniswap.org/protocol/V2/concepts/protocol-overview/how-uniswap-works) 9 | - [What Is Avalanche (AVAX)?](https://academy.binance.com/en/articles/what-is-avalanche-avax) 10 | - [Decentralized Autonomous Organisations DAO in Solidity](https://m.youtube.com/watch?v=rD8AxZ_wBA4&feature=youtu.be) 11 | -------------------------------------------------------------------------------- /Design Patterns/README.md: -------------------------------------------------------------------------------- 1 | # Software Design Patterns 2 | 3 | - [PageObject Pattern : Testing Web pages](https://martinfowler.com/bliki/PageObject.html) 4 | - [https://reactjs.org/docs/design-principles.html](https://reactjs.org/docs/design-principles.html) 5 | - [SOLID : Uncle Bob Lecture](https://www.youtube.com/watch?v=zHiWqnTWsn4) 6 | - [Python Design Patterns](https://www.youtube.com/watch?v=bsyjSW46TDg) 7 | - [More Python Stuff](https://www.youtube.com/watch?v=Er5K_nR5lDQ&list=PLaL2yxczKLcBQIHFvQmjI47Qtwg8MpGHN&index=1) 8 | - [More Python Design Patterns](https://www.youtube.com/watch?v=4KZx8bATBFs&list=PLaL2yxczKLcBQIHFvQmjI47Qtwg8MpGHN&index=2) 9 | - [Source Making : Design Patterns Examples](https://sourcemaking.com/design_patterns) 10 | - [Anti Patterns in Software Development](https://sourcemaking.com/antipatterns/software-development-antipatterns) 11 | - [Refactoring Guru](https://refactoring.guru/design-patterns) 12 | - [Azure Docs : Sidecar pattern](https://www.google.com/search?q=side+car+microservice&oq=side+car+microservice+&aqs=chrome..69i57j0i10i22i30.4916j0j7&sourceid=chrome&ie=UTF-8) 13 | - [SOLID in CPP](https://corecppil.github.io/Meetups/2020-05-26_CoreCpp_Worldwide!/The_SOLID_Principles.pdf) 14 | - [System design practice: designing a payment system](https://www.linkedin.com/pulse/system-design-practice-designing-payment-avik-das) 15 | - [Future of Data Engineering](https://www.youtube.com/watch?v=ZZr9oE4Oa5U) 16 | -------------------------------------------------------------------------------- /Discord Engineering/README.md: -------------------------------------------------------------------------------- 1 | ## Resources 2 | 3 | - [Elixir for C1M](https://blog.discord.com/using-rust-to-scale-elixir-for-11-million-concurrent-users-c6f19fc029d3) 4 | - [Some info on WebRTC](https://www.html5rocks.com/en/tutorials/webrtc/infrastructure/) 5 | - [WebRTC Discord](https://blog.discord.com/how-discord-handles-two-and-half-million-concurrent-voice-users-using-webrtc-ce01c3187429) 6 | - [Memomry Leak @Discord React](https://blog.discord.com/discord-react-memory-leak-565c89763e8) 7 | - [Discord Blog : Store a billion messages](https://blog.discord.com/how-discord-stores-billions-of-messages-7fa6ec7ee4c7) 8 | - [InShort : Discord's Backend Architecture](https://www.youtube.com/watch?v=S3tLp_eKjbk) 9 | - [Discord Blogs](https://blog.discord.com/how-discord-maintains-performance-while-adding-features-28ddaf044333) 10 | - [Why Discord is Sticking with React Native](https://blog.discord.com/why-discord-is-sticking-with-react-native-ccc34be0d427) 11 | - [How Discord Maintains Performance While Adding Features](https://blog.discord.com/how-discord-maintains-performance-while-adding-features-28ddaf044333) 12 | - [How-discord-creates-insights-from-trillions-of-data-points](https://discord.com/blog/how-discord-creates-insights-from-trillions-of-data-points) 13 | - [Building open-source design tools to improve Discord’s design workflow](https://blog.discord.com/building-open-source-design-tools-to-improve-discords-design-workflow-9a25c29f9143) 14 | - [INVESTIGATING DISCORD’S REACT MEMORY LEAK](https://discord.com/blog/investigating-discords-react-memory-leak) 15 | - [How Discord Indexes Billions of Messages](https://blog.discord.com/how-discord-indexes-billions-of-messages-e3d5e9be866f) 16 | - [HOW DATA SCIENCE INFORMS STRATEGY & INNOVATION AT DISCORD](https://discord.com/blog/how-data-science-informs-strategy-innovation-at-discord) 17 | - [USING MACHINE LEARNING TO BUILD A DELIGHTFUL NOTIFICATION EXPERIENCE](https://discord.com/blog/building-delightful-notifications-using-ml) 18 | -------------------------------------------------------------------------------- /Distributed Systems/README.md: -------------------------------------------------------------------------------- 1 | # Distributed Systems 2 | 3 | ## Some Basic Articles : 4 | 5 | - A Thorough Introduction to Distributed Systems 6 | - [FreeCodeCamp Article](https://www.freecodecamp.org/news/a-thorough-introduction-to-distributed-systems-3b91562c9b3c/#:~:text=A%20distributed%20system%20in%20its,affecting%20the%20whole%20system's%20uptime.) 7 | - What is a Distributed System? 8 | - [What is a Distributed System?](https://blog.stackpath.com/distributed-system/) 9 | - An Introduction to Distributed Systems 10 | - [An Introduction to Distributed Systems](http://webdam.inria.fr/Jorge/html/wdmch15.html) 11 | - Distributed System Un-mystified 12 | - [Google : Introduction to Distributed System Design](https://www.hpcs.cs.tsukuba.ac.jp/~tatebe/lecture/h23/dsys/dsd-tutorial.html#Design) 13 | - [The Anatomy of a Distributed System](https://www.youtube.com/watch?v=1TIzPL4878Q) 14 | - [**Distributed Systems in One Lesson by Tim Berglund**](https://www.youtube.com/watch?v=Y6Ev8GIlbxc) 15 | - [Lamport Clock](https://martinfowler.com/articles/patterns-of-distributed-systems/lamport-clock.html) 16 | - [As a Software Developer, Why Should You Care about the Monotonic Clock?](https://itnext.io/as-a-software-developer-why-should-you-care-about-the-monotonic-clock-7d9c8533595c) 17 | - [Making a Domain Name Service](https://circleid.com/posts/the_design_of_the_domain_name_system_part_i) 18 | 19 | ## Streaming in Distributed Systems : 20 | 21 | - [Streaming Concepts & Introduction to Flink Series - What is Stream Processing & Apache Flink](https://www.youtube.com/watch?v=ZU1r7uEAO7o) 22 | - [SF 2017: Monal Daxini - Stream Processing with Flink at Netflix](https://www.youtube.com/watch?v=sPB8w-YXX1s) 23 | - ["Apache Kafka and the Next 700 Stream Processing Systems" by Jay Kreps](https://www.youtube.com/watch?v=9RMOc0SwRro) 24 | - [Flink Forward : Keynote | Stream Processing at LinkedIn: Then and Now - Renu Tewari](https://www.youtube.com/watch?v=ukrEShAOJtI) 25 | 26 | ## Examples & More Links : 27 | 28 | - How Google Works? 29 | - [https://www.baselinemag.com/c/a/Infrastructure/How-Google-Works-1](https://www.baselinemag.com/c/a/Infrastructure/How-Google-Works-1) 30 | - Example 1 31 | - [Google Distributed Architecture](http://highscalability.com/google-architecture) 32 | - Lamport & Vector Clocks 33 | - [https://medium.com/@balrajasubbiah/lamport-clocks-and-vector-clocks-b713db1890d7](https://medium.com/@balrajasubbiah/lamport-clocks-and-vector-clocks-b713db1890d7) 34 | - Kafka as a Distributed Sytem : 35 | - [https://www.infoq.com/presentations/kafka-controller-zookeeper/](https://www.infoq.com/presentations/kafka-controller-zookeeper/) 36 | 37 | ## References 38 | 39 | - [Apache Flink](https://www.youtube.com/watch?v=Z4Gx7SP1E14) 40 | - [Designing Distributed Systems: Patterns and Paradigms for Scalable, Reliable Services](https://www.amazon.in/Designing-Distributed-Systems-Brendan-Burns/dp/1491983647) 41 | - [Rearchitecting apps for scale](https://blog.coinbase.com/rearchitecting-apps-for-scale-db438d058e79) 42 | - [Confluent -- Event-Driven architectures](https://www.confluent.io/resources/event-driven-microservices/?utm_medium=display&utm_source=google&utm_campaign=ch.display_tp.rmkt_tgt.key-page-visit-no-hva-discovery_rgn.india_lng.eng_dv.all_con.event-driven-microservice-whitepaper&utm_term=&creative=alc2-confluent-180Days&device=c&placement=&gclid=Cj0KCQiAutyfBhCMARIsAMgcRJSuqHFbODW-SGnf7zOcQNz622QGMnI2Jgi0riOBcCXs-O-h6M15VXoaArg9EALw_wcB) 43 | -------------------------------------------------------------------------------- /Dropbox Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Dropbox Engineering 2 | 3 | - [Drop Box Architecture Discussions](https://www.dropboxforum.com/t5/Dropbox-files-folders/Architecture-pattern-used-by-Dropbox/td-p/340542) 4 | - [Simple Drop Box from scratch on RoR](https://code.tutsplus.com/tutorials/build-a-dropbox-like-file-sharing-site-with-ruby-on-rails--net-17940) 5 | - [Google Drive : Design Example](https://towardsdatascience.com/system-design-analysis-of-google-drive-ca3408f22ed3) 6 | - [Architecture Compare : Google Drive](https://blogs.commons.georgetown.edu/cctp-820-fall2018/2018/11/20/the-architecture-of-google-drive) 7 | - [Fighting the forces of clock skew when syncing password payloads](https://dropbox.tech/application/dropbox-passwords-clock-skew-payload-sync-merge) 8 | - [That time we unplugged a data center to test our disaster readiness](https://dropbox.tech/infrastructure/disaster-readiness-test-failover-blackhole-sjc) 9 | -------------------------------------------------------------------------------- /E-Commerce Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## E-Commerce Architecture 2 | 3 | - [Initial Amazon Architecture](http://highscalability.com/amazon-architecture) 4 | - [How Is Software Developed At Amazon?](http://highscalability.com/blog/2019/3/4/how-is-software-developed-at-amazon.html) 5 | - [System Design Shopify eCommerce platform Interview Question for software engineers](https://www.youtube.com/watch?v=lEL4F_0J3l8) 6 | - [eCommerce Website like Amazon - System Design Interview Question](https://www.youtube.com/watch?v=b67C1Ou9b1Y) 7 | - [Design eCommerce Website (Part I)](http://blog.gainlo.co/index.php/2016/08/22/design-ecommerce-website-part/) 8 | - [Design eCommerce Website (Part II)](http://blog.gainlo.co/index.php/2016/08/28/design-ecommerce-website-part-ii/) 9 | - [Design and Implementation of E-Commerce Site for Online Shopping](https://opus.govst.edu/cgi/viewcontent.cgi?article=1079&context=capstones) 10 | - [Amazon Science (ML) : Data on correlated products and sellers helps improve demand forecasting](https://www.amazon.science/blog/data-on-correlated-products-and-sellers-helps-improve-demand-forecasting) 11 | -------------------------------------------------------------------------------- /Facebook Architecture/README.md: -------------------------------------------------------------------------------- 1 | # Main Blogs 2 | - [Facebook Engineering Blogs](https://engineering.fb.com/) 3 | 4 | ## Articles 5 | - [Production Engineering @Facebook](https://engineering.fb.com/production-engineering/async/) 6 | - [System@Scale Facebook](https://www.facebook.com/atscaleevents/videos/332024971479280/) 7 | - [Facebook Tao Graph - Easy](http://blog.gaurav.im/2016/12/29/system-design-facebook-tao/) 8 | - [Facebook Tao Paper - Usenix Original](https://www.usenix.org/system/files/conference/atc13/atc13-bronson.pdf) 9 | - [How UI redesigns happens at Facebook?](https://engineering.fb.com/2020/05/08/web/facebook-redesign/) 10 | - [Running Border Gateway Protocol in large-scale data centers](https://engineering.fb.com/2021/05/13/data-center-engineering/bgp/) 11 | - [Scale@Introduction Facebook](https://www.infoq.com/presentations/Scale-at-Facebook/) 12 | - [RAMP-TAO](https://engineering.fb.com/2021/08/18/core-data/ramp-tao/) 13 | - [ZippyDB: The Architecture of Facebook’s Strongly Consistent Key-Value Store](https://www.infoq.com/news/2021/09/facebook-zippydb/) 14 | - [Learn from Outrages](https://engineering.fb.com/2021/10/04/networking-traffic/outage/) 15 | - [Scaling Facebook Live Videos to a Billion Users](https://www.youtube.com/watch?v=IO4teCbHvZw) 16 | - [Production Engineering -- SLICK: Adopting SLOs for improved reliability @FB](https://engineering.fb.com/2021/12/13/production-engineering/slick/) 17 | - [Engineering FB : Ribbon Filter](https://engineering.fb.com/2021/07/09/data-infrastructure/ribbon-filter/) 18 | - [HyperLogLog @Facebook](https://engineering.fb.com/2018/12/13/data-infrastructure/hyperloglog/) 19 | - [Facebook Engineering Process with Kent Beck](https://softwareengineeringdaily.com/2019/08/28/facebook-engineering-process-with-kent-beck/) 20 | - [Facebook's Photo Storage Architecture - scaleyourapp.com](https://www.scaleyourapp.com/facebook-photo-storage-architecture/) 21 | - [Facebook Timeline: Brought To You By The Power Of Denormalization](http://highscalability.com/blog/2012/1/23/facebook-timeline-brought-to-you-by-the-power-of-denormaliza.html) 22 | - [Scale at Facebook](https://www.infoq.com/presentations/Scale-at-Facebook/) 23 | -------------------------------------------------------------------------------- /Financial Systems & Algo-Trading/README.md: -------------------------------------------------------------------------------- 1 | ## Algorithmic Trading. 2 | 3 | - [ATS @Scale](http://www.turingfinance.com/algorithmic-trading-system-architecture-post/#prettyPhoto) 4 | - [Quanti - ATS](https://blog.quantinsti.com/automated-trading-system/) 5 | - [Machine Learning -- Quanti](https://blog.quantinsti.com/tag/machine-learning/) 6 | - [Algorithmic Trading Strategies](https://algorithmictrading.net/project/robust-algorithmic-trading-strategies/) 7 | - [Agent-Human Interactions in the Continuous Double Auction](http://spider.sci.brooklyn.cuny.edu/~parsons/courses/840-spring-2005/notes/das.pdf) 8 | - [Deep Reinforcement Learning in Quantitative Algorithmic Trading: A Review](https://arxiv.org/abs/2106.00123) 9 | - [Algorithmic Trading : Papers with Code](https://paperswithcode.com/task/algorithmic-trading) 10 | - [A3C Trading Strategy](https://github.com/evgps/a3c_trading) 11 | - [Deep Reinforcement Learning for Automated Stock Trading](https://towardsdatascience.com/deep-reinforcement-learning-for-automated-stock-trading-f1dad0126a02) 12 | - [How To Automate The Stock Market Using FinRL (Deep Reinforcement Learning Library)?](https://analyticsindiamag.com/stock-market-prediction-using-finrl/) 13 | - [Deep Reinforcement Learning for Algorithmic Trading](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3812473) 14 | - [*Low Latency* High Frequency Trading](https://www.arista.com/en/solutions/low-latency-high-frequency-financial-trading-networks) 15 | - [*Turing Finance* Algorithmic Trading System Architecture](http://www.turingfinance.com/algorithmic-trading-system-architecture-post/) 16 | - [Stock Market Prices Do Not Follow Random Walks](http://www.turingfinance.com/stock-market-prices-do-not-follow-random-walks/) 17 | - [Why Big Data & Intelligent Middleware will revolutionize Financial trading…(part 1 of 3)](https://www.vamsitalkstech.com/aml/why-big-data-intelligent-middleware-will-revolutionize-financial-trading-part-1-of-3/) 18 | - [Simple and Boring -- but works like a charm and delivers like a pro !](https://vladmihalcea.com/revogain-software-architecture/) 19 | - [Deep Learning for Trading -- *https://ml4trading.io*](https://ml4trading.io/chapter/16) 20 | - [Deep Trading](https://github.com/Rachnog/Deep-Trading) 21 | - [Applying Machine Learning to Financial Payments](https://www.infoq.com/presentations/machine-learning-financial-payments/?topicPageSponsorship=b7a60f52-8c62-4239-94dd-1d3b5d5b3c20&itm_source=presentations_about_MachineLearning&itm_medium=link&itm_campaign=MachineLearning) 22 | - [Strange Loop Conference : "Building Financial Systems on Eventually Consistent DBs" by Rahul Pilani](https://www.youtube.com/watch?v=KH0l8QqhzYk) 23 | - [MetaTrader Business](https://www.metatrader5.com/en) 24 | - [AmiBroker Application](https://www.amibroker.com/) 25 | - [TradingView](https://in.tradingview.com/) 26 | - [Bitski: Web3 Infrastructure with Patrick Tescher](https://softwareengineeringdaily.com/2022/04/01/bitski-web3-infrastructure-with-patrick-tescher/) 27 | -------------------------------------------------------------------------------- /Flipkart Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Flipkart Engineering 2 | 3 | - [Flipkart Backend Blogs](https://tech.flipkart.com/tagged/backend) 4 | - [Searching Flipkart Data Catalog with Apache Jena](https://tech.flipkart.com/searching-flipkart-data-catalog-with-apache-jena-8398cc66fd2e) 5 | - [Dockerized Frontend Applications in Flipkart](https://tech.flipkart.com/dockerized-frontend-applications-in-flipkart-e73ae9177fa0) 6 | - [Building Personalized Search Autosuggestion](https://tech.flipkart.com/building-personalized-autosuggestion-9e705d5bf5f8) 7 | - [Predicting your next query even before you type!](https://tech.flipkart.com/predicting-your-next-query-even-before-you-type-83487a34109d) 8 | - [Flipkart Data Platform — India’s largest eCommerce Big Data Platform](https://tech.flipkart.com/overview-of-flipkart-data-platform-20c6d3e9a196) 9 | - [Sherlock: Near Real Time Search Indexing](https://tech.flipkart.com/sherlock-near-real-time-search-indexing-95519783859d) 10 | - [Foxtrot — Event Analytics At Scale](https://tech.flipkart.com/foxtrot-event-analytics-at-scale-bdcdc75402dc) 11 | - [AESOP change propagation system](https://tech.flipkart.com/aesop-change-propagation-system-a4c0f2a0d242) 12 | - [Making deliveries faster — The Flipkart Cache Cluster](https://tech.flipkart.com/making-deliveries-faster-the-flipkart-cache-cluster-953659c06a3a) 13 | - [Palette Image Generate — Technology to the rescue](https://tech.flipkart.com/palette-image-generation-technology-to-the-rescue-22000aac34b3) 14 | - [Optimizing Flipkart’s Serviceability Data from 300 GB to 150 MB in-memory](https://tech.flipkart.com/remodelling-flipkarts-serviceability-data-an-optimization-journey-from-300-gb-to-150-mb-in-memory-5c7e9c38bde) 15 | - [Running a multi-region Zookeeper](https://tech.flipkart.com/running-a-multi-region-zookeeper-58e52cec44ff) 16 | - [Memory Tuning a High Throughput Microservice](https://tech.flipkart.com/memory-tuning-a-high-throughput-microservice-ed57b3e60997) 17 | - [Predicting your next query even before you type!](https://medium.com/flipkart-engineering/predicting-your-next-query-even-before-you-type-83487a34109d) 18 | -------------------------------------------------------------------------------- /GitHub Engineering/README.md: -------------------------------------------------------------------------------- 1 | # GitHub Engineering & Architecture Posts 2 | 3 | - [GitHub : New Queue](https://github.blog/2008-10-30-the-new-queue/) 4 | - [History : Version Control System](https://medium.com/@willhayjr/the-architecture-and-history-of-git-a-distributed-version-control-system-62b17dd37742) 5 | - [Design & Concepts : Version Control](https://homes.cs.washington.edu/~mernst/advice/version-control.html) 6 | - [How we scaled the GitHub API with a sharded, replicated rate limiter in Redis](https://github.blog/2021-04-05-how-we-scaled-github-api-sharded-replicated-rate-limiter-redis/) 7 | - [How we found and fixed a rare race condition in our session handling](https://github.blog/2021-03-18-how-we-found-and-fixed-a-rare-race-condition-in-our-session-handling/) 8 | - [Deployment reliability at GitHub](https://github.blog/2021-02-03-deployment-reliability-at-github/) 9 | - [Visual Globe : GitHub Globe (UX/UI)](https://github.blog/2020-12-21-how-we-built-the-github-globe/) 10 | - [Why Write ADRs](https://github.blog/2020-08-13-why-write-adrs/) 11 | - [Vulcanizer: a library for operating Elasticsearch](https://github.blog/2019-03-05-vulcanizer-a-library-for-operating-elasticsearch/) 12 | - [How GitHub Partitioned Its Relational Database to Improve Reliability at Scale](https://www.infoq.com/news/2021/09/GitHub-database-partition/) 13 | -------------------------------------------------------------------------------- /Hotstar Engineering/README.md: -------------------------------------------------------------------------------- 1 | ## Hotstar 2 | 3 | - [Re-Architecting Apps For Scale](https://blog.hotstar.com/re-architecting-apps-for-scale-d4639b91e0c3) 4 | - [Scaling hotstar.com for 25 million concurrent viewers](https://www.youtube.com/watch?v=QjvyiyH4rr0) 5 | - [https://tech.hotstar.com/](https://tech.hotstar.com/) 6 | -------------------------------------------------------------------------------- /IDEs-Architecture/README.md: -------------------------------------------------------------------------------- 1 | - [Understanding Visual Studio Code architecture](https://franz-ajit.medium.com/understanding-visual-studio-code-architecture-5fc411fca07) 2 | - [VSCode Architecture And Overview](https://www.c-sharpcorner.com/article/vscode-architecture-and-overview/) 3 | - [Monorepos](https://www.toptal.com/front-end/guide-to-monorepos) 4 | - [Fleet Below Deck, Part I – Architecture Overview](https://blog.jetbrains.com/fleet/2022/01/fleet-below-deck-part-i-architecture-overview/) 5 | - [Fleet Below Deck, Part II – Breaking down the editor](https://blog.jetbrains.com/fleet/2022/02/fleet-below-deck-part-ii-breaking-down-the-editor/) 6 | -------------------------------------------------------------------------------- /Instagram Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Instagram Blogs 2 | 3 | * [Instagram : Fast, auto-generated streaming JSON parsing for Android](https://instagram-engineering.com/fast-auto-generated-streaming-json-parsing-for-android-ab8e7be21033) 4 | * [Scaling Instagram Infrastructure](https://www.youtube.com/watch?v=hnpzNAPiC0E) 5 | * [Insta Cloud 3 rules](https://medium.com/@DataStax/instagram-engineerings-3-rules-to-a-scalable-cloud-application-architecture-c44afed31406) 6 | * [Designing Instagram](https://www.educative.io/courses/grokking-the-system-design-interview/m2yDVZnQ8lG) 7 | * [Making instagram.com faster: Part-1](https://instagram-engineering.com/making-instagram-com-faster-part-1-62cc0c327538) 8 | * [Making instagram.com faster: Cache First!](https://instagram-engineering.com/making-instagram-com-faster-part-3-cache-first-6f3f130b9669) 9 | * [Making instagram.com faster: Code size and execution optimizations (Part 4)](https://instagram-engineering.com/making-instagram-com-faster-code-size-and-execution-optimizations-part-4-57668be796a8) 10 | * [Instagram Data Saver Mode](https://instagram-engineering.com/instagram-data-saver-mode-ffb01fd5a6bd) 11 | * [Five things I learned about working on content quality at Instagram](https://instagram-engineering.com/five-things-i-learned-about-working-on-content-quality-at-instagram-5031b1342bea) 12 | * [Thundering Herds & Promises](https://instagram-engineering.com/thundering-herds-promises-82191c8af57d) 13 | * [Engineering the Instagram Stories Team](https://instagram-engineering.com/engineering-the-instagram-stories-team-e16ec62e364d) 14 | * [**Messaging at Scale at Instagram (Old)**](https://www.youtube.com/watch?v=E708csv4XgY) 15 | -------------------------------------------------------------------------------- /Instant Messaging/README.md: -------------------------------------------------------------------------------- 1 | ## Instant Messaging 2 | 3 | - [Instant Messaging and the Signal Protocol - Computerphile](https://www.youtube.com/watch?v=DXv1boalsDI) 4 | - [The WhatsApp Architecture Facebook Bought For $19 Billion](http://highscalability.com/blog/2014/2/26/the-whatsapp-architecture-facebook-bought-for-19-billion.html) 5 | - [Scaling to Millions of Simultaneous Connections: Rick Reed](https://vimeo.com/44312354) 6 | - [What's Up WhatsApp? (Jan Koum, CEO at WhatsApp & David Rowan)](https://www.youtube.com/watch?v=WgAtBTpm6Xk&feature=youtu.be) 7 | - [yowsup WhatsApp Python Lib for Communication](https://github.com/tgalal/yowsup/wiki/Architecture) 8 | - [IBM Blog : XMPP Architecture](https://developer.ibm.com/technologies/messaging/tutorials/x-xmppintro/) 9 | - [WhatsApp Engineering at Scale : FB Blog](https://developers.facebook.com/videos/f8-2016/a-look-at-whatsapp-engineering-for-success-at-scale/) 10 | - [How WhatsApp enables multi-device capability](https://engineering.fb.com/2021/07/14/security/whatsapp-multi-device/) 11 | - [DIT — enabling de-identified data collection on WhatsApp](https://engineering.fb.com/2021/04/16/security/dit/) 12 | - [Project LightSpeed: Rewriting the Messenger codebase for a faster, smaller, and simpler messaging app](https://engineering.fb.com/2020/03/02/data-infrastructure/messenger/) 13 | - [Data Transfer Project: Enabling portability of photos and videos between services](https://engineering.fb.com/2019/12/02/security/data-transfer-project/) 14 | - [WhatsApp Business API Reference : Can you implement an API service to mimic it?](https://developers.facebook.com/docs/whatsapp/on-premises/reference) 15 | - [Pinterest Engineering](https://softwareengineeringdaily.com/2022/01/11/pinterest-engineering/) 16 | - [Designing WhatsApp](http://highscalability.com/blog/2022/1/3/designing-whatsapp.html) 17 | - [Snap refactored!](https://www.protocol.com/enterprise/snap-microservices-aws-google-cloud) 18 | - [Design Twitter - System Design Interview](https://www.youtube.com/watch?v=o5n85GRKuzk) 19 | -------------------------------------------------------------------------------- /Intuit Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Intuit Engineering 2 | 3 | - [How Intuit’s Platform Engineering Team Chose an App Definition](https://thenewstack.io/how-intuits-platform-engineering-team-chose-an-app-definition/) 4 | - [Numaproj — Driving Dev Velocity with Real-time Analytics, AIOps on Kubernetes](https://medium.com/intuit-engineering/numaproj-driving-dev-velocity-with-real-time-analytics-aiops-on-kubernetes-fba62e00eecf) 5 | - [Securing Your Network Today for a Post-Quantum Future: Why and How](https://medium.com/intuit-engineering/securing-your-network-today-for-a-post-quantum-future-why-and-how-3ca79340c561) 6 | - [Intuit Persistence Service: A Paved Road for Persistence](https://medium.com/intuit-engineering/intuit-persistence-service-a-paved-road-for-persistence-2aca0e22653a) 7 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /ML-NN Architectures/README.md: -------------------------------------------------------------------------------- 1 | ## Machine Learning (OPs, NN etc..) 2 | 3 | - [Product Lessons from ML Home: Spotify’s One-Stop Shop for Machine Learning](https://engineering.atspotify.com/2022/01/product-lessons-from-ml-home-spotifys-one-stop-shop-for-machine-learning/) 4 | - [Practical Machine Learning in JavaScript with Charlie Gerard](https://softwareengineeringdaily.com/2022/01/04/practical-ml-with-charlie-gerard/) 5 | - [SingleStore with Jordan Tigani](https://softwareengineeringdaily.com/2022/03/28/singlestore-with-jordan-tigani/) 6 | - [YOLO: Real-Time Object Detection Explained](https://www.v7labs.com/blog/yolo-object-detection) 7 | - [The Essential Guide to Neural Network Architectures](https://www.v7labs.com/blog/neural-network-architectures-guide) 8 | - [Neural Style Transfer: Everything You Need to Know [Guide]](https://www.v7labs.com/blog/neural-style-transfer) 9 | - [MLOps -- Continuous Delivery for Machine Learning on AWS](https://d1.awsstatic.com/whitepapers/mlops-continuous-delivery-machine-learning-on-aws.pdf) 10 | - [How ChatGPT works?](https://www.linkedin.com/posts/alexxubyte_systemdesign-coding-interviewtips-activity-7026228879040081920--KQ4?utm_source=share&utm_medium=member_desktop) 11 | -------------------------------------------------------------------------------- /Netflix Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Netflix Blogs and System Design 2 | 3 | * [Netflix OSS](https://github.com/Netflix) 4 | * [Netflix System Design Part-1](https://dev.to/gbengelebs/netflix-system-design-how-netflix-onboards-new-content-2dlb) 5 | * [Netflix System Design Part-2](https://dev.to/gbengelebs/netflix-system-design-backend-architecture-10i3) 6 | * [Netflix on AWS Full Series](https://aws.amazon.com/solutions/case-studies/netflix/?trk=global_employee_advocacy&sc_channel=sm&advocacy_source=everyonesocial&es_id=94a141c779) 7 | * [Netflix: What Happens When You Press Play?](http://highscalability.com/blog/2017/12/11/netflix-what-happens-when-you-press-play.html) 8 | * [Lessons for Architectural Design](https://www.nginx.com/blog/microservices-at-netflix-architectural-best-practices/) 9 | * [How Netflix works](https://medium.com/refraction-tech-everything/how-netflix-works-the-hugely-simplified-complex-stuff-that-happens-every-time-you-hit-play-a40c9be254b#:~:text=Such%20a%20structure%20is%20what,resources%20are%20its%20very%20own.) 10 | * [A Design Analysis of Cloud-based Microservices Architecture at Netflix](https://medium.com/swlh/a-design-analysis-of-cloud-based-microservices-architecture-at-netflix-98836b2da45f) 11 | * [Netflix Play API: Building an Evolutionary Architecture](https://www.infoq.com/news/2019/01/netflix-evolution-architecture/) 12 | * [Netflix Billing Migration to AWS — Part III](https://netflixtechblog.com/netflix-billing-migration-to-aws-part-iii-7d94ab9d1f59) 13 | * [Artwork Personalization at Netflix](https://netflixtechblog.com/artwork-personalization-c589f074ad76) 14 | * [Full Cycle Developers at Netflix — Operate What You Build](https://netflixtechblog.com/full-cycle-developers-at-netflix-a08c31f83249) 15 | * [Scaling Patterns for Netflix's Edge](https://www.infoq.com/presentations/netflix-edge-scalability-patterns/) 16 | * [A 360 Degree View Of The Entire Netflix Stack](http://highscalability.com/blog/2015/11/9/a-360-degree-view-of-the-entire-netflix-tack.htmlhttp://highscalability.com/blog/2015/11/9/a-360-degree-view-of-the-entire-netflix-stack.html) 17 | * [The Eternal Cost Savings Of Netflix's Internal Spot Market](http://highscalability.com/blog/2017/12/4/the-eternal-cost-savings-of-netflixs-internal-spot-market.html) 18 | * [book-notes/high-scalability-notes.markdown Netflix](https://github.com/mgp/book-notes/blob/master/high-scalability-notes.markdown) 19 | * [Paper: Netflix’s Transition To High-Availability Storage Systems ](http://highscalability.com/blog/2010/10/22/paper-netflixs-transition-to-high-availability-storage-syste.html) 20 | * [Netflix: Developing, Deploying, And Supporting Software According To The Way Of The Cloud](http://highscalability.com/blog/2011/12/12/netflix-developing-deploying-and-supporting-software-accordi.html) 21 | * [NETFLIX system design](https://medium.com/@narengowda/netflix-system-design-dbec30fede8d) 22 | * [Byte Down: Making Netflix’s Data Infrastructure Cost-Effective](https://netflixtechblog.com/byte-down-making-netflixs-data-infrastructure-cost-effective-fee7b3235032) 23 | * [Comparision : Amazon Prime Video Delivery](https://www.youtube.com/watch?v=2YAz20284FI) 24 | * [Netflix Builds a Reliable, Scalable Platform with Event Sourcing, MQTT and Alpakka-Kafka](https://www.infoq.com/news/2021/08/netflix-device-management/) 25 | * [Scaling Push Messaging for Millions of Devices @Netflix](https://www.youtube.com/watch?v=6w6E_B55p0E) 26 | * [Change Data Capture for Distributed Databases @Netflix](https://www.youtube.com/watch?v=Z4Gx7SP1E14) 27 | * [**QConf :** Netflix Play API - An Evolutionary Architecture](https://www.youtube.com/watch?v=6oPj-DW09DU) 28 | * [Scaling Event Sourcing for Netflix Downloads](https://www.youtube.com/watch?v=rsSld8NycCU) 29 | * [Pattern Matching @ Scale Using Finite State Machine -- Netflix](https://www.youtube.com/watch?v=WykSdgtLDD0) 30 | * [Netflix : Some more design aspects, ytb](https://www.youtube.com/watch?v=MxFt3YsjyQg) 31 | * [SE Daily : Notebooks at Netflix with Matthew Seal](https://softwareengineeringdaily.com/2019/01/15/notebooks-at-netflix-with-matthew-seal/) 32 | * [Designing Netflix](http://highscalability.com/blog/2021/12/13/designing-netflix.html) 33 | * [Cache warming: Leveraging EBS for moving petabytes of data](https://netflixtechblog.medium.com/cache-warming-leveraging-ebs-for-moving-petabytes-of-data-adcf7a4a78c3) 34 | * [Revisiting BetterTLS: Certificate Path Building](https://netflixtechblog.com/revisiting-bettertls-certificate-path-building-4c978b79843f) 35 | * [Why You Can't Talk About Microservices Without Mentioning Netflix](https://smartbear.com/blog/why-you-cant-talk-about-microservices-without-ment/) 36 | * [How Netflix Scales its API with GraphQL Federation (Part 1)](https://netflixtechblog.com/how-netflix-scales-its-api-with-graphql-federation-part-1-ae3557c187e2) 37 | -------------------------------------------------------------------------------- /Payment Architectures/README.md: -------------------------------------------------------------------------------- 1 | ## Payment Gateways 2 | 3 | * [What is a Payment Gateway & How it Works](https://blog.cashfree.com/what-is-a-payment-gateway-india) 4 | * [WHAT IS PAYMENT ORCHESTRATION (AND WHY HAVE IT)?](https://trimplement.com/blog/2021/07/payment-orchestration-layer-definition-benefits/) 5 | * [Payment gateways around the world](https://trimplement.com/blog/2020/02/payment-gateway-basic-definitions/) 6 | * [RazorPay - Online Payment Gateway](https://razorpay.com/blog/payment-gateway-101/) 7 | * [The Architecture that Helps Stripe Move Faster](https://www.infoq.com/presentations/stripe-api-pci/) 8 | * [Payment Checkout : Example](https://docs.paymentwall.com/integration/checkout-home) 9 | * [Payment Checkout : Implementation (React + Stripe)](https://blog.logrocket.com/building-payments-system-react-stripe/) 10 | * [Stripe : Canonical Log Lines](https://stripe.com/blog/canonical-log-lines) 11 | * [How Razorpay’s Notification Service Handles Increasing Load](https://engineering.razorpay.com/how-razorpays-notification-service-handles-increasing-load-f787623a490f) 12 | * [The Life Cycle of an Online Card Payment](https://razorpay.com/blog/how-online-card-payments-work/) 13 | * [**HOW TO DEVELOP A PAYMENT GATEWAY**](https://trimplement.com/blog/2020/06/payment-gateway-development-marketplaces/) 14 | * [Make Money from your API Tutorial](https://www.youtube.com/watch?v=MbqSMgMAzxU) 15 | * [**Architecting a Modern Financial Institution**](https://www.youtube.com/watch?v=VYuToviSx5Q) 16 | * [Bitcoin Transactions - **Intro**](https://www.bitcoin.com/get-started/how-bitcoin-transactions-work/) 17 | * [Refactoring and Optimizing a High Traffic API at PayPal](https://medium.com/paypal-tech/refactoring-and-optimizing-a-high-traffic-api-at-paypal-eb11c373d795) 18 | * [Razorpay -- Building a SAST program at Razorpay’s scale](https://engineering.razorpay.com/building-a-sast-program-at-razorpays-scale-719887fe0aec) 19 | * [Razorpay -- Go Consuming All Your Resources?](https://engineering.razorpay.com/golang-consuming-all-your-resources-5730cac4b61) 20 | * [Lumos: Amazon’s internal, large-scale serverless payments system](https://www.youtube.com/watch?v=8DkwUeZeVHo) 21 | * [UPI Basics: UPI 101](https://blog.setu.co/articles/upi-101-the-basics) 22 | * [Designing a Payment System](https://newsletter.pragmaticengineer.com/p/designing-a-payment-system) 23 | * [Apple Pay vs Google Pay: How Do They Handle Sensitive Card Info?](https://www.youtube.com/watch?v=cHv8LqkbPHk) 24 | -------------------------------------------------------------------------------- /Platform Reliablility/README.md: -------------------------------------------------------------------------------- 1 | # Site Reliability Stuff 2 | 3 | - [10 Things Everybody Needs to Know About Site Reliability Engineering (SRE)](https://blog.newrelic.com/technology/site-reliability-engineering-careers/) 4 | - [https://opensource.com/article/18/10/what-site-reliability-engineer](https://opensource.com/article/18/10/what-site-reliability-engineer) 5 | - [Google SRE](https://sre.google/) 6 | - [Delivering Large-Scale Platform Reliability](https://blog.roblox.com/2022/04/delivering-large-scale-platform-reliability/) 7 | - [SREcon21 - What To Do When SRE is Just a New Job Title?](https://www.youtube.com/watch?v=7l5Kl6RHyOc) 8 | - [Seven Ways to Fail at Microservices with Holly Cummins](https://www.infoq.com/podcasts/seven-ways-failing-microservices/) 9 | -------------------------------------------------------------------------------- /PubSub Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## What is Pub-Sub ? 2 | 3 | * [Simple Yet Comprehensive Pub-Sub](https://www.ably.io/topic/pub-sub) 4 | * [Cloud Pub-Sub Case : Spotify](https://engineering.atspotify.com/2016/03/03/spotifys-event-delivery-the-road-to-the-cloud-part-ii/) 5 | * [PushMan : Koinex Realtime](https://medium.com/koinex-crunch/pushman-the-koinex-standard-for-realtime-experience-4122d2715c92) 6 | * [gRPC Pub-Sub](https://grpc.io/blog/pubsub/) 7 | * [Amazon Simple Notification Service](https://aws.amazon.com/pub-sub-messaging/#:~:text=What%20is%20Pub%2FSub%20Messaging%3F,the%20subscribers%20to%20the%20topic.) 8 | * [Checkout Pub-Nub Mobile Framework -- JS Example](https://www.pubnub.com/docs/platform/quickstarts/javascript) 9 | * [Real-Time Performance Analysis for Publish/Subscribe Systems](http://dsc.soic.indiana.edu/publications/Realtime%20PubSub_Sangyoon.pdf) 10 | * [In-House Pub-Sub using Node.js & Redis.io](https://www.smashingmagazine.com/2018/06/pub-sub-service-in-house-node-js-redis/) 11 | * [Pub/Sub Examples: 5 Use Cases to Understand the Pattern and its Benefits](https://ably.com/blog/pub-sub-pattern-examples) 12 | * [ZeroMQ Python : Tornado Event Loop](https://learning-0mq-with-pyzmq.readthedocs.io/en/latest/pyzmq/multisocket/tornadoeventloop.html) 13 | * [Building a Reactive Architecture Around Redis](https://blog.bitsrc.io/building-a-reactive-architecture-around-redis-bc53662b81c8) 14 | * [Consumer/Producer Kafka](https://iwpnd.pw/articles/2020-03/apache-kafka-fastapi-geostream) 15 | * [Pub-Sub pattern: a brief explanation](https://dev.to/jucian0/pub-sub-pattern-a-brief-explanation-21ed) 16 | * [Pub-Sub using Kafka](https://solace.com/blog/solace-pubsub-vs-kafka-comparison-publish-subscribe-messaging-pattern/) 17 | * [SE Daily : Notifications Infrastructure with Chris Bell](https://softwareengineeringdaily.com/2022/05/24/notifications-infrastructure-with-chris-bell/) 18 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ### System Design Bytes for Enthusiasts 2 | 3 | ![System Design Discussions](https://raw.githubusercontent.com/codersguild/System-Design/master/system-design.PNG) 4 | 5 | I complied and collected some of the articles as a part of doing **CS654A** course at **IIT Kanpur** for a fantastic course on **Advanced Software Architecture** taught by [*Prof.Dr.T.V.Prabbhakar*](https://www.iitk.ac.in/new/index.php/dr-tadinada-venkata-prabhakar). 6 | 7 | Modified from [Zach](https://github.com/checkcheckzz) system design repository. Added more links and topics to cover on both PS/DS & System Design Interviews. We will keep updating this posting from time to time. Some more [awesome resource](https://github.com/binhnguyennus/awesome-scalability) 8 | 9 | [![How to "think" (and design) like a Software Architect at Silicon Valley Code Camp 2019](https://img.youtube.com/vi/mCM6QVHD08c/0.jpg)](https://www.youtube.com/watch?v=mCM6QVHD08c) 10 | 11 | [![Visualising software architecture with the C4 model - Simon Brown, Agile on the Beach 2019](https://img.youtube.com/vi/x2-rSnhpw0g/0.jpg)](https://www.youtube.com/watch?v=x2-rSnhpw0g) 12 | 13 | ## `SYSTEM DESIGN IS NOT JUST FOR INTERVIEWS, IT CAN BE HOW YOU MANAGE YOUR LIFE. GIVE IT A THOUGHT` 14 | 15 | ## Disclaimer/Acknowledgements 16 | 17 | I didn't write the `articles` myself. I love expanding my understanding of `system design` complexities and thus read many books, research papers, and articles that enhance my knowledge. I take the opportunity to thank everyone who found this repository useful. I would like to thank all the authors and developers who wrote the articles aggregated in this repository. 18 | 19 | ## More Content Comming ! 20 | 21 | We are working to create good content to fulfil the needs of system-design noobs. Please feel free to share any resource or material at ```lahiri.devs@gmail.com```. 22 | 23 | - [How Slack Works](https://www.youtube.com/watch?v=WE9c9AZe-DY) 24 | 25 | ## SWEBOOK & PDFs 26 | 27 | - http://swebokwiki.org 28 | - https://cs.fit.edu/~kgallagher/Schtick/Serious/SWEBOKv3.pdf 29 | - [System Design Basics by Aditya Malshikhare](https://www.linkedin.com/feed/update/urn:li:activity:6881853381657321472/?commentUrn=urn%3Ali%3Acomment%3A(ugcPost%3A6881853381124636672%2C6881999479675908096)) 30 | 31 | ## All-Time Favourites 32 | 33 | * [http://highscalability.com/all-time-favorites/](http://highscalability.com/all-time-favorites/) 34 | * [Software Engineering Daily](https://softwareengineeringdaily.com/) 35 | 36 | ## How to prepare system design questions? 37 | 38 | System design is a very broad topic. Even a software engineer with many years of working experience at a top IT company may not be an expert on system design. If you want to become an expert, you need to read many books, articles, and solve real large scale system design problems. 39 | 40 | In order to practice designing a few systems, for the love or learning or preparing for interviews, you can use this [practice platform](https://workat.tech/system-design/practice). 41 | 42 | This repository only teaches you how to handle the system design interview with a systematic approach in a concise way. You can dive into each topic if you have time. Of course, welcome to add your thoughts!. 43 | 44 | ## Table of Contents 45 | - [ ] [System Design Interview Tips & PS/DS](#tips) 46 | - [ ] [Basic Knowledge about System Design](#intro) 47 | - [ ] [Company Engineering Blogs](#blog) 48 | - [ ] [Products and Systems](#system) 49 | - [ ] [Hot Questions and Reference](#qs) 50 | - [ ] [Good Books](#bk) 51 | - [ ] [Object Oriented Design](#ood) 52 | - [ ] [Distributed System Design](#dsd) 53 | - [ ] [Projects to Try](#prjt) 54 | 55 | ### [[⬆]](#toc) System Design Interview Tips & PS/DS 56 | 57 | **Clarify the constraints and identify the user cases** 58 | 59 | Spend a few minutes questioning the interviewer and agreeing on the scope of the system. 60 | Remember to make sure you know all the requirements the interviewer didn't tell you about in the beginning. 61 | 62 | User cases indicate the main functions of the system, and constraints list the scale of the system such as requests 63 | per second, requests types, data written per second, data read per second. 64 | 65 | In a real world scenario, beyond a white-board interview setting one must understand the `functional` & `non-functional` requirements of an 66 | engineering project. 67 | 68 | - [Requirements Engineering](https://medium.com/omarelgabrys-blog/requirements-engineering-introduction-part-1-6d49001526d3) 69 | - [How to manage Modern Software Projects ?](https://medium.com/@lizparody/waterfall-vs-agile-methodology-in-software-development-1e19ef168cf6) 70 | - [A Design Doc : Online Judge (https://www.youtube.com/watch?v=_eRTl_YxgUw)](https://docs.google.com/document/d/1MgoMz8McpZAmAq_hJfn1topocHqfmAhcbqq42zJEMsY/edit) 71 | - [*Important* Data Engineering](https://www.dremio.com/data-lake/data-engineering/) 72 | 73 | **High-level architecture design** 74 | 75 | Sketch the important components and the connections between them, but don't go into some details. 76 | Usually, a scalable system includes webserver (load balancer), service (service partition), database (primary/secondary database cluster plug cache). 77 | 78 | **Component design** 79 | 80 | For each component, you need to write the specific APIs for each component. You may need to finish 81 | the detailed OOD design for a particular function. You may also need to design the database schema for the database. 82 | 83 | **Revist Basic PS/DS & Machine Coding Questions** 84 | 85 | Basics of OOPs, SOLID Concepts, algorithms and data structures will help a lot in clearing most tof the onsite interviews at large tech companies. Having a habit of solving problems on LeetCode or CodeFoces will definitely help in thinking faster and better in terms of approach to problem solving. 86 | 87 | * [What is PS/DS?](https://workat.tech/problem-solving/article/what-is-ps-ds-coding-round-efuatnl7zxju) 88 | * [What is Machine Coding?](https://workat.tech/machine-coding/article/what-is-a-machine-coding-round-omfn1w54ojlg) 89 | * [How to practice for Machine Coding?](https://workat.tech/machine-coding/article/how-to-practice-for-machine-coding-kp0oj3sw2jca) 90 | * [Sample Machine Coding Problems](https://workat.tech/practice) 91 | * [LeetCode Problems](https://leetcode.com/problemset/all/) 92 | * [Try the CodeChef Medium Problems](https://www.codechef.com/problems/medium) 93 | * [Try this as well](https://www.algoexpert.io/product) 94 | 95 | ### [[⬆]](#toc) Basic Knowledge about System Design: 96 | 97 | Here are some articles about system design related topics. 98 | 99 | * [Chaos Engineering](https://principlesofchaos.org/) 100 | * [The New Stack Blogs](https://thenewstack.io/) 101 | * [An Illustrated Proof of the CAP Theorem](https://mwhittaker.github.io/blog/an_illustrated_proof_of_the_cap_theorem/) 102 | * [Educative.io & Other Lists](https://www.8bitmen.com/best-resources-to-learn-software-architecture-system-design/) 103 | * [Node Clean Architecture](https://medium.com/better-programming/node-clean-architecture-deep-dive-ab68e523554b) 104 | * [Services Engineering Resources](https://github.com/mmcgrana/services-engineering) 105 | * [How to Rock a Systems Design Interview](http://www.palantir.com/2011/10/how-to-rock-a-systems-design-interview/) 106 | * [System Interview](http://www.hiredintech.com/app#system-design) 107 | * [SE Daily : Fiverr Engineering with Gil Sheinfeld](https://softwareengineeringdaily.com/2017/11/15/fiverr-engineering-with-gil-scheinfeld/) 108 | * [Scalability for Dummies](http://www.lecloud.net/tagged/scalability) 109 | * [Scalable Web Architecture and Distributed Systems](http://www.aosabook.org/en/distsys.html) 110 | * [Numbers Everyone Should Know](http://everythingisdata.wordpress.com/2009/10/17/numbers-everyone-should-know/) 111 | * [Fallacies of distributed systems](https://pages.cs.wisc.edu/~zuyu/files/fallacies.pdf) 112 | * [Designing Tinder](http://highscalability.com/blog/2022/1/17/designing-tinder.html) 113 | * [Scalable System Design Patterns](http://horicky.blogspot.com/2010/10/scalable-system-design-patterns.html) 114 | * [Introduction to Architecting Systems for Scale](http://lethain.com/introduction-to-architecting-systems-for-scale/) 115 | * [Transactions Across Datacenters](http://snarfed.org/transactions_across_datacenters_io.html) 116 | * [A Plain English Introduction to CAP Theorem](http://ksat.me/a-plain-english-introduction-to-cap-theorem/) 117 | * [The CAP FAQ](https://github.com/henryr/cap-faq) 118 | * [Paxos Made Simple](http://research.microsoft.com/en-us/um/people/lamport/pubs/paxos-simple.pdf) 119 | * [Simple : Consistent Hashing](https://medium.com/omarelgabrys-blog/consistent-hashing-beyond-the-basics-525304a12ba) 120 | * [More On : Consistent Hashing](http://www.tom-e-white.com/2007/11/consistent-hashing.html) 121 | * [NOSQL Patterns](http://horicky.blogspot.com/2009/11/nosql-patterns.html) 122 | * [Emerging Architectures](https://a16z.com/2020/10/15/the-emerging-architectures-for-modern-data-infrastructure/) 123 | * [Scalability, Availability & Stability Patterns](http://www.slideshare.net/jboner/scalability-availability-stability-patterns) 124 | * [Simple Publisher-Subscriber design for Koinex : PushMan](https://medium.com/koinex-crunch/pushman-the-koinex-standard-for-realtime-experience-4122d2715c92) 125 | * [Web Architecture 101](https://engineering.videoblocks.com/web-architecture-101-a3224e126947) 126 | * [Testing in Production: the hard parts](https://medium.com/@copyconstruct/testing-in-production-the-hard-parts-3f06cefaf592) 127 | * [Distributed Tracing — we’ve been doing it wrong](https://medium.com/@copyconstruct/distributed-tracing-weve-been-doing-it-wrong-39fc92a857df) 128 | * [Distributed Consistent Hashing](https://medium.com/ably-realtime/how-to-implement-consistent-hashing-efficiently-fe038d59fff2) 129 | * [System Design White Board](https://www.youtube.com/channel/UCRPMAqdtSgd0Ipeef7iFsKw) 130 | * [Bloom Filter : A Probabilistic Data Structure](https://medium.com/system-design-blog/bloom-filter-a-probabilistic-data-structure-12e4e5cf0638) 131 | * [Basics : ML Architecture](https://www.bmc.com/blogs/machine-learning-architecture) 132 | * [Security By Design](https://blog.threatpress.com/security-design-principles-owasp/) 133 | * [How Netlify’s deploying and routing infrastructure works](https://medium.com/netlify/how-netlifys-deploying-and-routing-infrastructure-works-c90adbde3b8d) 134 | * [Basic Overview of Blockchain](https://www.edureka.co/blog/blockchain-architecture/) 135 | * [Architecting a Machine Learning Pipeline](https://towardsdatascience.com/architecting-a-machine-learning-pipeline-a847f094d1c7) 136 | * [ML Reference Architecture](https://freeandopenmachinelearning.readthedocs.io/en/latest/architecture.html) 137 | * [Reducing Databse Costs](https://scalegrid.io/blog/reducing-your-database-hosting-costs-digitalocean-vs-aws-vs-azure/) 138 | * [Patterns : Thinking About Microservices](https://www.infoq.com/articles/microservices-design-ideals/?itm_source=infoq&itm_medium=popular_widget&itm_campaign=popular_content_list&itm_content=) 139 | * [The Reactive Monolith - How to Move from CRUD to Event Sourcing](https://www.wix.engineering/post/the-reactive-monolith-how-to-move-from-crud-to-event-sourcing) 140 | * [Terraform Software](https://www.terraform.io/) 141 | * [FreeCodeCamp : DevOps Course](https://www.youtube.com/watch?v=j5Zsa_eOXeY) 142 | * [Some Linux Know How is necessary](https://training.linuxfoundation.org/training/linux-kernel-internals-and-development/) 143 | * [Architecture of Open Source Systems](http://aosabook.org/en/index.html) 144 | * [Some Quickstart ML know-how for system design : What to use? Where to use it?](https://youtu.be/VyWAvY2CF9c) 145 | * [Quick : Observability and Microservices](https://www.infoq.com/news/2018/06/observability-microservices/) 146 | * [System Design Interviews](https://www.youtube.com/channel/UC9vLsnF6QPYuH51njmIooCQ) 147 | * [Designing Microservices](https://www.youtube.com/watch?v=j6ow-UemzBc) 148 | * [Crack the System Design Interview - FreeCodeCamp](https://www.freecodecamp.org/news/how-to-system-design-dda63ed27e26/) 149 | * [Intro to Distributed Logging](https://blog.treasuredata.com/blog/2016/08/03/distributed-logging-architecture-in-the-container-era/) 150 | * [Usenix -- Gmail Overview](https://www.usenix.org/legacy/event/webapps10/tech/slides/deboor.pdf) 151 | * [Jeff Dean On Large-Scale Deep Learning At Google](http://highscalability.com/blog/2016/3/16/jeff-dean-on-large-scale-deep-learning-at-google.html) 152 | * [Infinite Memory Transformer: Attending to Arbitrarily Long Contexts Without Increasing Computation Burden 153 | Researchers from Instituto de Telecomunicações.](https://syncedreview.com/2021/09/09/deepmind-podracer-tpu-based-rl-frameworks-deliver-exceptional-performance-at-low-cost-100/) 154 | 155 | Of course, if you want to dive into system related topics, here is a good collection of reading list about [services-engineering](https://github.com/mmcgrana/services-engineering), and 156 | a good collection of material about [distributed systems](http://dancres.github.io/Pages/). 157 | 158 | ### [[⬆]](#toc) Off-topic Blogs: 159 | 160 | * [Architecture of Machine Learning Systems](https://medium.com/louis-dorard/architecture-of-a-real-world-machine-learning-system-795254bec646) 161 | * [Engineering Dependability And Fault Tolerance In A Distributed System - @@Ably](http://highscalability.com/blog/2021/2/19/engineering-dependability-and-fault-tolerance-in-a-distribut.html) 162 | * [Postman API Testing](https://www.youtube.com/watch?v=VywxIQ2ZXw4) 163 | * [Microservices and the Economics of Small Things](https://www.infoq.com/articles/microservices-economics-small-things/?topicPageSponsorship=62547418-6220-4c74-9be8-b11f14b85016&itm_source=articles_about_scalability&itm_medium=link&itm_campaign=scalability) 164 | * [Service Mesh Ultimate Guide - Second Edition: Next Generation Microservices Development](https://www.infoq.com/articles/service-mesh-ultimate-guide-2e/?itm_campaign=rightbar_v2&itm_source=infoq&itm_medium=articles_link&itm_content=link_text) 165 | * [Adoption of Cloud Native Architecture, Part 3: Service Orchestration and Service Mesh](https://www.infoq.com/articles/cloud-native-architecture-adoption-part3/?itm_campaign=rightbar_v2&itm_source=infoq&itm_medium=articles_link&itm_content=link_text) 166 | 167 | ### [[⬆]](#toc) Company Engineering Blogs: 168 | 169 | If you are going to have an onsite with a company, you should read their engineering blog. 170 | 171 | * [InfoQ](https://www.infoq.com/) 172 | * [High Scalability](http://highscalability.com/) 173 | * [Complex Systems: Microservices and Humans](https://www.youtube.com/watch?v=E8A3Yn2Vjx8) 174 | * [The GitHub Blog](https://github.com/blog/category/engineering) 175 | * [Engineering at Quora](http://engineering.quora.com/) 176 | * [Yelp Engineering Blog](http://engineeringblog.yelp.com/) 177 | * [Twitter Engineering](https://engineering.twitter.com/) 178 | * [Facebook Engineering](https://www.facebook.com/Engineering) 179 | * [Yammer Engineering](http://eng.yammer.com/blog/) 180 | * [Etsy Code as Craft](http://codeascraft.com/) 181 | * [Foursquare Engineering Blog](http://engineering.foursquare.com/) 182 | * [Airbnb Engineering](http://nerds.airbnb.com/) 183 | * [WebEngage Engineering Blog](http://engineering.webengage.com/) 184 | * [LinkedIn Engineering](http://engineering.linkedin.com/blog) 185 | * [The Netflix Tech Blog](http://techblog.netflix.com/) 186 | * [BankSimple Simple Blog](https://www.simple.com/engineering/) 187 | * [Square The Corner](http://corner.squareup.com/) 188 | * [SoundCloud Backstage Blog](https://developers.soundcloud.com/blog/) 189 | * [Flickr Code](http://code.flickr.net/) 190 | * [Instagram Engineering](http://instagram-engineering.tumblr.com/) 191 | * [Dropbox Tech Blog](https://tech.dropbox.com/) 192 | * [Cloudera Developer Blog](http://blog.cloudera.com/) 193 | * [Bandcamp Tech](http://bandcamptech.wordpress.com/) 194 | * [Oyster Tech Blog](http://tech.oyster.com/) 195 | * [THE REDDIT BLOG](http://www.redditblog.com/) 196 | * [Groupon Engineering Blog](https://engineering.groupon.com/) 197 | * [Songkick Technology Blog](http://devblog.songkick.com/) 198 | * [Google Research Blog](http://googleresearch.blogspot.com/) 199 | * [Pinterest Engineering Blog](http://engineering.pinterest.com/) 200 | * [Twilio Engineering Blog](http://www.twilio.com/engineering) 201 | * [Bitly Engineering Blog](http://word.bitly.com/) 202 | * [Uber Engineering Blog ](https://eng.uber.com/) 203 | * [Godaddy Engineering](http://engineering.godaddy.com/) 204 | * [Splunk Blog](http://blogs.splunk.com/) 205 | * [Coursera Engineering Blog](https://building.coursera.org/) 206 | * [PayPal Engineering Blog](https://www.paypal-engineering.com/) 207 | * [Nextdoor Engineering Blog](https://engblog.nextdoor.com/) 208 | * [Booking.com Development Blog](https://blog.booking.com/) 209 | * [Scalyr Engineering Blog ](https://blog.scalyr.com/) 210 | * [Architect.io Blog](https://www.architect.io/blog) 211 | * [Ably Engineering Blog](https://ably.com/blog) 212 | * [DoorDash Engineering Blog](https://doordash.engineering/blog/) 213 | 214 | ### [[⬆]](#toc) Products and Systems: 215 | 216 | The following papers/articles/slides can help you to understand the general design idea of different real products and systems. 217 | 218 | * [MapReduce: Simplied Data Processing on Large Clusters](http://static.googleusercontent.com/media/research.google.com/zh-CN/us/archive/mapreduce-osdi04.pdf) 219 | * [Bigtable: A Distributed Storage System for Structured Data](http://www.read.seas.harvard.edu/~kohler/class/cs239-w08/chang06bigtable.pdf) 220 | * [The Google File System](http://static.googleusercontent.com/media/research.google.com/zh-CN/us/archive/gfs-sosp2003.pdf) 221 | * [The Chubby lock service for loosely-coupled distributed systems](http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/archive/chubby-osdi06.pdf) 222 | * [Dynamo: Amazon's Highly Available Key-value Store](http://www.read.seas.harvard.edu/~kohler/class/cs239-w08/decandia07dynamo.pdf) 223 | * [Frontend in React](https://reactjs.org/tutorial/tutorial.html) 224 | * [State Management using Redux](https://redux.js.org/introduction/getting-started) 225 | * [Angular Get Started](https://angular.io/start) 226 | * [First DJango App](https://docs.djangoproject.com/en/3.0/intro/tutorial01/) 227 | * [Build a CRUD Todo app with Django and React/Redux](https://medium.com/technest/build-a-crud-todo-app-with-django-and-react-redux-8ddb0b6ac2f0) 228 | * [The MERN Stack Tutorial – Building A React CRUD Application From Start To Finish](https://codingthesmartway.com/the-mern-stack-tutorial-building-a-react-crud-application-from-start-to-finish-part-1/) 229 | * [Introduction to Memcached](http://www.slideshare.net/oemebamo/introduction-to-memcached) 230 | * [Cassandra Introduction Features](http://www.slideshare.net/planetcassandra/cassandra-introduction-features-30103666) 231 | * [Introduction to HBase](http://www.slideshare.net/alexbaranau/intro-to-hbase) 232 | * [Introduction to MongoDB](http://www.slideshare.net/mdirolf/introduction-to-mongodb) 233 | * [Introduction to Redis](http://www.slideshare.net/dvirsky/introduction-to-redis) 234 | * [Storm](http://www.slideshare.net/previa/storm-16094009) 235 | * [Introduction to Zookeeper](http://www.slideshare.net/sauravhaloi/introduction-to-apache-zookeeper) 236 | * [Kafka](http://www.slideshare.net/mumrah/kafka-talk-tri-hug) 237 | * [YouTube Architecture](http://highscalability.com/youtube-architecture) 238 | * [Scaling Pinterest](http://highscalability.com/blog/2013/4/15/scaling-pinterest-from-0-to-10s-of-billions-of-page-views-a.html) 239 | * [Google Architecture](http://highscalability.com/google-architecture) 240 | * [Scaling Twitter](http://highscalability.com/scaling-twitter-making-twitter-10000-percent-faster) 241 | * [The WhatsApp Architecture](http://highscalability.com/blog/2014/2/26/the-whatsapp-architecture-facebook-bought-for-19-billion.html) 242 | * [Flickr Architecture](http://highscalability.com/flickr-architecture) 243 | * [Amazon Architecture](http://highscalability.com/amazon-architecture) 244 | * [Stack Overflow Architecture](http://highscalability.com/blog/2009/8/5/stack-overflow-architecture.html) 245 | * [Pinterest Architecture](http://highscalability.com/blog/2012/5/21/pinterest-architecture-update-18-million-visitors-10x-growth.html) 246 | * [Tumblr Architecture](http://highscalability.com/blog/2012/2/13/tumblr-architecture-15-billion-page-views-a-month-and-harder.html) 247 | * [Instagram Architecture](http://highscalability.com/blog/2011/12/6/instagram-architecture-14-million-users-terabytes-of-photos.html) 248 | * [TripAdvisor Architecture](http://highscalability.com/blog/2011/6/27/tripadvisor-architecture-40m-visitors-200m-dynamic-page-view.html) 249 | * [Scaling Mailbox](http://highscalability.com/blog/2013/6/18/scaling-mailbox-from-0-to-one-million-users-in-6-weeks-and-1.html) 250 | * [Salesforce Architecture ](http://highscalability.com/blog/2013/9/23/salesforce-architecture-how-they-handle-13-billion-transacti.html) 251 | * [ESPN Architecture](http://highscalability.com/blog/2013/11/4/espns-architecture-at-scale-operating-at-100000-duh-nuh-nuhs.html) 252 | * [Uber Architecture](http://highscalability.com/blog/2015/9/14/how-uber-scales-their-real-time-market-platform.html) 253 | * [DropBox Design](https://www.youtube.com/watch?v=PE4gwstWhmc) 254 | * [Splunk Architecture](http://www.splunk.com/view/SP-CAAABF9) 255 | * [Good Parts of AWS](https://www.educative.io/courses/good-parts-of-aws?aid=5082902844932096) 256 | * [Azure DataCenter Architecture](https://youtu.be/69PrhWQorEM) 257 | * [Evolution Of Search Engines Architecture - Highscalability](http://highscalability.com/blog/2021/8/2/evolution-of-search-engines-architecture-algolia-new-search.html) 258 | 259 | ## Trends 260 | 261 | - [Emerging Trends in Software Architecture](https://www.oreilly.com/library/view/software-architecture-a/9788131707494/ch07.html) 262 | - [Software Architecture and Design InfoQ Trends Report—April 2020](https://www.infoq.com/articles/architecture-trends-2020/) 263 | 264 | ### [[⬆]](#toc) Hot Questions and Reference: 265 | 266 | There are some good references for each question. The references here are slides and articles. 267 | 268 | **Design a CDN network** 269 | Reference: 270 | * [Globally Distributed Content Delivery](http://repository.cmu.edu/cgi/viewcontent.cgi?article=2112&context=compsci) 271 | 272 | **Design a Google document system** 273 | Reference: 274 | * [google-mobwrite](https://code.google.com/p/google-mobwrite/) 275 | * [Differential Synchronization](https://neil.fraser.name/writing/sync/) 276 | 277 | **Design a random ID generation system** 278 | Reference: 279 | * [Announcing Snowflake](https://blog.twitter.com/2010/announcing-snowflake) 280 | * [snowflake](https://github.com/twitter/snowflake/) 281 | 282 | **Design a key-value database** 283 | Reference: 284 | * [Introduction to Redis](http://www.slideshare.net/dvirsky/introduction-to-redis) 285 | * [Introduction to Memcached](https://medium.com/swlh/what-is-memcached-d1498623db3b) 286 | 287 | **Design the Facebook news feed function** 288 | Reference: 289 | * [Deisgn a News Feed System](https://medium.com/@bansal_ankur/design-a-news-feed-system-6bf42e9f03fb) 290 | * [What are best practices for building something like a News Feed?](http://www.quora.com/What-are-best-practices-for-building-something-like-a-News-Feed) 291 | * [What are the scaling issues to keep in mind while developing a social network feed?](http://www.quora.com/Activity-Streams/What-are-the-scaling-issues-to-keep-in-mind-while-developing-a-social-network-feed) 292 | * [Activity Feeds Architecture](http://www.slideshare.net/danmckinley/etsy-activity-feeds-architecture) 293 | 294 | **Design the Facebook timeline function** 295 | Reference: 296 | * [Building Timeline](https://www.facebook.com/note.php?note_id=10150468255628920) 297 | * [Facebook Timeline](http://highscalability.com/blog/2012/1/23/facebook-timeline-brought-to-you-by-the-power-of-denormaliza.html) 298 | * [Facebook System Design](https://www.codekarle.com/system-design/facebook-system-design.html) 299 | 300 | **Design a function to return the top k requests during past time interval** 301 | Reference: 302 | * [Efficient Computation of Frequent and Top-k Elements in Data Streams](http://www.cse.ust.hk/~raywong/comp5331/References/EfficientComputationOfFrequentAndTop-kElementsInDataStreams.pdf) 303 | * [An Optimal Strategy for Monitoring Top-k Queries in Streaming Windows](http://davis.wpi.edu/xmdv/docs/EDBT11-diyang.pdf) 304 | 305 | **Design an online multiplayer card game** 306 | Reference: 307 | * [How to Create an Asynchronous Multiplayer Game](http://www.indieflashblog.com/how-to-create-an-asynchronous-multiplayer-game.html) 308 | * [How to Create an Asynchronous Multiplayer Game Part 2: Saving the Game State to Online Database](http://www.indieflashblog.com/how-to-create-async-part2.html) 309 | * [How to Create an Asynchronous Multiplayer Game Part 3: Loading Games from the Database](http://www.indieflashblog.com/how-to-create-async-part3.html) 310 | * [How to Create an Asynchronous Multiplayer Game Part 4: Matchmaking](http://www.indieflashblog.com/how-to-create-async-part4-html.html#comment-4447) 311 | * [Real Time Multiplayer in HTML5](http://buildnewgames.com/real-time-multiplayer/) 312 | 313 | **Design a graph search function** 314 | Reference: 315 | * [Building out the infrastructure for Graph Search](https://www.facebook.com/notes/facebook-engineering/under-the-hood-building-out-the-infrastructure-for-graph-search/10151347573598920) 316 | * [Indexing and ranking in Graph Search](https://www.facebook.com/notes/facebook-engineering/under-the-hood-indexing-and-ranking-in-graph-search/10151361720763920) 317 | * [The natural language interface of Graph Search](https://www.facebook.com/notes/facebook-engineering/under-the-hood-the-natural-language-interface-of-graph-search/10151432733048920) and [Erlang at Facebook](http://www.erlang-factory.com/upload/presentations/31/EugeneLetuchy-ErlangatFacebook.pdf) 318 | 319 | **Design a picture sharing system** 320 | Reference: 321 | * [Flickr Architecture](http://highscalability.com/flickr-architecture) 322 | * [Instagram Architecture](http://highscalability.com/blog/2011/12/6/instagram-architecture-14-million-users-terabytes-of-photos.html) 323 | 324 | **Design a search engine** 325 | Reference: 326 | * [How would you implement Google Search?](http://programmers.stackexchange.com/questions/38324/interview-question-how-would-you-implement-google-search) 327 | * [Implementing Search Engines](http://www.ardendertat.com/2012/01/11/implementing-search-engines/) 328 | 329 | **Design a recommendation system** 330 | Reference: 331 | * [Hulu’s Recommendation System](http://tech.hulu.com/blog/2011/09/19/recommendation-system.html) 332 | * [Recommender Systems](http://ijcai13.org/files/tutorial_slides/td3.pdf) 333 | 334 | **Design a tinyurl system** 335 | Reference: 336 | * [System Design for Big Data-tinyurl](http://n00tc0d3r.blogspot.com/) 337 | * [URL Shortener API](https://developers.google.com/url-shortener/?csw=1) 338 | * [Tiny URL System Design](https://www.youtube.com/watch?v=AVztRY77xxA) 339 | 340 | **Design a garbage collection system** 341 | Reference: 342 | * [Baby's First Garbage Collector](http://journal.stuffwithstuff.com/2013/12/08/babys-first-garbage-collector/) 343 | 344 | **Design a scalable web crawling system** 345 | Reference: 346 | * [How can I build a web crawler from scratch?](https://www.quora.com/How-can-I-build-a-web-crawler-from-scratch) 347 | 348 | **Design the Facebook chat function** 349 | Reference: 350 | * [Erlang at Facebook](http://www.erlang-factory.com/upload/presentations/31/EugeneLetuchy-ErlangatFacebook.pdf) 351 | * [Facebook Chat](https://www.facebook.com/note.php?note_id=14218138919&id=9445547199&index=0) 352 | * [Facebook Messenger/Whatsapp System Design](https://www.youtube.com/watch?v=RjQjbJ2UJDg) 353 | 354 | **Design a micro blogging site** 355 | Reference: 356 | * [Twitter System Design](https://www.youtube.com/watch?v=EkudBdvbDhs) 357 | 358 | 359 | **Design hotel booking platform** 360 | Reference: 361 | * [AirBNB/Booking.com System Design](https://www.youtube.com/watch?v=YyOXt2MEkv4) 362 | 363 | **Design a trending topic system** 364 | Reference: 365 | * [Implementing Real-Time Trending Topics With a Distributed Rolling Count Algorithm in Storm](http://www.michael-noll.com/blog/2013/01/18/implementing-real-time-trending-topics-in-storm/) 366 | * [Early detection of Twitter trends explained](http://snikolov.wordpress.com/2012/11/14/early-detection-of-twitter-trends/) 367 | 368 | **Design a cache system** 369 | Reference: 370 | * [Introduction to Memcached](http://www.slideshare.net/oemebamo/introduction-to-memcached) 371 | 372 | **Design LeetCode** 373 | - [Youtube Link-1 : Gaurav Sen](https://www.youtube.com/watch?v=eg0nlYcbLpo) 374 | - [Youtube Link-2](https://www.youtube.com/watch?v=cMH2aa0xNYQ) 375 | 376 | **Design a Payment System** 377 | * [Digital Wallet Design](https://techwithkp.com/digital-wallet-design-machine-coding-round-solution/) 378 | 379 | 380 | 381 | **Basic SRE** 382 | Reference: 383 | * [How Google Runs Production Systems?](https://landing.google.com/sre/) 384 | 385 | **Design a React Native Application** 386 | Reference : 387 | * [Facebook F8 App](https://makeitopen.com/) 388 | 389 | **Numbers from concerte implementations** 390 | References : 391 | * [DB Comparisions](http://highscalability.com/blog/2021/2/17/benchmark-ycsb-numbers-for-redis-mongodb-couchbase2-yugabyte.html) 392 | 393 | ### [[⬆]](#toc) Good Books: 394 | 395 | * [Big Data: Principles and best practices of scalable realtime data systems](http://www.amazon.com/Big-Data-Principles-practices-scalable/dp/1617290343) 396 | * [Real-Time Analytics: Techniques to Analyze and Visualize Streaming Data](http://www.amazon.com/Real-Time-Analytics-Techniques-Visualize-Streaming/dp/1118837916) 397 | * [Building Microservices: Designing Fine-Grained Systems](http://www.amazon.com/Building-Microservices-Sam-Newman/dp/1491950358) 398 | * [Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems](https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321) 399 | * [Site Reliability Engineering - How Google Runs Production Systems (English, Paperback, Beyer Betsy)](https://www.amazon.in/Site-Reliability-Engineering-Betsy-Beyer/dp/149192912X) 400 | 401 | ### [[⬆]](#toc) Object Oriented Design: 402 | 403 | #### Tips for OOD Interview 404 | 405 | **Clarify the scenario, write out user cases** 406 | 407 | Use case is a description of sequences of events that, taken together, lead to a system doing something useful. Who is going to use it and how they are going to use it. The system may be very simple or very complicated. 408 | 409 | Special system requirements such as multi-threading, read or write oriented. 410 | 411 | **Define objects** 412 | 413 | Map identity to class: one scenario for one class, each core object in this scenario for one class. 414 | 415 | Consider the relationships among classes: certain class must have unique instance, one object has many other objects (composition), one object is another object (inheritance). 416 | 417 | Identify attributes for each class: change noun to variable and action to methods. 418 | 419 | Use design patterns such that it can be reused in multiple applications. 420 | 421 | #### Useful Websites 422 | 423 | * [101 Design Patterns & Tips for Developers](http://sourcemaking.com/design-patterns-and-tips) 424 | * [A Solid Guide to SOLID Principles](https://www.baeldung.com/solid-principles) 425 | * [SOLID Design Principles Explained](https://stackify.com/solid-design-principles/) 426 | * [SOLID Principles made easy](https://hackernoon.com/solid-principles-made-easy-67b1246bcdf) 427 | * [Becoming a better developer by using the SOLID design principles by Katerina Trajchevska](https://www.youtube.com/watch?v=rtmFCcjEgEw) 428 | * [Common System Design Interview Questions](https://www.codekarle.com/) 429 | * [Common Machine Coding Interview Questions](http://lldcoding.com) 430 | 431 | ### [[⬆]](#toc) Distributed System Design : 432 | 433 | #### Distributed System Design 434 | 435 | * [Basics of Lamport Clocks](https://medium.com/@balrajasubbiah/lamport-clocks-and-vector-clocks-b713db1890d7) 436 | * [Distributed Consensus : RAFT](http://thesecretlivesofdata.com/raft/) 437 | * [Distributed Consensus : PAXOS](https://medium.com/@logeshrajendran/paxos-a9d76ebf04f3) 438 | * [Two Generals Problem](https://www.youtube.com/watch?v=IP-rGJKSZ3s) 439 | 440 | ### [[⬆]](#toc) Projects to try : 441 | 442 | * [Projects to try](https://web.eecs.utk.edu/~azh/blog/morechallengingprojects.html) 443 | 444 | #### Misc 445 | 446 | * [Scale like a Pro](https://medium.com/swlh/how-i-scaled-a-software-systems-performance-by-35-000-6dacd63732df) 447 | * [GoLang to Node.Js](https://medium.com/thecobbles/why-we-moved-from-golang-to-nodejs-cecf66a47740) 448 | * [Documenting Software Architecture Decisions](https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions) 449 | * [Choosing the correct storage solutions](https://www.codekarle.com/system-design/Database-system-design.html) 450 | 451 | #### More Info 452 | 453 | Feel free to contact [Sumit Lahiri](mailto:lahiri.devs@gmail.com) 454 | -------------------------------------------------------------------------------- /Scalability/README.md: -------------------------------------------------------------------------------- 1 | # Scalability, Auth, Patterns, Basics 2 | 3 | - [Scalable Design Patterns](http://horicky.blogspot.com/2010/10/scalable-system-design-patterns.html) 4 | - [https://www.infoq.com/news/2009/05/8-Best-Practices-Scalability/](https://www.infoq.com/news/2009/05/8-Best-Practices-Scalability/) 5 | - [SE Daily - Architecting for Scale with Lee Atchison](https://softwareengineeringdaily.com/2022/02/12/architecting-for-scale-with-lee/) 6 | - [https://www.infoq.com/articles/ebay-scalability-best-practices/](https://www.infoq.com/articles/ebay-scalability-best-practices/) 7 | - [13 Scalability Best Practices](http://highscalability.com/blog/2009/8/11/13-scalability-best-practices.html) 8 | - [How to Improve Your OAuth Developer Experience](https://thenewstack.io/how-to-improve-your-oauth-developer-experience/) 9 | - [Upgrading the rocket in the air – CTO Decisions with Cos Nicolaescu](https://softwareengineeringdaily.com/2022/06/09/cto-decisions-with-cos-nicolaescu/) 10 | - [https://www.keycdn.com/blog/scalability-testing](https://www.keycdn.com/blog/scalability-testing) 11 | - [Node.js App with Auto-scalling](https://node.university/blog/10954/aws-autoscaling) 12 | - [Why Are Facebook, Digg, And Twitter So Hard To Scale?](http://highscalability.com/blog/2009/10/13/why-are-facebook-digg-and-twitter-so-hard-to-scale.html) 13 | - [AWS : **Architecting for Reliable Scalability**](https://aws.amazon.com/blogs/architecture/architecting-for-reliable-scalability/) 14 | - [Paritioning Data Streams : **Article Highlight**](https://gojko.net/2008/03/03/two-data-streams-for-a-happy-website/) 15 | - [**Scalability!**: But at what **COST?**](https://www.usenix.org/system/files/conference/hotos15/hotos15-paper-mcsherry.pdf) 16 | - [**The Future of Microservices?** More Abstractions](https://thenewstack.io/the-future-of-microservices-more-abstractions) 17 | - [Caching Works!](https://www.youtube.com/watch?v=ASP7O5fDpSg) 18 | - [8 steps to build a scalable and distributed system design for web applications](https://www.linkedin.com/pulse/8-steps-build-scalable-distributed-system-design-web-yamit-mehta) 19 | - [The Scoop #33: Will Google start to pay less, over time?](https://newsletter.pragmaticengineer.com/p/the-scoop-33) 20 | - ["Functional distributed systems beyond request/response" by Melinda Lu](https://www.youtube.com/watch?v=VWrpnT8rwVY) 21 | - [BBC Online: Architecting for Scale with the Cloud and Serverless](https://www.youtube.com/watch?v=WE-tkz2tf30) 22 | - [Microservices Database Management](https://relevant.software/blog/microservices-database-management/) 23 | - [Ad-free Search on Neeva with Darin Fisher](https://softwareengineeringdaily.com/2022/01/25/neeva-with-darin/) 24 | - [Google Cloud : Design for scale and high availability](https://cloud.google.com/architecture/framework/reliability/design-scale-high-availability) 25 | - [Google Cloud Architecture Framework: System design](https://cloud.google.com/architecture/framework/system-design) 26 | - [Refactoring and Optimizing a High Traffic API at PayPal](https://medium.com/paypal-tech/refactoring-and-optimizing-a-high-traffic-api-at-paypal-eb11c373d795) 27 | - [A Recipe to Migrate and Scale Monoliths in the Cloud](https://www.infoq.com/articles/cloud-migrate-scale/?topicPageSponsorship=2db34777-a828-4199-8777-865da05e8838&itm_source=articles_about_architecture-design&itm_medium=link&itm_campaign=architecture-design) 28 | - [Building Large-Scale Real-Time JSON Applications](https://thenewstack.io/building-large-scale-real-time-json-applications/) 29 | -------------------------------------------------------------------------------- /Secure Design/README.md: -------------------------------------------------------------------------------- 1 | - [5 Golden Rules for Great Web API Design](https://www.toptal.com/api-developers/5-golden-rules-for-designing-a-great-web-api) 2 | - [How to design a secure web API access for your website?](https://blog.bytebytego.com/p/how-to-design-a-secture-web-api-access) 3 | - [Securing APIs: 10 Best Practices for Keeping Your Data and Infrastructure Safe](https://www.f5.com/labs/learning-center/securing-apis-10-best-practices-for-keeping-your-data-and-infrastructure-safe) 4 | - [API security: 12 essential best practices](https://blog.axway.com/learning-center/digital-security/keys-oauth/api-security-best-practices) 5 | -------------------------------------------------------------------------------- /Serverless Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Serverless Architechture 2 | 3 | - [Design Patterns for Serverless Systems](https://www.infoq.com/articles/design-patterns-for-serverless-systems/?itm_campaign=rightbar_v2&itm_source=infoq&itm_medium=articles_link&itm_content=link_text) 4 | - [Serverless is really complex. Or is it?](http://highscalability.com/blog/2020/7/31/stuff-the-internet-says-on-scalability-for-july-31st-2020.html) 5 | - [https://github.com/serverless/examples](https://github.com/serverless/examples) 6 | - [Building a Serverless URL Shortener](https://www.freecodecamp.org/news/how-to-build-a-serverless-url-shortener-using-aws-lambda-and-s3-4fbdf70cbf5c/) 7 | - [Building a Serverless MEME Generator](https://www.alibabacloud.com/blog/fun-with-functions-building-a-serverless-meme-generator-with-function-compute_596421) 8 | - [Intro : Google Cloud Funtions](https://www.serverless.com/framework/docs/providers/google/examples/) 9 | - [Khan Academy : Serverless](https://www.nextplatform.com/2021/05/12/serverless-veteran-khan-academy-on-pros-cons/) 10 | - [Example : Serverless App](https://www.infoq.com/news/2021/02/serverless-react-apps-aws-lambda/) 11 | - [Serverless Functions for Microservices?](https://www.infoq.com/articles/serverless-microservices-flexibility/) 12 | - [Implementation : Flask, Serverless, Lambda, ... AWS](https://www.serverless.com/blog/flask-python-rest-api-serverless-lambda-dynamodb) 13 | - [Databases in the Microservices World](https://www.youtube.com/watch?v=-9Veoch50Bg) 14 | - [BBC Online: Architecting for Scale with the Cloud and Serverless](https://www.youtube.com/watch?v=WE-tkz2tf30) 15 | -------------------------------------------------------------------------------- /Slack Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Slack Engineering 2 | 3 | - [Scaling Slack - The Good, the Unexpected, and the Road Ahead](https://www.youtube.com/watch?v=_M-oHxknfnI) 4 | - [How Slack Works](https://www.youtube.com/watch?v=WE9c9AZe-DY) 5 | - [Scaling Slack - GOTO](https://www.youtube.com/watch?v=o4f5G9q_9O4) 6 | - [Old Slack Tutorial Video : **Discover Slack**](https://www.youtube.com/watch?v=0GTIbXHdtj4) 7 | - [How We Design Our APIs at Slack?](https://slack.engineering/how-we-design-our-apis-at-slack/) 8 | - [Slack Security : How Two Interns Are Helping Secure Millions of Lines of Code](https://slack.engineering/how-two-interns-are-helping-secure-millions-of-lines-of-code/) 9 | - [Slack Frontend Architecture with Anuj Nair](https://softwareengineeringdaily.com/2020/02/27/slack-frontend-architecture-with-anuj-nair/#:~:text=Slack%20is%20a%20messaging%20application,and%20reliable%2C%20despite%20its%20complexity.) 10 | - [The Case of the Recursive Resolvers](https://slack.engineering/what-happened-during-slacks-dnssec-rollout/) 11 | - [Slack 22.2.22 Outage Explained!](https://www.youtube.com/watch?v=8pWA7jsdha8) 12 | - [Reducing Slack’s memory footprint](https://slack.engineering/reducing-slacks-memory-footprint/) 13 | - [Beyond the last message: Designing for all information in Slack ](https://slack.design/articles/beyond-the-last-message-designing-for-all-information-in-slack/) 14 | - [How We Design Our APIs at Slack](https://slack.engineering/how-we-design-our-apis-at-slack/) 15 | - [Remote Development at Slack](https://slack.engineering/remote-development-at-slack/) 16 | - [A Day in the Life of a Backend Product Engineer at Slack*](https://medium.com/several-people-are-coding/a-day-in-the-life-of-a-backend-product-engineer-at-slack-e786a8a08fc4) 17 | - [Building the Next Evolution of Cloud Networks at Slack – A Retrospective](https://slack.engineering/building-the-next-evolution-of-cloud-networks-at-slack-a-retrospective/) 18 | -------------------------------------------------------------------------------- /Snapdeal Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Snapdeal Engineering 2 | 3 | - [Rapid Product Experimenting at Scale: The Tech Underneath Snapdeal](https://culture.kissflow.com/rapid-product-experimenting-at-scale-the-tech-underneath-snapdeal-d623c5a58029) 4 | -------------------------------------------------------------------------------- /Software Architecture Patterns/README.md: -------------------------------------------------------------------------------- 1 | ## System Design Patterns (What and What not?) 2 | 3 | - [Modern-Day Architecture Design Patterns for Software Professionals](https://medium.com/better-programming/modern-day-architecture-design-patterns-for-software-professionals-9056ee1ed977) 4 | - [Microservices + Events + Docker = A Perfect Trio](https://www.youtube.com/watch?v=sSm2dRarhPo) 5 | - [Software Design Pattern is different from system design patterns](https://en.wikipedia.org/wiki/Software_design_pattern) 6 | - [Saga Pattern : Microservices](https://microservices.io/patterns/data/saga.html) 7 | - [CQRS Pattern : Microservices](https://docs.microsoft.com/en-us/azure/architecture/patterns/cqrs) 8 | - [Pitfalls and Patterns in Microservice Dependency Management](https://www.infoq.com/articles/pitfalls-patterns-microservice-dependency-management/) 9 | - [Patterns of Distributed Systems](https://martinfowler.com/articles/patterns-of-distributed-systems/) 10 | - [High-Water Mark](https://martinfowler.com/articles/patterns-of-distributed-systems/high-watermark.html) 11 | - [Idempotent Receiver](https://martinfowler.com/articles/patterns-of-distributed-systems/idempotent-receiver.html) 12 | - [Low-Water Mark](https://martinfowler.com/articles/patterns-of-distributed-systems/low-watermark.html) 13 | - [Request Pipeline](https://martinfowler.com/articles/patterns-of-distributed-systems/request-pipeline.html) 14 | - [Version Vector](https://martinfowler.com/articles/patterns-of-distributed-systems/version-vector.html) 15 | - [Singular Update Queue](https://martinfowler.com/articles/patterns-of-distributed-systems/singular-update-queue.html) 16 | - [Write-Ahead Log](https://martinfowler.com/articles/patterns-of-distributed-systems/wal.html) 17 | - [Event Sourcing](https://www.youtube.com/watch?v=rUDN40rdly8) 18 | - [Avoiding Coordination Cost: Three Patterns for Building Efficient Distributed Systems](https://blog.techlanika.com/avoiding-coordination-cost-three-patterns-for-building-efficient-distributed-systems-b8aff9314e88) 19 | 20 | ## More Articles 21 | 22 | - [ODD : https://www.oodesign.com/](https://www.oodesign.com/) 23 | - [Tapad Engineering : Scale-Three principle](http://highscalability.com/blog/2015/5/11/designing-for-scale-three-principles-and-three-practices-fro.html) 24 | - [Patterns : Thinking About Microservices](https://www.infoq.com/articles/microservices-design-ideals/?itm_source=infoq&itm_medium=popular_widget&itm_campaign=popular_content_list&itm_content=) 25 | - [Observer Design Pattern](https://medium.com/better-programming/understanding-the-observer-design-pattern-f621b1d0b6c9) 26 | - [A quick look on scalable architectures](https://dzone.com/articles/scalable-system-design) 27 | - [The Future of Microservices? More Abstractions](https://thenewstack.io/the-future-of-microservices-more-abstractions/) 28 | - [What is a quorum?](https://martinfowler.com/articles/patterns-of-distributed-systems/quorum.html) 29 | - [[BUILD] BFF Pattern with Go Microservices using REST & gRPC.](https://itnext.io/bff-pattern-with-go-microservices-using-rest-grpc-87d269bc2434) 30 | - [TDD & Clean Code Practices](https://www.youtube.com/watch?v=IZWLnn2fNko) 31 | - [https://medium.com/codex/the-fifo-fallacy-of-event-driven-architecture-8742477fefd0](The FIFO fallacy of event-driven architecture) 32 | -------------------------------------------------------------------------------- /Spotify Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Spotify 2 | 3 | - [Backend infrastructure at Spotify](https://engineering.atspotify.com/2013/03/backend-infrastructure-at-spotify/) 4 | - [Personalization at Spotify using Cassandra](https://engineering.atspotify.com/2015/01/personalization-at-spotify-using-cassandra/) 5 | - [Engineering Culture @Spotify](https://www.youtube.com/watch?v=b8PHi1D193k) 6 | -------------------------------------------------------------------------------- /Swiggy Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Swiggy Engineering 2 | 3 | - [A brief introduction to Engineering challenges at Swiggy](https://bytes.swiggy.com/engineering-challenges-at-swiggy-430dea6c86a3) 4 | - [Service Level Testing for Microservices in Swiggy](https://bytes.swiggy.com/service-level-testing-for-microservices-in-swiggy-62b6b3f865f4) 5 | - [Fan(s)tastic: Search for blazing-fast results](https://bytes.swiggy.com/fan-s-tastic-search-for-blazing-fast-results-46aa706313ef) 6 | - [Swiggy-Rest — Opinionated CRUD Library On Spring](https://bytes.swiggy.com/swiggy-rest-opinionated-crud-library-on-spring-a78715074eb4) 7 | - [The Swiggy Delivery Challenge (Part One)](https://bytes.swiggy.com/the-swiggy-delivery-challenge-part-one-6a2abb4f82f6) 8 | - [Designing the Serviceability Platform at Swiggy for High Scale](https://bytes.swiggy.com/designing-the-serviceability-platform-at-swiggy-for-high-scale-part-2-ab20365fbc23) 9 | - [Designing Resilient Microservices — Part 1](https://bytes.swiggy.com/designing-resilient-microservices-part-1-6a72fe964759) 10 | - [Designing Resilient Microservices — Part 2](https://bytes.swiggy.com/designing-resilient-microservices-part-2-14f8b564f622) 11 | - [Segmentation at Swiggy](https://bytes.swiggy.com/segmentation-at-swiggy-part-1-d9566ab1a442) 12 | - [Segmentation at Swiggy — Part 3](https://bytes.swiggy.com/segmentation-at-swiggy-part-3-final-part-b740f7a3697d) 13 | - [Address Location Correction System for Q-commerce](https://bytes.swiggy.com/address-location-correction-system-for-q-commerce-57c82ef291d7) 14 | -------------------------------------------------------------------------------- /System Design Basics/README.md: -------------------------------------------------------------------------------- 1 | # System-Design 2 | 3 | * [Scaling with common sense #2: Being future ready.](https://zerodha.tech/blog/being-future-ready-with-common-sense/) 4 | * [The cost of Hash Tables | The Backend Engineering Show](https://www.youtube.com/watch?v=hxdT_QgHUSg) 5 | * [What Software Architecture Should Look Like • Dave Farley • GOTO 2022](https://www.youtube.com/watch?v=Eg_dapdKCHU) 6 | * [Concurrency vs. Parallelism — A brief view](https://medium.com/@itIsMadhavan/concurrency-vs-parallelism-a-brief-review-b337c8dac350) 7 | * [Designing Tinder](http://highscalability.com/blog/2022/1/17/designing-tinder.html) 8 | * [Designing Microservices the right way](https://www.youtube.com/watch?v=j6ow-UemzBc) 9 | * [Microservice Architecture @Uber](https://eng.uber.com/microservice-architecture/) 10 | * [Clean Software Architecture](https://herbertograca.com/tag/software-architecture/) 11 | * [Software Architecture Chronicles](https://herbertograca.com/2017/07/03/the-software-architecture-chronicles/) 12 | * [Domain-Driven Design with Onion Architecture](https://www.infoq.com/news/2014/10/ddd-onion-architecture/?itm_source=presentations_about_DesignPattern&itm_medium=link&itm_campaign=DesignPattern) 13 | * [Exploring the Hexagonal Architecture](https://www.infoq.com/news/2014/10/exploring-hexagonal-architecture/?itm_source=presentations_about_DesignPattern&itm_medium=link&itm_campaign=DesignPattern) 14 | * [E-Commerce/food delivery app (Zomato/Swiggy/1mg)](https://medium.com/@ravindersengar/end-to-end-design-of-a-food-delivery-app-like-zomato-or-swiggy-52b96f3a635f) 15 | * [The Best Way to Think about Resilience Is Not to](https://thenewstack.io/the-best-way-to-think-about-resilience-is-not-to/) 16 | * [DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together](https://herbertograca.com/2017/11/16/explicit-architecture-01-ddd-hexagonal-onion-clean-cqrs-how-i-put-it-all-together/) 17 | * [DDD + Golang](https://towardsdatascience.com/how-to-implement-domain-driven-design-ddd-in-golang-2e2139beb09d) 18 | * [Quick & Brief Overview of the basics](https://www.cronj.com/blog/system-designing-basics/) 19 | * [Backend Development Topic](https://copyconstruct.medium.com/nonblocking-i-o-99948ad7c957) 20 | * [Load Balancing](https://www.educative.io/courses/grokking-the-system-design-interview/3jEwl04BL7Q) 21 | * [Designing a URL Shortening service like TinyURL](https://www.educative.io/courses/grokking-the-system-design-interview/m2ygV4E81AR) 22 | * [When is a API not RESTFUL?](https://www.infoq.com/articles/web-api-rest/) 23 | * [Go Use Cases : With scalability in Mind](https://opensource.googleblog.com/2020/08/new-case-studies-about-googles-use-of-go.html) 24 | * [On Engineering Dependibility](http://highscalability.com/blog/2021/2/19/engineering-dependability-and-fault-tolerance-in-a-distribut.html) 25 | * [More on System Design Basics](https://medium.com/system-design-blog) 26 | * [API Gateway Pattern](https://microservices.io/patterns/apigateway.html) 27 | * [8 steps to build a scalable and distributed system design for web applications](https://www.linkedin.com/pulse/8-steps-build-scalable-distributed-system-design-web-yamit-mehta) 28 | * [Building robust distributed systems](https://kislayverma.com/software-architecture/building-robust-distributed-systems/) 29 | * [Architecting Backend For A Social Product](http://highscalability.com/blog/2015/7/22/architecting-backend-for-a-social-product.html) 30 | * [http://highscalability.com/plentyoffish-architecture](http://highscalability.com/plentyoffish-architecture) 31 | * [Trouble with Timestamps](https://aphyr.com/posts/299-the-trouble-with-timestamps) 32 | * [All Things Clock, Time and Order in Distributed Systems: Logical Clock vs Google True Time](https://medium.com/geekculture/all-things-clock-time-and-order-in-distributed-systems-logical-clock-vs-google-true-time-dba552f2d842) 33 | * [CD/CI for ML Models at Uber](https://eng.uber.com/continuous-integration-deployment-ml/) 34 | * [Redis as a Cache : But Why?](https://redislabs.com/wp-content/uploads/2016/03/15-Reasons-Caching-is-best-with-Redis-RedisLabs-1.pdf) 35 | * [7 Microservices Best Practices for Developers](https://dzone.com/articles/7-microservices-best-practices-for-developers) 36 | * [Pitfalls and Patterns in Microservice Dependency Management](https://www.youtube.com/watch?v=kjbfvP65Jn0) 37 | * [Language Choice Matters : Why We Switched from Python to Go](https://softwareengineeringdaily.com/2021/03/03/why-we-switched-from-python-to-go/) 38 | * [Pieces of a Scalable iOS App Architecture](https://betterprogramming.pub/pieces-of-a-scalable-ios-app-architecture-7c182f9dcd2c) 39 | * [Robustness in Complex Systems](https://www.gribble.org/papers/robust.pdf) 40 | * [Out of the tar pit](https://github.com/papers-we-love/papers-we-love/blob/master/design/out-of-the-tar-pit.pdf) 41 | * [Create Distributed, Scalable, Durable, and Highly Available Software— With Cadence](https://betterprogramming.pub/create-distributed-scalable-durable-and-highly-available-software-with-cadence-9f4fa6b1376b?gi=f8dcb5bb93b1) 42 | * [Proxy vs Reverse Proxy (Real-world Examples)](https://www.youtube.com/watch?v=4NB0NDtOwIQ) 43 | 44 | ## Machine Coding Basics 45 | * [Machine Coding Explained With Examples](https://techwithkp.com/machine-coding-round-what-is-it-how-to-crack-it/) 46 | 47 | ### Software & API Design Bytes : 48 | 49 | These are also necessary since they give a fair idea as to organize code that is used to build and maintain components. I have covered this in great length in other links and repos of mine. 50 | 51 | - [Best Book Ever : GoF](https://www.oreilly.com/library/view/design-patterns-elements/0201633612/) 52 | - [4 Design Patterns You Should Know for Web Development](https://www.freecodecamp.org/news/4-design-patterns-to-use-in-web-development/) 53 | - [Traversy Media -- 5 Design Patterns Every Engineer Should Know](https://www.youtube.com/watch?v=FLmBqI3IKMA) 54 | - [Introduction to Creational Design](https://www.baeldung.com/creational-design-patterns) 55 | - [API Design-First Using the "Align-Define-Design-Refine" Process](https://www.infoq.com/news/2021/09/api-design-first-addr/?itm_source=infoq&itm_campaign=footer_links&itm_medium=footer_links_category_page_by_content_type) 56 | - [Adopting an API Design-First Approach](https://kalele.io/adopting-an-api-design-first-approach/) 57 | - [Components, Patterns and Sh\*t That’s Hard to Deal with](https://www.infoq.com/presentations/conde-nast-components-patterns/?topicPageSponsorship=02b1f4ac-b8f1-443d-9804-c3ee69fd77a0&itm_source=presentations_about_Design&itm_medium=link&itm_campaign=Design) 58 | -------------------------------------------------------------------------------- /Twitch Engineering/README.md: -------------------------------------------------------------------------------- 1 | ## Twitch Engineering 2 | 3 | - [Ingesting Live Video Streams at Global Scale](https://blog.twitch.tv/en/2022/04/26/ingesting-live-video-streams-at-global-scale/) 4 | - [Smarter, Better, Faster: Using Machine Learning to Review Emotes](https://blog.twitch.tv/en/2022/06/22/smarter-better-faster-using-machine-learning-to-review-emotes/) 5 | - [Twitch Engineering: An Introduction and Overview](https://blog.twitch.tv/en/2015/12/18/twitch-engineering-an-introduction-and-overview-a23917b71a25/) 6 | -------------------------------------------------------------------------------- /Twitter Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Twitter Architecture 2 | 3 | - [The Infrastructure Behind Twitter: Scale](https://blog.twitter.com/engineering/en_us/topics/infrastructure/2017/the-infrastructure-behind-twitter-scale.html) 4 | - [The Architecture Twitter Uses To Deal With 150M Active Users, 300K QPS, A 22 MB/S Firehose, And Send Tweets In Under 5 Seconds](http://highscalability.com/blog/2013/7/8/the-architecture-twitter-uses-to-deal-with-150m-active-users.html) 5 | - [Hunting a Linux kernel bug](https://blog.twitter.com/engineering/en_us/topics/open-source/2020/hunting-a-linux-kernel-bug) 6 | - [Dropping cache didn’t drop cache](https://blog.twitter.com/engineering/en_us/topics/open-source/2021/dropping-cache-didnt-drop-cache) 7 | - [Logging at Twitter: Updated](https://blog.twitter.com/engineering/en_us/topics/infrastructure/2021/logging-at-twitter-updated) 8 | - [Google Case Studies: Twitter](https://cloud.google.com/blog/products/data-analytics/modernizing-twitters-ad-engagement-analytics-platform) 9 | - [Twitter Architecture 2022 vs. 2012. What’s changed over the past 10 years?](https://twitter.com/alexxubyte/status/1594008281340530688) 10 | - [Twitter / Newsfeed System Design Interview Question](https://www.youtube.com/watch?v=gbysuvl2TZo) 11 | -------------------------------------------------------------------------------- /Uber Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Uber Engineering Blog (Links) 2 | 3 | - [Designing Uber](http://highscalability.com/blog/2022/1/25/designing-uber.html) 4 | - [Vertical CPU Scaling: Reduce Cost of Capacity and Increase Reliability](https://www.uber.com/en-IN/blog/vertical-cpu-scaling/) 5 | - [Design the Uber backend: System design walkthrough (educative)](https://www.educative.io/blog/uber-backend-system-design) 6 | - [The Uber Engineering Tech Stack, Part I: The Foundation](https://eng.uber.com/tech-stack-part-one-foundation/) 7 | - [Uber’s Fulfillment Platform: Ground-up Re-architecture to Accelerate Uber’s Go/Get Strategy](https://eng.uber.com/fulfillment-platform-rearchitecture) 8 | - [Bringing what’s new from teams across Uber to life](https://www.uber.com/en-IN/blog/bringing-whats-new-from-teams-across-uber-to-life/) 9 | - [Introducing Domain-Oriented Microservice Architecture](https://eng.uber.com/microservice-architecture/) 10 | - [Customer Support Automation Platform at Uber](https://eng.uber.com/customer-automation-platform/) 11 | - [CRISP: Critical Path Analysis for Microservice Architectures](https://eng.uber.com/crisp-critical-path-analysis-for-microservice-architectures/) 12 | - [Operating Apache Pinot @ Uber Scale](https://eng.uber.com/operating-apache-pinot/) 13 | - [‘Orders Near You’ and User-Facing Analytics on Real-Time Geospatial Data](https://eng.uber.com/orders-near-you/) 14 | - [Elastic Distributed Training with XGBoost on Ray](https://eng.uber.com/elastic-xgboost-ray) 15 | - [Why Uber Engineering Switched from Postgres to MySQL](https://eng.uber.com/postgres-to-mysql-migration/) 16 | - [Enabling Seamless Kafka Async Queuing with Consumer Proxy](https://eng.uber.com/kafka-async-queuing-with-consumer-proxy/) 17 | - [Building Reliable Reprocessing and Dead Letter Queues with Apache Kafka](https://eng.uber.com/reliable-reprocessing/) 18 | - [How Uber is Leveraging Apache Kafka For More Than 300 Micro Services](https://analyticsindiamag.com/how-uber-is-leveraging-apache-kafka-for-more-than-300-micro-services/) 19 | - [Michelangelo PyML: Introducing Uber’s Platform for Rapid Python ML Model Development](https://www.uber.com/en-IN/blog/michelangelo-pyml/) 20 | - [Supercharging A/B Testing at Uber](https://eng.uber.com/supercharging-a-b-testing-at-uber/) 21 | - [Jellyfish: Cost-Effective Data Tiering for Uber’s Largest Storage System](https://eng.uber.com/jellyfish-cost-effective-data-tiering/) 22 | - [YAML Generator for Funnel YAML Files: Streamlining the Mobile Data Workflow Process](https://eng.uber.com/streamlining-mobile-data-workflow-process/) 23 | - [Real-Time Exactly-Once Ad Event Processing with Apache Flink, Kafka, and Pinot](https://eng.uber.com/real-time-exactly-once-ad-event-processing/) 24 | - [Introducing AresDB: Uber’s GPU-Powered Open Source, Real-time Analytics Engine](https://eng.uber.com/aresdb/) 25 | - [Time Series Forecasting @Uber](https://www.youtube.com/watch?v=VYpAodcdFfA) 26 | - [Forecasting @UBER](https://www.youtube.com/watch?v=bn8rVBuIcFg) 27 | - [Deep and Confident Prediction for Time Series at Uber](https://arxiv.org/pdf/1709.01907.pdf) 28 | - [Building Uber’s Fulfillment Platform for Planet-Scale using Google Cloud Spanner](https://eng.uber.com/building-ubers-fulfillment-platform/) 29 | - [UBER State Machine -- Trips](https://eng.uber.com/sessionizing-data/) 30 | - [Design the Uber backend: System design walkthrough](https://www.educative.io/blog/uber-backend-system-design) 31 | - [SED : Uber State Machine with Uday Kiran Medisetty](https://softwareengineeringdaily.com/2022/01/18/uber-state-machine-with-uday-kiran-medisetty/) 32 | - [Architecting with Google Cloud](https://www.youtube.com/watch?v=DY2AR8Wzg3Y) 33 | - [DeepETA: How Uber Predicts Arrival Times Using Deep Learning](https://eng.uber.com/deepeta-how-uber-predicts-arrival-times/) 34 | - [Faster Neural Networks Straight from JPEG](https://eng.uber.com/neural-networks-jpeg/) 35 | - [Uber’s Next Gen Push Platform on gRPC](https://www.uber.com/en-IN/blog/ubers-next-gen-push-platform-on-grpc/) 36 | - [Uber Design GKCS](https://www.youtube.com/watch?v=W0KNQuMka-Q) 37 | -------------------------------------------------------------------------------- /Web-App-Engineering/README.md: -------------------------------------------------------------------------------- 1 | ## Development Related Stuff. 2 | 3 | - [SE Daily : JavaScript Supply Chain with Feross Aboukhadijeh](https://softwareengineeringdaily.com/2022/04/22/javascript-supply-chain-with-feross-aboukhadijeh/) 4 | 5 | Understand the basics of the web before diving in **System Design**. 6 | 7 | - [Micro-frontends](https://www.youtube.com/watch?v=lKKsjpH09dU) 8 | - [React Microfrontends](https://blog.bitsrc.io/how-to-develop-microfrontends-using-react-step-by-step-guide-47ebb479cacd) 9 | - [SE Daily - Micro-Frontends with Luca Mezzalira](https://softwareengineeringdaily.com/2022/02/14/micro-frontends-with-luca-mezzalira/) 10 | - [FrontEnd Stuff](https://www.youtube.com/c/JackHerrington/playlists) 11 | - [Front-End System Design Example](https://www.youtube.com/watch?v=LEaiGjffLEs) 12 | - [Microfrontend Architecture](https://www.youtube.com/watch?v=BuRB3djraeM) 13 | - [Design a Poll Widget](https://www.youtube.com/watch?v=lO6GyCvbDm8) 14 | - [Introductory - Learn HTML Free in [2022] – Basic HTML Codes for Beginners](https://www.websiteplanet.com/blog/html-guide-beginners/) 15 | - [Design Concepts for Building a Website: Main Points to Consider](https://medium.com/@upqode/design-concepts-for-building-a-website-main-points-to-consider-92ae48d6d059) 16 | - [The Perils of Rehydration](https://www.joshwcomeau.com/react/the-perils-of-rehydration/) 17 | - [How I Built The Internet's Best Performing Code Execution Engine](https://www.youtube.com/watch?v=SD4KgwdjmdI) 18 | - [Build a website with Notion in seconds, no coding required](https://www.notion.so/help/guides/build-a-website-with-notion-in-seconds-no-coding-required) 19 | - [Browser Observability With Jay Khatri](https://softwareengineeringdaily.com/2022/05/20/browser-observability-with-jay/) 20 | - [Exploring JS](https://exploringjs.com/) 21 | - [15 Open-source Tailwind-based UI Frameworks and Component Libraries](https://medevel.com/15-tailwind-libraries/) 22 | - [Prepping for 2023: What’s Ahead for Frontend Developers](https://thenewstack.io/prepping-for-2023-whats-ahead-for-frontend-developers/) 23 | 24 | ## App/Full-Stack/Backend Engineering 25 | 26 | Implementation & Project links. 27 | 28 | - [Building a React Design System](https://blog.bitsrc.io/building-a-react-component-design-system-8b643bb8922b) 29 | - [Understanding Referential Equality in React](https://blog.bitsrc.io/understanding-referential-equality-in-react-a8fb3769be0) 30 | - [React Patterns: The Container pattern](https://itnext.io/react-patterns-the-container-pattern-4d8b5b6f0127) 31 | - [A Front-End's (good) impressions about Elixir](https://medium.com/inside-sumup/a-front-ends-good-impressions-about-elixir-68f8983d8ab) 32 | - [Learn Responsive Web Design by Building 20 Projects – a Major freeCodeCamp Curriculum Update](https://www.freecodecamp.org/news/responsive-web-design-certification-redesigned/) 33 | - [React Architecture Patterns for Your Projects](https://blog.openreplay.com/react-architecture-patterns-for-your-projects) 34 | - [React Antipatterns you should know](https://yosua-halim.medium.com/react-antipatterns-you-should-know-dc2c7b7ce159) 35 | - [Architecture Of Max ReHIT Workout](http://highscalability.com/blog/2021/11/30/architecture-of-max-rehit-workout.html) 36 | - [A Product Story: Three Lessons We Learned from Developing the Mobile App](https://engineering.atspotify.com/2021/10/a-product-story-three-lessons-we-learned-from-developing-the-mobile-app/) 37 | - [Building Compound Components in React](https://medium.com/unibuddy/building-compound-components-in-react-8fbbe7565640) 38 | - [The 4 Creational Design Patterns In Node.js You Should Know](https://daily.dev/blog/the-4-creational-design-patterns-in-node-js-you-should-know) 39 | - [My Favorite Microservice Design Patterns for Node.js](https://blog.bitsrc.io/my-favorite-microservice-design-patterns-for-node-js-fe048c635d83) 40 | - [Remote Code Execution Platform](https://medium.com/@yashbudukh/building-a-remote-code-execution-system-9e55c5b248d6) 41 | - [What happens when you type a URL into your browser?](https://www.youtube.com/watch?v=AlkDbnbv7dk) 42 | - [What The Tech?! NATS and all-things Golang](https://blog.hackajob.co/nats-and-all-things-golang/) 43 | - [Cool Stuff With Go’s AST Package Pt 1](https://medium.com/swlh/cool-stuff-with-gos-ast-package-pt-1-981460cddcd7) 44 | - [How to Support a Million Users on Your Website: A Success Stor](https://thenewstack.io/how-to-support-a-million-users-on-your-website-a-success-story/) 45 | -------------------------------------------------------------------------------- /Webhook Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Webhooks 2 | 3 | * [Webhook Architecture Design](https://www.youtube.com/watch?v=4jvV75OD620) 4 | * [Webhook Architecture Diagram](https://www.svix.com/resources/webhook-architecture-diagram/) 5 | * [Webhook Security in the Real World](https://blog.ngrok.com/posts/get-webhooks-secure-it-depends-a-field-guide-to-webhook-security) 6 | * [Webhooks.fyi](https://webhooks.fyi/) -------------------------------------------------------------------------------- /Yelp Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Yelp Architecture Bytes 2 | 3 | - [Yelp Engineering: Using Services to Break Down a Monolith](https://www.infoq.com/news/2015/03/yelp-soa-break-monoliths/) 4 | - [Billions of Messages a Day - Yelp's Real-time Data Pipeline](https://engineeringblog.yelp.com/2016/07/billions-of-messages-a-day-yelps-real-time-data-pipeline.html) 5 | - [Minimizing Read-Write downtime MySQL DB-Service](https://engineeringblog.yelp.com/2020/11/minimizing-read-write-mysql-downtime.html) 6 | -------------------------------------------------------------------------------- /Youtube Architecture/README.md: -------------------------------------------------------------------------------- 1 | ## Youtube Architecture 2 | 3 | * [YT-ARCH](http://highscalability.com/youtube-architecture) 4 | * [YouTube SEO Ways](https://backlinko.com/youtube-ranking-factors) 5 | * [Scaling with Go: YouTube's Vitess](https://www.youtube.com/watch?v=midJ6b1LkA0) 6 | * [Scaling YouTube's Backend: The Vitess Trade-offs - @Scale 2014 - Data](https://www.youtube.com/watch?v=5yDO-tmIoXY) 7 | * [Scalling @youtube](https://www.youtube.com/watch?v=G-lGCC4KKok) 8 | * [Reimagining video infrastructure to empower YouTube](https://blog.youtube/inside-youtube/new-era-video-infrastructure/) 9 | * [On YouTube’s recommendation system](https://blog.youtube/inside-youtube/on-youtubes-recommendation-system/) 10 | -------------------------------------------------------------------------------- /Zomato Engineering/README.md: -------------------------------------------------------------------------------- 1 | # Zomato Engineering 2 | 3 | - [The Deep Tech Behind Estimating Food Preparation Time](https://www.zomato.com/blog/food-preparation-time) 4 | - [Predicting your order’s Food Preparation Time](https://www.zomato.com/blog/predicting-fpt-optimally) 5 | - [Powering Zomato’s data analytics using Trino](https://www.zomato.com/blog/powering-data-analytics-with-trino) 6 | - [How we use embeddings to identify and cluster unique addresses](https://www.zomato.com/blog/unique-addresses) 7 | - [Rethinking Zomato Search (Part Two)](https://www.zomato.com/blog/rethinking-zomato-search-pt-2) 8 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | remote_theme: pmarsceill/just-the-docs 2 | 3 | theme: jekyll-theme-slate -------------------------------------------------------------------------------- /system-design.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/codersguild/System-Design/59c31d7b7933478e668598ee44ec0550ca76df87/system-design.PNG --------------------------------------------------------------------------------