If you want to get better at System Design, read these 19 articles: [1] Extracting Services from a Monolithic App Why read it: Learn how to migrate critical functionality to a new service in a risk-free manner https://t.co/PfttjkageF [2] Should You Fire and Forget an Event Why

15 articles to help you get better at System Design: [1] 4 Challenges of Distributed Systems - And Possible Solutions https://t.co/aXWgGRJrDw [2] Your Code is Fast, But Your Database is Slow—Now What? https://t.co/naVF9SkRe0 [3] 15 Must-Know Elements of System Design

15 articles to help you get better at System Design: [1] 4 Challenges of Distributed Systems - And Possible Solutions https://t.co/aXWgGRJrDw [2] Your Code is Fast, But Your Database is Slow—Now What? https://t.co/naVF9SkRe0 [3] 15 Must-Know Elements of System Design

What’s the most important part of Event-Driven Architecture? Events, of course. In an EDA-based application, different components communicate by sending and receiving events. But what exactly is an event? It is an occurrence that has happened in the application. Some

Interested in System Design? Subscribe to my newsletter for more detailed posts. https://t.co/zu2eLJcXfO

What’s the most important part of Event-Driven Architecture? Events, of course. In an EDA-based application, different components communicate by sending and receiving events. But what exactly is an event? It is an occurrence that has happened in the application. Some

What’s the deal with Stateless Architecture? The term “stateless architecture” can be a little confusing. It seems to imply that the system is without any state. This is not exactly true. Stateless architecture just means that the state information (if needed) is stored

Interested in System Design? Subscribe to my newsletter for more detailed posts on concepts and case studies. https://t.co/zu2eLJcXfO

What’s the deal with Stateless Architecture? The term “stateless architecture” can be a little confusing. It seems to imply that the system is without any state. This is not exactly true. Stateless architecture just means that the state information (if needed) is stored

24 principles that can help you navigate System Design Interviews: ✅ If you need to scale an individual component, stick with Vertical Scaling first. Then, look at Horizontal Scaling when needed ✅ To deal with traffic spikes, evaluate the use of Autoscaling for Dynamic

Layer 4 vs Layer 7 Load Balancers Simplified ✅ Layer 4 Load Balancer As the name suggests, Layer 4 load balancers operate in the transport layer of the OSI model. Yes, the famous OSI model! What does it mean? The routing decisions are made solely based on the info available

Interested in System Design? Subscribe to my newsletter for more detailed posts. https://t.co/zu2eLJcXfO

Layer 4 vs Layer 7 Load Balancers Simplified ✅ Layer 4 Load Balancer As the name suggests, Layer 4 load balancers operate in the transport layer of the OSI model. Yes, the famous OSI model! What does it mean? The routing decisions are made solely based on the info available

How do you scale a component? There are three points that I consider: ✅ Vertical Scaling vs Horizontal Scaling The easiest way to scale a component is vertical scaling. Think bigger RAM. A larger disk or CPU. It's cost-effective in the short term. Plus, you avoid dealing

Interested in System Design? Subscribe to my newsletter for more detailed posts on concepts and case studies. https://t.co/zu2eLJcXfO

How do you scale a component? There are three points that I consider: ✅ Vertical Scaling vs Horizontal Scaling The easiest way to scale a component is vertical scaling. Think bigger RAM. A larger disk or CPU. It's cost-effective in the short term. Plus, you avoid dealing

15 articles to help you get better at System Design: [1] 6 Strategies to Build Secure APIs https://t.co/fCn6KOIGRw [2] How HTTP 2 Improves Upon HTTP 1 https://t.co/kwVgozLx2a [3] How Netflix Uses Caching to Hold Attention? https://t.co/vmQetXtUix [4] 8 Must-Know Strategies to

15 articles to help you get better at System Design: [1] 6 Strategies to Build Secure APIs https://t.co/fCn6KOIGRw [2] How HTTP 2 Improves Upon HTTP 1 https://t.co/kwVgozLx2a [3] How Netflix Uses Caching to Hold Attention? https://t.co/vmQetXtUix [4] 8 Must-Know Strategies to

Interested in System Design? Subscribe to my newsletter for more detailed posts on concepts and case studies. https://t.co/zu2eLJcXfO

Load Balancer vs API Gateway vs Backend-For Frontend simplified. ✅ Load Balancer When you check in to a hotel, you are usually greeted by a receptionist. The receptionist checks your documents, enters your info into their system, and guides you to your room. If there are too

4 must-know Microservice Design Patterns: ✅ Database per service - In this pattern, each microservice manages its own data. - This means that no other service can access that data directly. - Communication or exchange of data can only happen through the owner service. -