You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's learn about System Design via these 174 free blog posts. They are ordered by HackerNoon reader engagement data. Visit the /Learn or LearnRepo.com to find the most read blog posts about any technology.
System design is the process of defining the architecture, components, and interfaces for a system to satisfy specified requirements. It is critical for building scalable, reliable, and maintainable software systems, ensuring they meet both current and future needs.
Designing Large Scale Distributed Systems has become the standard part of the software engineering interviews. Engineers struggle with System Design Interviews (SDIs), primarily because of the following two reasons:
I recently published a post How NOT to design Netflix in your 45-minute System Design Interview?. First, surprisingly, it got pretty popular. Secondly, and even more surprisingly, several people reached out to me asking if there are any tips on what NOT to do during their coding interviews. Most of these people had the questions along the following lines:
If you’re a software engineer interviewing for a backend role, you’ll probably be tested on how well you can design a system architecture given some goals and constraints. It's one of the most high-signal interviews, because it’s open-ended, which presents more opportunities for both mistakes and flexes. An important detail is that these interviews test not only your knowledge of backend systems, but also how effectively you can communicate your ideas.
SOLID Principles are the principles of objective oriented programming essential to develop scalable softwares. S stands for Single Responsibility Principle ...
This article argues that true engineering excellence lies not in adopting new frameworks or rewriting systems but in sustaining resilient, boring infrastructure
Discover the key features of Load Balancers, Reverse Proxies, Forward Proxies, and API Gateways. Ideal for refreshing knowledge before System Design interview.
So I’m on zero sleep. I decided last night at 3am that it wasn’t worth waiting in bed, hoping to fall asleep anymore, having to wake up at 8am anyway. Being incredibly tired, beyond tired, loopy even, I think, “what to do?” I don’t have much to do to pack before my flight tomorrow, and I’m useless for anything productive...maybe a little Factorio?
The popular implementations of an on-demand video streaming service are the following: YouTube, Netflix, Vimeo, and TikTok. The video files are stored in a mana
A practical look at designing API contracts during legacy system modernization, focusing on real production failures and strategies to prevent silent regression
Apple Vision Pro revolutionizes presentations and mind mapping for product management and system design, yet faces drawbacks, indicating room for improvement.
I was very much interested in developing distributed systems and the like. But it was very difficult to find related beginner articles. One of my projects was a cloud drive. In order to implement that, i had to go many places i haven't. It had a good steep learning curve. I wanted to share that knowledge.
Some of the popular implementations of a Kanban board are the following: Trello, JIRA, Microsoft Planner, and Asana. The changes on the board are synchronized i
Imagine — You’re in a system design interview and need to pick a database to store, let’s say, order-related data in an e-commerce system. Your data is structured and needs to be consistent, but your query pattern doesn’t match with a standard relational DB’s. You need your transactions to be isolated, and atomic and all things ACID… But OMG it needs to scale infinitely like Cassandra!! So how would you decide what storage solution to choose? Well, let’s see!
Explore 25 key system design interview questions with detailed answers, covering topics like scalability, load balancing, proxies, database sharding, and more.
You'll likely be asked some system design questions when interviewing at many tech companies today. Here's how to use the whiteboard to answer them effectively.
CAP theorem proofed and explained. Why is it important? What are consistency, availability, and partition tolerance? How does it relate to distributed systems?
That dreaded system design interview. I remember the first system design question I was asked. “Design WhatsApp”, he said. I didn’t know where to start! I was a fresher. Data structures and algorithms were the only things I knew. I am sure you can guess how that interview went. Then after enough research, I made myself a checklist of components, of sorts, to navigate me through my next system design interviews. And I sh*t you not, it works!
This short post is written for recent graduates and current students who aim to find a job as a Software Engineer in the Tech industry and contains a list of resources to help them.
In the Software Engineering world, if you are applying for a Senior Engineer/Lead/Architect or a more senior role, System Design is the most sought-after skill
Cassandra is designed to prioritize availability and partition tolerance, making it suitable for applications where consistency is not a critical requirement.
Learn the key stages of implementation, the role of tools like FastAPI, and the significance of algorithms like ANNs in creating personalized experiences.
Scale system design interviews with these essential topics—scalability, fault tolerance, data storage, caching, message queues, and event-driven architecture.
What is the significance of blockchain technology in the future, why can Bitcoin be hyped for over ten years and still have such strong vitality? It is impossible to know what the future world will look like without studying these issues in depth.
The term “industrial electronics” refers to any electrical equipment or system used for manufacturing goods or participating in this process indirectly.
Dive deep into the many layers of caching in modern systems from browser and CDN to app memory and database internals. Learn strategies, consistency models.
You don’t need sprints to ship good products. You just need clear focus, quick feedback loops, and the discipline to actually finish things before moving on.
Learn how backpressure helps distributed systems stay resilient under load. Explore real-world patterns to manage flow control, retries, and queue buildup.
Explore corporate information system integration, its strategic tasks, and challenges. Learn about EDA, ESB, ETL, security, software architecture, and more.
This article proposes a mindset shift in using LLMs: instead of using them to generate code, use them to aggressively critique and "break" architectural designs
CAP theorem isn't about picking two. Learn what Consistency, Availability, and Partition Tolerance actually mean and how production systems handle trade-offs.
Confused by cookies, tokens, and API keys? This guide breaks down 6 common authentication methods — Basic Auth, Cookies, Tokens, API Keys, OTP, and SSO!
In 2025, the developer's role is shifting from a manual "writer" to a strategic "orchestrator," managing teams of digital agents that can self-correct.
AI is a powerful accelerator for writing code and optimizing queries, but it lacks the contextual understanding to make high-stakes architectural trade-offs.
Latency sensitive financial systems favor predictable behavior and controlled execution paths, even as tools, infrastructure, and languages continue to evolve.
Redis doesn’t track expirations with sorted lists, it uses randomness. Learn how its probabilistic key cleanup keeps speed, memory, and simplicity in balance.
Boost system resilience and scalability by splitting services into self-contained cells with dedicated routing, reducing failure impact and deployment risk.
I designed an autonomous REIT where AI, blockchain, and automation replace intermediaries—handling leasing, rent, and dividends end-to-end. With on-chain settle
Your go‑to guide for understanding system design end‑to‑end—clear explanations of High‑Level and Low‑Level Design with everything you need to get started
As per Gartner, almost 80 percent of every emerging technology will have Artificial Intelligence as the backbone by the end of 2021. Building secure software is a no mean feat. Amid the lingering cybersecurity threats and the potential challenges posed by the endpoint inadequacies, the focus is continuously shifting towards machine learning and the relevant AI implementations for strengthening the existing app and software security standards.
GDPR's "right to be forgotten" just redesigned your database. HIPAA moved your PHI to a separate infrastructure. Here’s how compliance shapes architecture.
Explore consistency guarantees like read-after-write, monotonic reads, and consistent prefixes in the second series on replication in distributed systems.
Rethinking UNIQUE INDEXes: Explore why they can be costly and problematic in large-scale, why application-layer uniqueness checks are more flexible and robust
Availability refers to the ability of a system to remain operational and accessible to users even in the face of various failures, disruptions, and maintenance.
A real-world failure shows why distributed systems must be designed for failure, not success, using circuit breakers, timeouts, and resilience patterns.
Maintain atomicity in distributed systems with protocols like Two-Phase Commit and the Saga Pattern, addressing challenges in microservices environments.
How Reddit scaled from a single Python server to a resilient architecture that could handle millions. A story of caching, queues, and the chaos of success.
Explore leaderless replication in distributed systems, from ensuring quorum consistency to implementing Last Write Wins, conflict resolution and version vectors
Explore the detailed system design of vAttention, which leverages separate virtual and physical memory allocation to enable dynamic KV-cache management
How agentic AI with MCP protocols is replacing complex UI development. Learn to build systems with LLMs at the center, ship features in days, not months.
Explore 5 advanced data structures that go beyond arrays and linked lists. Learn how B-Trees, Bloom Filters, Radix Trees, and more power modern systems.
Your distributed lock is silently failing. Learn how GC pauses and clock skew break DynamoDB, Redis, and ZooKeeper locks and how fencing tokens close the gap.
