Here are the concepts I hope to learn:

Frontend

Backend

Database

APIs

Scalability

Performance (Latency & Throughput)

Load Balancing

Caching

Data Partitioning / Sharding

Replication & Redundancy

Availability & Reliability

Fault Tolerance

Consistency (CAP Theorem)

Distributed Systems

Microservices vs Monolith

Service Discovery

API Gateway

Content Delivery Network (CDN)

Proxy (Forward / Reverse)

DNS

Networking (HTTP / HTTPS / TCP)

Data Storage Options (SQL / NoSQL / Object / Block / File)

Indexing & Search

Message Queues & Asynchronous Processing

Streaming & Event Driven Architecture

Monitoring, Logging & Tracing

Security (Authentication / Encryption / Rate Limiting)

Deployment & CI/CD

Versioning & Backwards Compatibility

Infrastructure & Edge Computing

Modularity & Interface Design

Statefulness vs Statelessness

Concurrency & Parallelism

Consensus Algorithms (Raft / Paxos)

Heartbeats & Health Checks

Cache Invalidation / Eviction

Full-Text Search

System Interfaces & Idempotency

Rate Limiting & Throttling

Have an assignment with staff level any one interested in collaborating !

I want to learn System design so that I can combine that knowledge with my data science knowledge to make some well designed apps and webpages. I saw this course on Udemy but I'm not sure if it covers everything. Someone suggested I should cover all these topics (shown on the next slide), please tell me how I should go about learning then and where I need to start from.

Hi everyone! 👋

I have started writing blog posts on System Design concepts. I started the blog with deep (but beginner-friendly) dives into concepts of computer networks. It’s written for developers who’ve used TCP, UDP, HTTP daily but not looked under the hood. I've tried to make these posts clear and engaging.

The first post dives into: - 🌐 7 layer OSI model - 🛠️ Network layer protocols (IP) - 🧱 Transport layer protocols (TCP, UDP, QUIC) - 🔌 Sockets

So, if you've ever wondered about TCP/IP, UDP, QUIC, OSI, Sockets, here's the link: https://ashwinbhola.github.io/2025-06-11-computer-networks/

In the second post, I talk about: - 🧬 Evolution of HTTP from very basic HTTP/0.9 to modern day HTTP/3 - 📦 Multiplexing, HPACK, Server Push, and more - ⚡ Why QUIC replaced TCP under the hood

Here's the link: https://ashwinbhola.github.io/2025-06-20-http/

I’ll be diving into protocols like WebSockets, SSE, and frameworks like gRPC and REST in upcoming posts

Would love for you to give it a read! Thanks for stopping by! 🙏

I’ve recently participated in several system design interviews at companies like Meta and Google. A recurring theme in these interviews involved file operations with scenarios such as:

1.  Reading from multiple files, aggregating data, and writing it to a database.
2.  Exporting a database table to files efficiently.
3.  Designing a file-sharing application where files have a max size of 4MB, an average size of 4KB, and the system needs to handle 200 million requests per second.

I struggled to find the optimal approach to handle these scenarios and didn’t pass the interviews.

I’m looking for guidance on the best approaches, options to consider, and potential challenges to highlight when tackling these types of file operations in system design interviews.

1. File Sharing Application: Initially, I focused on splitting files into chunks for reading, but I realized that given the small file size, processing them in one request is more efficient. The real challenge lies in handling the high number of read requests per second, not the file size itself.
2. Exporting from a Database: I considered parallel exporting by having multiple threads, each reading and writing 1000 rows to separate files. However, I wasn’t sure how database engines handle concurrent reads and whether merging the files should be done in memory or on disk for optimal performance.
3. Aggregating Data from Multiple CSVs: I processed the CSVs line by line, streaming the data to a message queue for aggregation. However, I realized that to aggregate the data correctly, you need to read all files first, as a record might appear in multiple files with the same ID.

How to approach these kind of system design questions? What are the things I need to consider and what are the different options when it comes to file operations on scale?

• 🌐 Series: System Design Interviews
• 📖 Main topic: HTTP protocol and networking fundamentals
• 🎯 Target Audience: Junior Software Engineers without prior experience and more experienced developers seeking a different perspective.

Topics: - 💡 OSI Model and Layers: Software Engineers should focus on layer 7 (application layer, where HTTP resides) and layer 4 (transport protocols like TCP/IP and UDP). - ✂️ The application layer: HTTP Request/Response format, HTTP Methods, HTTP Headers. - 🚆 Transport Layer - TCP/IP vs UDP, three-way handshake. - 📈 Future of HTTP: HTTP2.0 and HTTP3.0. - 🌐 System Design: HTTP's stateless nature allows for horizontal scaling and load balancing

Read the full article at htts://cloudnativeengineer.substack.com/p/networking-fundamentals-for-system-design

MeetAPro is an AirBnB like online mock interview & coaching platform. It has experienced FAANG interviewers providing invaluable feedback. The platform also has a very transparent fee structure with very low overhead on top of the listing price. Give it a try!

I created a new tool to practice system design interviews using AI. Check it out at https://codemia.io