Saurabh Dashora (@progressivecod2) 's Twitter Profile
Saurabh Dashora

@progressivecod2

Writing the System Design Codex Newsletter • I simplify software design with concepts and case studies

ID: 1090810652061356037

linkhttps://newsletter.systemdesigncodex.com calendar_today31-01-2019 03:15:00

16,16K Tweet

17,17K Takipçi

308 Takip Edilen

Saurabh Dashora (@progressivecod2) 's Twitter Profile Photo

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. -

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. 

-
Saurabh Dashora (@progressivecod2) 's Twitter Profile Photo

15 articles to help you get better at System Design: [1] 6 Strategies to Build Secure APIs newsletter.systemdesigncodex.com/p/6-strategies… [2] How HTTP 2 Improves Upon HTTP 1 newsletter.systemdesigncodex.com/p/how-http-2-i… [3] How Netflix Uses Caching to Hold Attention? newsletter.systemdesigncodex.com/p/how-netflix-… [4] 8 Must-Know Strategies to

15 articles to help you get better at System Design:

[1] 6 Strategies to Build Secure APIs
newsletter.systemdesigncodex.com/p/6-strategies…

[2] How HTTP 2 Improves Upon HTTP 1
newsletter.systemdesigncodex.com/p/how-http-2-i…

[3] How Netflix Uses Caching to Hold Attention?
newsletter.systemdesigncodex.com/p/how-netflix-…

[4] 8 Must-Know Strategies to
Saurabh Dashora (@progressivecod2) 's Twitter Profile Photo

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

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
Saurabh Dashora (@progressivecod2) 's Twitter Profile Photo

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

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
Saurabh Dashora (@progressivecod2) 's Twitter Profile Photo

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

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
Saurabh Dashora (@progressivecod2) 's Twitter Profile Photo

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

Saurabh Dashora (@progressivecod2) 's Twitter Profile Photo

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

Saurabh Dashora (@progressivecod2) 's Twitter Profile Photo

15 articles to help you get better at System Design: [1] 4 Challenges of Distributed Systems - And Possible Solutions newsletter.systemdesigncodex.com/p/4-challenges… [2] Your Code is Fast, But Your Database is Slow—Now What? newsletter.systemdesigncodex.com/p/your-code-is… [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
newsletter.systemdesigncodex.com/p/4-challenges…

[2] Your Code is Fast, But Your Database is Slow—Now What?
newsletter.systemdesigncodex.com/p/your-code-is…

[3] 15 Must-Know Elements of System Design