#System-Design
23 notas · última:
Notes on Distributed Systems for Young Bloods
A set of practical lessons for new distributed systems engineers, emphasizing failure, coordination costs, backpressure, metrics, percentiles, capacity, feature flags, and service extraction.
Tips to Become 10x Better in Tech Interviews
The piece argues that interview success comes from preparation with leverage: build relationships before you need them, treat interviews as practice, prepare adaptable stories, and negotiate the format when you can.
Why system design is my favorite interview
The post argues that system design interviews reveal the most signal in an hour, because they test working design, judgment, questions, and tradeoffs while reflecting real engineering experience.
4 Steps to Prepare for System Design Interviews in 2025
The page says system design interviews require core concepts, engineering blogs, common questions, and repeated practice, with mock interviews and timing used to avoid common mistakes.
Interview Question: how do you ensure you only virus scan once?
The article argues for interview questions based on real work, using a file-upload and virus-scanning scenario to test system design, performance, fault tolerance, and UX rather than rote algorithms.
Polling Vs Webhooks
The post contrasts polling, which checks for new data at intervals, with webhooks, which push updates through a callback URL when events happen. It explains when each approach fits.
8 Must-Know Strategies to Build Scalable Systems
The page lists eight ways to make systems scale under higher load: stateless services, horizontal scaling, load balancing, auto-scaling, caching, database replication, sharding, and asynchronous processing.
15 Must-Know Elements of System Design
The post groups core system design elements into distributed systems, messaging, caching, scaling, networking, storage, and observability, and explains what each one does in a distributed setup.
GitHub - karanpratapsingh/system-design: Learn how to design systems at scale and prepare for system design interviews
Course outline on system design covering networking, storage, databases, distributed systems, APIs, messaging, security, and interview patterns, plus worked designs for URL shortener, WhatsApp, Twitter, Netflix, and Uber.
Twitter System Design Example for Tech Interviews
A system design guide for interviews that structures the creation of a Twitter/X.com into requirements, capacity estimates, APIs, database, architecture, and trade-offs.
Designing Intelligence: System Design in AI/ML Evolution
The piece connects principles such as simplicity, context, resilience, ethics, and decision making to design choices in ML, arguing for useful, interpretable solutions aligned with the business.
EP130: Design a System Like YouTube
Covers eight Software Development Life Cycle models and a 9-step pipeline for a YouTube-like video system, from upload through transcoding to CDN delivery.
EP118: What are the differences among database locks?
A five-topic system design refresher: database lock types, six pagination techniques, MVC-family architecture patterns, what happens on a URL request, and QR code payments.
Design a Rate Limiter
Hello Interview's breakdown walks a system-design rate limiter from placement decisions through four limiting algorithms, landing on Token Bucket over Redis with a Lua script to close the race condition.
33/60 Days System Design Questions
A daily.dev system design prompt: an order service that only stores current state can't reconstruct a billing dispute, and the post argues event sourcing is the real fix, not a patch.
Review — Is Designing Data-intensive Applications by Martin Kleppman Worth it?
The review argues that Martin Kleppmann’s book is a worthwhile, broad guide to data-intensive application design, with strong coverage of databases, distributed systems, reliability, scalability, and trade-offs.
10 Reasons to Learn System Design in 2025
The article argues that system design matters for interviews, scalability, distributed systems, leadership, optimization, and real-world software work, and it points to books, courses, and platforms for learning.
How to Design Twitter (X) in a System Design Interview?
The article outlines a structured way to answer a Twitter-like system design interview by covering requirements, capacity estimates, APIs, database tables, caching, load balancing, and failure scenarios.
System Design — Tips
A practical list of system design choices for scalability, availability, latency, and reliability, with examples showing when to use caches, queues, sharding, replication, and other patterns.
Message Queues in System Design
The page explains message queues as an asynchronous buffer between producers and consumers, showing how they decouple work, improve durability, and let systems scale under load.
System Design: How to Design Instagram
The post outlines Instagram-like requirements, storage tables, and a high-level architecture for uploading, reading, and generating photo feeds with caching, sharding, blobs, and two feed strategies.
Orchestration and choreography - ByteByteGo System Design
The page contrasts choreography and orchestration in microservices, showing orchestration as centralized control with transaction management and easier rule changes, but also higher latency and a single point of failure.
Taco Bell Programming
The essay argues that many systems problems can be solved by reconfiguring basic Unix tools instead of adding complex stacks. Simplicity reduces failure risk and often gets the job done.