donnemartin

Si querés aprender arquitectura de software o preparar entrevistas Senior, este repo es clave: donnemartin/system-design-primer Trae teoría (escalabilidad, cachés, CAP) y casos reales paso a paso para diseñar apps como Twitter o Netflix a gran escala.

The best system design course is a free GitHub repo #shorts Comment SYSTEM and I'll send you the repo 👇 People pay $148 for a system design course. The System Design Primer is free, with 370K+ stars. It covers caching, load balancing, sharding and the CAP theorem, with real interview questions, full solutions and Anki flashcards. Repo: donnemartin/system-design-primer Course price: designgurus.io, checked Oct 19, 2026. Repo by Donne Martin, CC BY 4.0. Voiceover: AI clone of my own voice. #systemdesign #coding #softwareengineering #interviewprep #shorts [de-DE] Der beste System-Design-Kurs ist ein kostenloses GitHub-Repo #shorts Kommentiere mit SYSTEM und ich schicke dir das Repository 👇 Manche zahlen 148 $ für einen Systemdesign-Kurs. Der System Design Primer ist kostenlos und hat über 370.000 Sterne. Er behandelt Caching, Load Balancing, Sharding und das CAP-Theorem und enthält echte Interviewfragen, vollständige Lösungen und Anki-Karteikarten. Repository: donnemartin/system-design-primer Kurspreis: designgurus.io, geprüft am 19. Oktober 2026. Repository von Donne Martin, CC BY 4.0. Voiceover: KI-Klon meiner Stimme. #systemdesign #coding #softwareengineering #interviewprep #shorts [es-US] El mejor curso de diseño de sistemas es un repositorio gratuito de GitHub #shorts Comenta "SYSTEM" y te enviaré el repositorio 👇 Hay quienes pagan $148 por un curso de diseño de sistemas. El curso "System Design Primer" es gratuito y cuenta con más de 370.000 estrellas. Cubre temas como el almacenamiento en caché, el balanceo de carga, el particionamiento y el teorema CAP, con preguntas reales de entrevistas, soluciones completas y tarjetas Anki. Repositorio: donnemartin/system-design-primer Precio del curso: designgurus.io, consultado el 19 de octubre de 2026. Repositorio de Donne Martin, CC BY 4.0. Voz en off: Clon de IA de mi propia voz. #diseñodesistemas #programación #ingenieríadesoftware #preparaciónparaentrevistas #shorts [fr-FR] La meilleure formation en conception de systèmes est un dépôt GitHub gratuit #shorts Commentez « SYSTÈME » et je vous enverrai le dépôt 👇 Certains paient 148 $ pour une formation en conception de systèmes. Le guide « System Design Primer » est gratuit et compte plus de 370 000 étoiles. Il aborde la mise en cache, l’équilibrage de charge, le partitionnement et le théorème CAP, avec de vraies questions d’entretien, des solutions complètes et des fiches Anki. Dépôt : donnemartin/system-design-primer Prix de la formation : designgurus.io, vérifié le 19 octobre 2026. Dépôt de Donne Martin, CC BY 4.0. Voix off : Clone IA de ma propre voix. #conceptiondesystèmes #programmation #génielogiciel #préparationentretien #vidéoscourtes [hi] सिस्टम डिज़ाइन का सबसे बेहतरीन कोर्स एक फ्री GitHub रिपॉज़िटरी है #shorts SYSTEM लिखकर कमेंट करें और मैं आपको रेपो भेज दूँगा 👇 लोग सिस्टम डिज़ाइन कोर्स के लिए $148 खर्च करते हैं। सिस्टम डिज़ाइन प्राइमर मुफ़्त है और इसे 370K+ स्टार्स मिल चुके हैं। इसमें कैशिंग, लोड बैलेंसिंग, शार्डिंग और CAP थ्योरम शामिल हैं, साथ ही वास्तविक इंटरव्यू प्रश्न, पूर्ण समाधान और Anki फ्लैशकार्ड भी हैं। रेपो: donnemartin/system-design-primer कोर्स की कीमत: designgurus.io, 19 अक्टूबर 2026 को चेक किया गया। रेपो: डोने मार्टिन, CC BY 4.0 लाइसेंस के तहत। वॉइसओवर: मेरी अपनी आवाज़ का AI क्लोन। #systemdesign #coding #softwareengineering #interviewprep #shorts [id] Kursus system design terbaik adalah repo GitHub gratis #shorts Komentari SYSTEM dan saya akan mengirimkan repositorinya 👇 Orang-orang membayar $148 untuk kursus desain sistem. Kursus Dasar Desain Sistem ini gratis, dengan lebih dari 370 ribu bintang. Kursus ini mencakup caching, load balancing, sharding, dan teorema CAP, dengan pertanyaan wawancara nyata, solusi lengkap, dan kartu flash Anki. Repositori: donnemartin/system-design-primer Harga kursus: designgurus.io, diperiksa 19 Oktober 2026. Repositori oleh Donne Martin, CC BY 4.0. Narasi: Klon AI dari suara saya sendiri. #desainsistem #coding #rekayasaperangkatlunak #persiapanwawancara #video pendek [it] Il miglior corso di system design è un repository GitHub gratuito #shorts Commenta SYSTEM e ti invierò il repository 👇 C'è chi paga 148 dollari per un corso di progettazione di sistemi. Il System Design Primer è gratuito e ha più di 370.000 stelle. Tratta argomenti come caching, bilanciamento del carico, sharding e il teorema CAP, con domande di colloquio reali, soluzioni complete e flashcard Anki. Repository: donnemartin/system-design-primer Prezzo del corso: designgurus.io, verificato il 19 ottobre 2026. Repository di Donne Martin, CC BY 4.0. Voce fuori campo: clone AI della mia voce. #systemdesign #coding #softwareengineering #interviewprep #shorts [pt-BR] O melhor curso de design de sistemas é um repositório gratuito no GitHub #shorts Comente SYSTEM e eu te envio o repositório 👇 As pessoas pagam US$ 148 por um curso de design de sistemas. O System Design Primer é gratuito e tem mais de 370 mil estrelas. Ele aborda temas como cache, balanceamento de carga, particionamento de dados e o teorema CAP, com questões reais de entrevistas, soluções completas e flashcards do Anki. Repositório: donnemartin/system-design-primer Preço do curso: designgurus.io, verificado em 19 de outubro de 2026. Repositório por Donne Martin, CC BY 4.0. Narração: clone de IA da minha própria voz. #systemdesign #coding #softwareengineering #interviewprep #shorts

GitHub लिंक में 1 शब्द बदलो, AI टूल मिलेगा 🤯 | 3 Free Tricks GitHub link me sirf ek word badlo aur free AI tool khul jayega - kisi bhi public repo ke liye. Video me dikhaye gaye sab screens real hain (repo: donnemartin/system-design-primer). Example repo: donnemartin/system-design-primer Trick 1 - DeepWiki (AI wiki): URL me "github" ki jagah "deepwiki" likho. deepwiki.com Poore repo ki AI-generated wiki milti hai (topics, source file references, diagrams). Neeche "Ask Devin" box me repo ke baare me sawaal bhi pooch sakte ho. Trick 2 - Gitingest (repo ko prompt banao): URL me "github" ki jagah "gitingest" likho. gitingest.com Summary, directory structure aur saari files ka text ek jagah. "Copy all" dabao aur ChatGPT ya kisi bhi AI me paste karke sawaal poochho. Limit: default me sirf 50kB se chhoti files include hoti hain, aur bahut bade repos me ek limit tak hi files analyze hoti hain. Bada repo ChatGPT ki text limit cross kar sakta hai. Trick 3 - GitDiagram (architecture diagram): URL me "github" ki jagah "gitdiagram" likho. gitdiagram.com Repo ka architecture diagram ban jata hai. "Enable zoom" dabao, aur "Export" se PNG download karo. Steps (kisi bhi public repo ke liye): 1. GitHub par repo kholo. 2. Address bar me "github.com" me se sirf "github" hatao. 3. deepwiki / gitingest / gitdiagram likho aur Enter dabao. Login ki zaroorat nahi. Follow Daily AI Hacks - roz ek AI hack! #Shorts #AIHacks #GitHub #Coding #Programming [bn] GitHub লিঙ্কে ১টি শব্দ পরিবর্তন করুন, AI টুল পান 🤯 | ৩টি ফ্রি ট্রিকস যেকোনো পাবলিক রিপোর জন্য, গিটহাব লিঙ্কে শুধু একটি শব্দ পরিবর্তন করলেই ফ্রি এআই টুলটি খুলে যাবে। ভিডিওতে দেখানো সমস্ত স্ক্রিন আসল (রিপো: donnemartin/system-design-primer)। উদাহরণ রিপো: donnemartin/system-design-primer কৌশল ১ – ডিপউইকি (এআই উইকি): URL-এ "github"-এর জায়গায় "deepwiki" লিখুন। deepwiki.com সম্পূর্ণ রিপোটির একটি এআই-জেনারেটেড উইকি পাওয়া যাবে (টপিক, সোর্স ফাইলের রেফারেন্স, ডায়াগ্রাম)। আপনি নিচের "Ask Devin" বক্সে রিপোটি সম্পর্কে প্রশ্নও করতে পারেন। কৌশল ২ - গিটিংগেস্ট (রিপোটিকে প্রম্পট করুন): URL-এ "github"-এর পরিবর্তে "gitingest" লিখুন। gitingest.com সমস্ত ফাইলের সারাংশ, ডিরেক্টরি কাঠামো এবং টেক্সট এক জায়গায়। "Copy all" চাপুন এবং প্রশ্ন করার জন্য এটি ChatGPT বা যেকোনো AI টুলে পেস্ট করুন। সীমাবদ্ধতা: ডিফল্টরূপে, শুধুমাত্র ৫০kB-এর চেয়ে ছোট ফাইলগুলো অন্তর্ভুক্ত করা হয়, এবং খুব বড় রিপোগুলো একটি নির্দিষ্ট সীমা পর্যন্ত ফাইল বিশ্লেষণ করে। বড় রিপোগুলো ChatGPT-এর টেক্সট সীমা অতিক্রম করতে পারে। কৌশল ৩ - GitDiagram (আর্কিটেকচার ডায়াগ্রাম): URL-এ "github"-এর পরিবর্তে "gitdiagram" লিখুন। gitdiagram.com রিপোটির আর্কিটেকচার ডায়াগ্রাম তৈরি হয়ে যাবে। "Enable zoom" চাপুন এবং "Export" থেকে PNG ফাইলটি ডাউনলোড করুন। ধাপসমূহ (যেকোনো পাবলিক রিপোর জন্য): ১. GitHub-এ রিপোটি খুলুন। ২. অ্যাড্রেস বার থেকে "github.com"-এর পরিবর্তে "github" মুছে ফেলুন। ৩. deepwiki/gitingest/gitdiagram টাইপ করুন এবং এন্টার চাপুন। কোনো লগইনের প্রয়োজন নেই। ডেইলি এআই হ্যাকস অনুসরণ করুন - প্রতিদিন একটি করে এআই হ্যাক! #শর্টস #এআইহ্যাকস #গিটহাব #কোডিং #প্রোগ্রামিং [en] Change 1 Word in a GitHub Link, Get an AI Tool 🤯 | 3 Free Tricks Change one word in any public GitHub repo URL and a free AI tool opens. Every screen in this video is real (repo: donnemartin/system-design-primer). Example repo: donnemartin/system-design-primer Trick 1 - DeepWiki (AI wiki): replace "github" with "deepwiki". deepwiki.com An AI-generated wiki of the whole repo, plus an "Ask Devin" box to ask questions about it. Trick 2 - Gitingest (turn the repo into a prompt): replace "github" with "gitingest". gitingest.com Summary, directory structure and all file contents in one place. Tap "Copy all" and paste into ChatGPT or any AI. Limit: by default only files under 50 kB are included, and very large repos are only partly analyzed. Trick 3 - GitDiagram (architecture diagram): replace "github" with "gitdiagram". gitdiagram.com Draws the repo's architecture diagram. Tap "Enable zoom", or "Export" to download a PNG. Steps (any public repo): 1. Open the repo on GitHub. 2. In the address bar, delete just "github" from "github.com". 3. Type deepwiki / gitingest / gitdiagram and press Enter. No login needed. Follow Daily AI Hacks - one AI hack every day! [en-US] Change 1 word in your GitHub link, get an AI tool 🤯 | 3 Free Tricks Just change one word in the GitHub link and the free AI tool will open – for any public repo. All screens shown in the video are real (repo: donnemartin/system-design-primer). Example repo: donnemartin/system-design-primer Trick 1 – DeepWiki (AI wiki): Replace "github" with "deepwiki" in the URL. deepwiki.com An AI-generated wiki of the entire repo is available (topics, source file references, diagrams). You can also ask questions about the repo in the "Ask Devin" box below. Trick 2 - Gitingest (make the repo prompt): Instead of "github" in the URL, write "gitingest". gitingest.com Summary, directory structure, and text for all files in one place. Press "Copy all" and paste it into ChatGPT or any AI tool to ask questions. Limit: By default, only files smaller than 50kB are included, and very large repos only analyze files up to a certain limit. Large repos may exceed ChatGPT's text limit. Trick 3 - GitDiagram (architecture diagram): Instead of "github" in the URL, write "gitdiagram." gitdiagram.com The repo's architecture diagram is created. Press "Enable zoom" and download the PNG from "Export." Steps (for any public repo): 1. Open the repo on GitHub. 2. Remove "github" from "github.com" in the address bar. 3. Type deepwiki/gitingest/gitdiagram and press Enter. No login required. Follow Daily AI Hacks - one AI hack every day! #Shorts #AIHacks #GitHub #Coding #Programming

5 free GitHub repos for coding interview prep (LeetCode, system design) Stop paying for interview prep. These 5 GitHub repos are free. 1. Tech Interview Handbook (Grind 75: which LeetCode problems to solve, week by week): yangshun/tech-interview-handbook 2. Coding Interview University (a complete CS study plan): jwasham/coding-interview-university 3. System Design Primer (how apps like Twitter are designed): donnemartin/system-design-primer 4. Build Your Own X (rebuild Git, Redis or a database; that's a resume project): codecrafters-io/build-your-own-x 5. Developer Roadmap (a step-by-step path for every tech role): roadmap.sh Save this for your next prep week and send it to your study partner. #InterviewPrep #LeetCode #SystemDesign #GitHub #SoftwareEngineer #shorts

Load balancers, caching, databases, distributed systems, scalability. Everything that sounds intimidating when a senior engineer starts talking. A massive free resource for understanding how large-scale systems work. donnemartin/system-design-primer

System Design Primer Learn how larger applications handle traffic, databases, caching and scaling. It's especially useful for understanding system design interviews. A good next step once you're comfortable with coding basics. GitHub repo - donnemartin/system-design-primer

@costlytweets Dinikante best edi ledu donnemartin/system-design-primer

System design capstone and final assessment --- title: "System design capstone and final assessment" published: true description: "Design a system from a one-line brief, with a pacing guide, a 100-point rubric and a 12-question assessment." tags: systemdesign, architecture, career, tutorial series: System Design Learning Path --- Part 8 of 8 · week 8 of the learning path The capstone has each team design a new system from a one-line brief, using the same six steps as the case studies, and the final assessment checks that everyone can apply the ideas to fresh scenarios. Capstone brief. Pick one, or have the trainer assign it: - A photo sharing feed for 50 million daily users. - A ride-hailing service that matches riders to nearby drivers. - A file sync service like a cloud drive. - A notification service that sends push, email and SMS at scale. - A distributed rate limiter used by many services. Deliverables: a design document of up to four pages following the six steps, one architecture diagram with numbered steps, and a 15-minute presentation followed by 10 minutes of questions. Pacing for a 45-minute design interview or review | Minutes | Step | | --- | --- | | 5 | Clarify requirements and scope | | 5 | Estimate load and storage | | 5 | Define the API and data model | | 10 | Draw the high-level design | | 15 | Deep dive on the two or three hardest parts | | 5 | Trade-offs, failures and monitoring | Common mistakes: skipping requirements, designing without numbers, leaving a single point of failure, ignoring duplicates and retries, forgetting how it will be monitored, and choosing exotic technology without a reason. Capstone rubric (100 points, pass mark 70) | Criterion | Points | What good looks like | | --- | --- | --- | | Requirements and scope | 15 | Functional and non-functional needs are explicit, with scope limits stated | | Estimation | 15 | Numbers are reasonable, shown, and used to drive choices | | Architecture and data model | 25 | A clear diagram, sensible components, API and data model that fit the requirements | | Deep dives | 25 | Consistency, scaling and failure handling are worked through for the hardest parts | | Trade-offs and operations | 20 | Alternatives are weighed, and monitoring, security and cost are addressed | Final assessment (12 scenario questions, pass mark 9, Architect level needs 11) 1. A photo app has 50 million daily users who each upload 2 photos of 3 MB a day. About how much new storage is needed per day before replication? - A) 30 TB - B) 300 TB - C) 3 PB - D) 3 TB 2. Which pattern keeps a multi-service order consistent without a distributed transaction? - A) A saga with compensating actions - B) A shared lock across services - C) A bigger database - D) Retrying every step forever 3. A service must guarantee that a database update and the matching event are both recorded. What should it use? - A) Publish the event first, then update the database - B) Update the database, then publish in a separate step - C) A bigger queue - D) The outbox pattern: write both in one transaction and publish from the outbox 4. A chat message reaches the server twice because the client retried. How do you avoid showing it twice? - A) Compare timestamps - B) Ignore all retries - C) Deduplicate by a client-generated message ID - D) Increase the timeout 5. A new video loads slowly for its first viewers but fast for later ones. Why? - A) Disk wear - B) The first request fills the edge cache from the origin and later requests hit the cache - C) DNS caching - D) Encoding finishes later 6. Two refund requests for the same payment arrive at the same moment. What stops the system refunding more than was paid? - A) Hope they do not collide - B) Separate caches - C) Eventual consistency - D) A transaction on a versioned or locked payment row, so the second request sees the first refund 7. A user updates their profile but sees the old value on reload. What is the likely cause and fix? - A) Reading from a lagging follower; read your own writes from the leader - B) A browser bug; clear cookies - C) Too few indexes; add more - D) Encryption; turn it off 8. A table keyed by timestamp has one overloaded partition. What is the best fix? - A) Give that partition larger disks - B) Add more replicas - C) Hash or combine the key so current writes spread across partitions - D) Delete old data 9. Two services always deploy together and share a database. What is this? - A) An ideal microservices design - B) A distributed monolith; merge them or redraw the boundaries - C) A gateway problem - D) A replica problem 10. The card network times out on an authorization. What should the payment service do? - A) Mark it processing and check its status or reconcile before any retry - B) Retry the authorization at once - C) Tell the customer it failed and refund - D) Delete the payment 11. Peak traffic is 3 million requests per second. Each server can handle 5,000 per second, and you run servers at 50% of that. About how many servers are needed? - A) 600 - B) 300 - C) 2,400 - D) 1,200 12. Events for the same order arrive out of order at a consumer. What is the best design? - A) Turn off the broker - B) Add more consumers - C) Key by order ID so they share a partition, and use version numbers to ignore stale events - D) Make the messages smaller {% details Final assessment answers %} 1. B 50 million times 2 times 3 MB is 300 TB per day. 2. A 3. D 4. C 5. B 6. D 7. A 8. C 9. B 10. A 11. D each server effectively handles 2,500 per second at 50% load, and 3 million divided by 2,500 is 1,200 servers. 12. C {% enddetails %} Sources and further reading - System Design Primer, with more practice problems and sample solutions for capstone ideas. - Designing Data-Intensive Applications, for checking consistency and failure reasoning in deep dives. - Timeouts, retries, and backoff with jitter, for the failure-handling part of the rubric. Resources - Designing Data-Intensive Applications by Martin Kleppmann, the main reference for Modules 3 and 4. - Building Microservices by Sam Newman, for Module 2. - System Design Interview by Alex Xu, for more worked designs. - Site Reliability Engineering from Google, for reliability and monitoring practice. - Stripe documentation on idempotent requests and on webhooks, for Module 7. The real-world figures in the case studies (message volume, hours uploaded and watched, connection counts) come from public statements and engineering write-ups and are used as inputs for exercises. Trainers should check the current numbers before each cohort. ``

Day-1 of finding goated GitHub repos System Design Primer: One of the most popular repositories on GitHub, offering a comprehensive, organized walkthrough of scalability, latency, caching, load balancing, and sample interview questions. Link: donnemartin/system-design-primer t.co

System design fundamentals: estimate, scale and trade off --- title: "System design fundamentals: estimate, scale and trade off" published: true description: "Back-of-envelope math, the core building blocks and the design method used in every later post." tags: systemdesign, architecture, beginners, tutorial series: System Design Learning Path --- Part 1 of 8 · week 1 of the learning path Every large design is the same few building blocks combined to meet numbers, so learn the blocks and learn to estimate before drawing any boxes. Learning objectives - Turn a product request into functional and non-functional requirements. - Do back-of-envelope estimates for traffic, storage and bandwidth. - Explain what each core building block does and when to use it. Requirements first - Functional: what the system does (send a message, upload a video, charge a card). - Non-functional: how well it does it: scale, latency, availability, durability, consistency, security and cost. - Ask about scope and priorities before designing; a design for 1,000 users and one for 100 million are different systems. Estimation cheat sheet | Fact | Rule of thumb | | --- | --- | | Seconds in a day | About 86,400, so requests per day divided by 86,400 gives average QPS | | Peak versus average | Plan for 2 to 3 times average, more for spiky products | | Memory read | About 100 nanoseconds | | SSD random read | About 100 microseconds | | Round trip inside one datacenter | About 0.5 milliseconds | | Round trip across continents | About 150 milliseconds | | Storage | Records per day times record size times retention | Worked example: 10 million daily users each make 20 reads and 2 writes a day. Reads are 200 million a day, about 2,300 per second on average and about 7,000 at a 3x peak. Writes are 20 million a day, about 230 per second and about 700 at peak. At 1 KB per write, that is 20 GB a day, or about 7.3 TB a year before replication. Building blocks | Block | Job | Key choices | | --- | --- | --- | | Load balancer | Spreads requests across instances | Layer 4 or layer 7, health checks, algorithm | | Cache | Serves hot data from memory | Cache-aside versus write-through, eviction, expiry, stampede protection | | CDN | Serves static and cacheable content near users | What to cache, expiry, invalidation | | Relational database | Structured data with transactions | Indexes, replicas, sharding | | NoSQL store | Scale and flexible models | Key-value, document, wide-column, graph | | Queue or log | Decouples producers and consumers, absorbs spikes | Ordering, retention, delivery guarantees | | Object storage | Cheap durable storage for large files | Lifecycle, access control | | Search index | Full text and filtered queries | Refresh lag, relevance | | Rate limiter | Protects services from abuse and overload | Token bucket, per-user or per-key limits | Scaling basics: make services stateless so any instance can serve any request; scale out behind a load balancer; cache reads; replicate data for reads and safety; shard data when one node cannot hold or write it all. When the network splits, a distributed store must choose consistency or availability, so decide per feature which matters more. Design exercise: a URL shortener gets 100 million new links a month with ten reads per write. Estimate write and read QPS, storage over five years and cache size for the hottest 20% of links, then list the blocks you would use. Quiz 1 (5 questions, pass mark 4) 1. About what is the average QPS for 86.4 million requests a day? - A) 100 - B) 1,000 - C) 10,000 - D) 86,400 2. Why is a stateless service easy to scale? - A) It uses sticky sessions - B) It keeps sessions in local memory - C) Any instance can serve any request, so you add instances behind a load balancer - D) It needs a single large server 3. What is cache-aside? - A) The cache is the only store - B) Reads bypass the cache - C) The database pushes every write into the cache - D) The app checks the cache first and, on a miss, reads the database and fills the cache 4. What does a CDN mainly do? - A) Serves static and cacheable content from locations near users, cutting latency and origin load - B) Stores financial transactions - C) Runs SQL queries - D) Encrypts the database 5. How should you size for traffic peaks? - A) Use the average only - B) Ignore peaks - C) Plan for a multiple of average, commonly 2 to 3 times or more, plus headroom - D) Assume every second is a peak {% details Quiz 1 answers %} 1. B 86.4 million divided by 86,400 seconds is 1,000 requests per second. 2. C 3. D 4. A 5. C {% enddetails %} Sources and further reading - Latency numbers every programmer should know, the Jeff Dean and Peter Norvig figures behind the estimation table; the numbers are rough and dated, so use them for orders of magnitude. - System Design Primer, an open study guide covering the building blocks in this module. - Designing Data-Intensive Applications by Martin Kleppmann, for caching, replication and consistency in depth. --- Part 1 of 8 in the System Design Learning Path series. Next: part 2.