The course "High-Level System Design" will help you understand how to design scalable and fault-tolerant applications: from basic client-server interaction to the architecture of distributed systems. In five weeks, you will study key System Design topics, learn how to choose architectural solutions, assess load, work with data, and explain your decisions in technical interviews.
About this course
The course is dedicated to high-level system design: service architecture, scaling, data storage, load balancing, caching, message queues, fault tolerance, monitoring, and API design. The material helps you connect individual engineering solutions into a cohesive architecture and understand which compromises must be considered when creating real-world products.
You will learn how to design applications under load, choose between monoliths and microservices, use SQL and NoSQL storages, build asynchronous interactions through Kafka or RabbitMQ, and prepare for System Design interview questions.
Who this course is for
- Backend developers who want to better understand the architecture of complex systems.
- Fullstack developers planning to develop towards System Design and backend engineering.
- Engineers preparing for technical interviews for middle, senior, and lead positions.
- Developers who need to learn how to justify architectural decisions and evaluate compromises.
What you will learn
- Client-server architecture, network protocols, and service interactions.
- Monolithic architecture, microservices, and system decomposition approaches.
- Scaling, load balancing, caching, and request routing.
- SQL, NoSQL, indexing, replication, sharding, and distributed transactions.
- Message queues, Pub/Sub, Kafka, RabbitMQ, and asynchronous event processing.
- Fault tolerance, monitoring, logging, rate limiting, and API security.
- A practical analysis of the architecture of popular services: a messenger, video platform, ride-sharing service, and brokerage application.
Course program
Week 1 — Networks and Service Interactions
You will start with the fundamental principles of client-server interaction. You'll examine how network protocols work, the differences between monolithic architecture and microservices, and when to use WebSocket, Server-Sent Events (SSE), and gRPC.
Week 2 — Performance and Scaling
In the second week, you will study latency and throughput, consistency and availability, the CAP theorem, synchronous and asynchronous interaction. Particular attention is given to Pub/Sub, Kafka, RabbitMQ, proxies, load balancing, caching, service routing, and P2P approaches.
Week 3 — Data and Databases
You will learn how to choose a data storage solution for the task: SQL, NoSQL, and specialized databases. The program also includes migrations, indexing, replication, sharding, consistent hashing, horizontal and vertical scaling, and distributed transactions.
Week 4 — Design and Operation
This part of the course focuses on the practical aspects of system operation: assessing required resources, polling and streaming, configuration, rate limiting, pagination, filtering, fault tolerance, logging, monitoring, API design, and security.
Week 5 — Practice and Interview Preparation
The final week is devoted to analyzing the high-level architecture of real systems. You will consider designing a messenger like WhatsApp or Discord, a video platform like YouTube, a ride-sharing service like Uber, and a brokerage application. The course concludes with preparation for System Design interview questions.
What skills you will gain
- You will learn to design high-level architecture for applications and distributed systems.
- You will be able to assess load, choose scaling approaches, and explain architectural compromises.
- You will understand how to build robust services with caching, queues, replication, and monitoring.
- You will be more confident in answering System Design interview questions.
Conclusion
The course will help you move from a set of individual technical knowledge to a systematic understanding of architecture. You will learn not only how to choose technologies, but also how to explain why a specific solution is suitable for a certain load, business task, and level of reliability.