#30daysofsystemdesign Suchergebnisse

Day 7 of #30DaysOfSystemDesign 👨‍💻 📃Learned about Load Balancing, and how it ensuring optimal performance and prevents overload 💡 📃Key benefits: ⚖️ Scalability - Handle increased traffic smoothly 💪 Redundancy - Minimize downtime with failover capabilities 🔄

theAakashOjha's tweet image. Day 7 of #30DaysOfSystemDesign 👨‍💻

📃Learned about Load Balancing, and how it ensuring optimal performance and prevents overload 💡
📃Key benefits: 
⚖️ Scalability - Handle increased traffic smoothly 
💪 Redundancy - Minimize downtime with failover capabilities 🔄

Taking up a new tech challenge and calling it #30DaysOfSystemDesign Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design #Day0 Basics of Low level Design

znn57833953's tweet image. Taking up a new tech challenge and calling it #30DaysOfSystemDesign
Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design

#Day0

Basics of Low level Design
znn57833953's tweet image. Taking up a new tech challenge and calling it #30DaysOfSystemDesign
Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design

#Day0

Basics of Low level Design
znn57833953's tweet image. Taking up a new tech challenge and calling it #30DaysOfSystemDesign
Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design

#Day0

Basics of Low level Design
znn57833953's tweet image. Taking up a new tech challenge and calling it #30DaysOfSystemDesign
Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design

#Day0

Basics of Low level Design

🚀 Day 1/30 of #30DaysOfSystemDesign! Today we explore Client-Server Architecture. Think of it like ordering pizza: You (the client) order a pizza. The pizza place (the server) makes it. The delivery driver (the network) brings it to you. #SystemDesign #Tech

JitenMohantyDev's tweet image. 🚀 Day 1/30 of #30DaysOfSystemDesign! Today we explore Client-Server Architecture.

Think of it like ordering pizza:

You (the client) order a pizza.

The pizza place (the server) makes it.

The delivery driver (the network) brings it to you.

 #SystemDesign #Tech

#Day2 Meeting Scheduler Side Note : I'm really struggling to break a problem statement into a class Diagram as in 1st screenshot...I think I have to practice more problems before I develop intuition for it github : github.com/jubinsoni/30Da… #30DaysOfSystemDesign

znn57833953's tweet image. #Day2 

Meeting Scheduler 

Side Note : I'm really struggling to break a problem statement into a class Diagram as in 1st screenshot...I think I have to practice more problems before I develop intuition for it

github : github.com/jubinsoni/30Da…

#30DaysOfSystemDesign
znn57833953's tweet image. #Day2 

Meeting Scheduler 

Side Note : I'm really struggling to break a problem statement into a class Diagram as in 1st screenshot...I think I have to practice more problems before I develop intuition for it

github : github.com/jubinsoni/30Da…

#30DaysOfSystemDesign
znn57833953's tweet image. #Day2 

Meeting Scheduler 

Side Note : I'm really struggling to break a problem statement into a class Diagram as in 1st screenshot...I think I have to practice more problems before I develop intuition for it

github : github.com/jubinsoni/30Da…

#30DaysOfSystemDesign

Day 2 of #30DaysOfSystemDesign 👨‍💻 📃Explored HTTP/HTTPS protocols & their real-world applications. 📃delved into TCP/IP layers - Physical, Data Link, Network, Transport, App. #NetworkingBasics

theAakashOjha's tweet image. Day 2 of #30DaysOfSystemDesign 👨‍💻

📃Explored HTTP/HTTPS protocols & their real-world applications. 

📃delved into TCP/IP layers - Physical, Data Link, Network, Transport, App.  

#NetworkingBasics

Day 8 of #30DaysOfSystemDesign Consistent hashing & Sharding🛠️ 1️⃣ Scalability: Distribute data across nodes efficiently, no single point of failure📊 2️⃣ Load Balancing: Optimize performance, balance workload evenly🔄 3️⃣Fault Tolerance: Spread data, minimize impact of failures🛡️

theAakashOjha's tweet image. Day 8 of #30DaysOfSystemDesign

 Consistent hashing & Sharding🛠️
1️⃣ Scalability: Distribute data across nodes efficiently, no single point of failure📊
2️⃣ Load Balancing: Optimize performance, balance workload evenly🔄
3️⃣Fault Tolerance: Spread data, minimize impact of failures🛡️

Day 9 of #30DaysOfSystemDesign 🛠️ Bloom Filters & Data Replication: 1️⃣Efficiently check set membership, save space, reduce false positives 🔍 2️⃣Enhance availability, fault tolerance by storing data copies across nodes 🔄 3️⃣reduce latency, ensure data integrity in DS💡

theAakashOjha's tweet image. Day 9 of #30DaysOfSystemDesign 🛠️

Bloom Filters & Data Replication:

1️⃣Efficiently check set membership, save space, reduce false positives 🔍 
2️⃣Enhance availability, fault tolerance by storing data copies across nodes 🔄 
3️⃣reduce latency, ensure data integrity in DS💡

Committing to Round2 #100DaysOfCode where I'll try to solve a single leetcode problem per day and post the solution Along with this I'll do passively #30DaysOfSystemDesign and Japanese learning


Day 3/30: System Design Dived into Databases today ->Horizontal vs Vertical Scaling ->Normalization (1NF, 2NF, 3NF) ->Table Replicas ->Caching ->Indexing ->Database Sharding #30DaysOfSystemDesign #DevOps #Backend #Cloud


Day 5 of #30DaysOfSystemDesign 👨‍💻 📃 about caching and how it is used to make architecture efficient. 📃 learned about hit ratio, cache memory 📃 Locality of reference- Spatial and temporary 📃 learned that Caches are stored in Cache lines which has same number of bytes in it.


Day 2️⃣ of #30DaysOfSystemDesign Imp phase of #systemdesign - Requirement Gathering/Analysis 👉 Functional Reqs 👉 Non-Functional Reqs Find answer of 👇 ⚡What system should be able to do/not do? ⚡System will be highly consistent/available/scalable/latency? ⚡ Cost limitation?


Starting today with #30DaysOfSystemDesign to revise the system design concepts and be practicing a good number of problems to get a better hand at it. #100DaysOfCode #CODEVEIN #DEVCommunity #SystemDesign


Day1 of #30DaysOfSystemDesign Started Basics: - Learned what is System Design, how it benefits the architecture of any new application. - Learned some basics like about Vertical Scaling, Horizontal Scaling - A vital part of System Design i. e. Capacity Estimation and Planning


Day 1️⃣ of #30DaysOfSystemDesign Starting this day with sharing few facts we need to know about #systemdesign interview and in general as well ⚡ Desiging scalable systems is the basis of system design ⚡ System that is designed is always ever evolving Read on 🧵


I'll be starting with #30DaysofSystemDesign challenge from today.. Going to share whatever the topic I'm going through... 👨‍💻 Let's do this 💪


Day3 of #30DaysOfSystemDesign 👨‍💻 📃 Relational Databases, it's use cases and cons. 📃 Gone through with the basics of Indexing in DB 📃 How NoSQL Databases are beneficial for certain system architectures and why they are getting adopted #database


Revised the concepts of SOLID principles today Single Responsibility Principle (SRP) Open/Closed Principle (OCP) Liskov Substitution Principle (LSP) Interface Segregation Principle (ISP) Dependency Inversion Principle (DIP) #30daysOfSystemDesign #100DaysOfCode


Day 3/30: System Design Dived into Databases today ->Horizontal vs Vertical Scaling ->Normalization (1NF, 2NF, 3NF) ->Table Replicas ->Caching ->Indexing ->Database Sharding #30DaysOfSystemDesign #DevOps #Backend #Cloud


🚀 Day 1/30 of #30DaysOfSystemDesign! Today we explore Client-Server Architecture. Think of it like ordering pizza: You (the client) order a pizza. The pizza place (the server) makes it. The delivery driver (the network) brings it to you. #SystemDesign #Tech

JitenMohantyDev's tweet image. 🚀 Day 1/30 of #30DaysOfSystemDesign! Today we explore Client-Server Architecture.

Think of it like ordering pizza:

You (the client) order a pizza.

The pizza place (the server) makes it.

The delivery driver (the network) brings it to you.

 #SystemDesign #Tech

Day 10 of #30DaysOfSystemDesign 👨‍💻 Topic Location based databases and Data Migration 📃Location data targets marketing, while data migration secures seamless transfers. 📃 Data migration ensures smooth transfer, preserving data integrity.


Day 9 of #30DaysOfSystemDesign 🛠️ Bloom Filters & Data Replication: 1️⃣Efficiently check set membership, save space, reduce false positives 🔍 2️⃣Enhance availability, fault tolerance by storing data copies across nodes 🔄 3️⃣reduce latency, ensure data integrity in DS💡

theAakashOjha's tweet image. Day 9 of #30DaysOfSystemDesign 🛠️

Bloom Filters & Data Replication:

1️⃣Efficiently check set membership, save space, reduce false positives 🔍 
2️⃣Enhance availability, fault tolerance by storing data copies across nodes 🔄 
3️⃣reduce latency, ensure data integrity in DS💡

Day 8 of #30DaysOfSystemDesign Consistent hashing & Sharding🛠️ 1️⃣ Scalability: Distribute data across nodes efficiently, no single point of failure📊 2️⃣ Load Balancing: Optimize performance, balance workload evenly🔄 3️⃣Fault Tolerance: Spread data, minimize impact of failures🛡️

theAakashOjha's tweet image. Day 8 of #30DaysOfSystemDesign

 Consistent hashing & Sharding🛠️
1️⃣ Scalability: Distribute data across nodes efficiently, no single point of failure📊
2️⃣ Load Balancing: Optimize performance, balance workload evenly🔄
3️⃣Fault Tolerance: Spread data, minimize impact of failures🛡️

Day 7 of #30DaysOfSystemDesign 👨‍💻 📃Learned about Load Balancing, and how it ensuring optimal performance and prevents overload 💡 📃Key benefits: ⚖️ Scalability - Handle increased traffic smoothly 💪 Redundancy - Minimize downtime with failover capabilities 🔄

theAakashOjha's tweet image. Day 7 of #30DaysOfSystemDesign 👨‍💻

📃Learned about Load Balancing, and how it ensuring optimal performance and prevents overload 💡
📃Key benefits: 
⚖️ Scalability - Handle increased traffic smoothly 
💪 Redundancy - Minimize downtime with failover capabilities 🔄

Till now in System Design, I have covered all Basic/Pre requisites for it, completed the Load Balancing topic. Acing to learn more topics and complete #30DaysOfSystemDesign Challenge 💪


Day 6 of #30DaysOfSystemDesign 👨‍💻 - Learned about Thrashing - how Multiprogramming takes place and when Thrashing occurs and how to tackle thrashing. - Learned about Threads, Processes and how multi threading helps to execute a program faster. #Multiprogramming #OS


Day 5 of #30DaysOfSystemDesign 👨‍💻 📃 about caching and how it is used to make architecture efficient. 📃 learned about hit ratio, cache memory 📃 Locality of reference- Spatial and temporary 📃 learned that Caches are stored in Cache lines which has same number of bytes in it.


Day 4 of #30DaysOfSystemDesign Continuing database basics 📃 Understanding the role of data modeling in designing efficient database schemas. 📃 Examining the trade-offs between consistency, availability, and partition tolerance in distributed database systems.


Day3 of #30DaysOfSystemDesign 👨‍💻 📃 Relational Databases, it's use cases and cons. 📃 Gone through with the basics of Indexing in DB 📃 How NoSQL Databases are beneficial for certain system architectures and why they are getting adopted #database


Day 2 of #30DaysOfSystemDesign 👨‍💻 📃Explored HTTP/HTTPS protocols & their real-world applications. 📃delved into TCP/IP layers - Physical, Data Link, Network, Transport, App. #NetworkingBasics

theAakashOjha's tweet image. Day 2 of #30DaysOfSystemDesign 👨‍💻

📃Explored HTTP/HTTPS protocols & their real-world applications. 

📃delved into TCP/IP layers - Physical, Data Link, Network, Transport, App.  

#NetworkingBasics

Day1 of #30DaysOfSystemDesign Started Basics: - Learned what is System Design, how it benefits the architecture of any new application. - Learned some basics like about Vertical Scaling, Horizontal Scaling - A vital part of System Design i. e. Capacity Estimation and Planning


I'll be starting with #30DaysofSystemDesign challenge from today.. Going to share whatever the topic I'm going through... 👨‍💻 Let's do this 💪


Starting today with #30DaysOfSystemDesign to revise the system design concepts and be practicing a good number of problems to get a better hand at it. #100DaysOfCode #CODEVEIN #DEVCommunity #SystemDesign


Follow #30DaysOfSystemDesign. This might also help for interview preperafion

Day 2️⃣ of #30DaysOfSystemDesign Imp phase of #systemdesign - Requirement Gathering/Analysis 👉 Functional Reqs 👉 Non-Functional Reqs Find answer of 👇 ⚡What system should be able to do/not do? ⚡System will be highly consistent/available/scalable/latency? ⚡ Cost limitation?



Keine Ergebnisse für "#30daysofsystemdesign"

Day 7 of #30DaysOfSystemDesign 👨‍💻 📃Learned about Load Balancing, and how it ensuring optimal performance and prevents overload 💡 📃Key benefits: ⚖️ Scalability - Handle increased traffic smoothly 💪 Redundancy - Minimize downtime with failover capabilities 🔄

theAakashOjha's tweet image. Day 7 of #30DaysOfSystemDesign 👨‍💻

📃Learned about Load Balancing, and how it ensuring optimal performance and prevents overload 💡
📃Key benefits: 
⚖️ Scalability - Handle increased traffic smoothly 
💪 Redundancy - Minimize downtime with failover capabilities 🔄

🚀 Day 1/30 of #30DaysOfSystemDesign! Today we explore Client-Server Architecture. Think of it like ordering pizza: You (the client) order a pizza. The pizza place (the server) makes it. The delivery driver (the network) brings it to you. #SystemDesign #Tech

JitenMohantyDev's tweet image. 🚀 Day 1/30 of #30DaysOfSystemDesign! Today we explore Client-Server Architecture.

Think of it like ordering pizza:

You (the client) order a pizza.

The pizza place (the server) makes it.

The delivery driver (the network) brings it to you.

 #SystemDesign #Tech

Day 2 of #30DaysOfSystemDesign 👨‍💻 📃Explored HTTP/HTTPS protocols & their real-world applications. 📃delved into TCP/IP layers - Physical, Data Link, Network, Transport, App. #NetworkingBasics

theAakashOjha's tweet image. Day 2 of #30DaysOfSystemDesign 👨‍💻

📃Explored HTTP/HTTPS protocols & their real-world applications. 

📃delved into TCP/IP layers - Physical, Data Link, Network, Transport, App.  

#NetworkingBasics

Taking up a new tech challenge and calling it #30DaysOfSystemDesign Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design #Day0 Basics of Low level Design

znn57833953's tweet image. Taking up a new tech challenge and calling it #30DaysOfSystemDesign
Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design

#Day0

Basics of Low level Design
znn57833953's tweet image. Taking up a new tech challenge and calling it #30DaysOfSystemDesign
Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design

#Day0

Basics of Low level Design
znn57833953's tweet image. Taking up a new tech challenge and calling it #30DaysOfSystemDesign
Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design

#Day0

Basics of Low level Design
znn57833953's tweet image. Taking up a new tech challenge and calling it #30DaysOfSystemDesign
Here I'll try to summarise some basics of system design concepts and some sample problems which will give an understanding of both low-level and High level Design

#Day0

Basics of Low level Design

#Day2 Meeting Scheduler Side Note : I'm really struggling to break a problem statement into a class Diagram as in 1st screenshot...I think I have to practice more problems before I develop intuition for it github : github.com/jubinsoni/30Da… #30DaysOfSystemDesign

znn57833953's tweet image. #Day2 

Meeting Scheduler 

Side Note : I'm really struggling to break a problem statement into a class Diagram as in 1st screenshot...I think I have to practice more problems before I develop intuition for it

github : github.com/jubinsoni/30Da…

#30DaysOfSystemDesign
znn57833953's tweet image. #Day2 

Meeting Scheduler 

Side Note : I'm really struggling to break a problem statement into a class Diagram as in 1st screenshot...I think I have to practice more problems before I develop intuition for it

github : github.com/jubinsoni/30Da…

#30DaysOfSystemDesign
znn57833953's tweet image. #Day2 

Meeting Scheduler 

Side Note : I'm really struggling to break a problem statement into a class Diagram as in 1st screenshot...I think I have to practice more problems before I develop intuition for it

github : github.com/jubinsoni/30Da…

#30DaysOfSystemDesign

Day 8 of #30DaysOfSystemDesign Consistent hashing & Sharding🛠️ 1️⃣ Scalability: Distribute data across nodes efficiently, no single point of failure📊 2️⃣ Load Balancing: Optimize performance, balance workload evenly🔄 3️⃣Fault Tolerance: Spread data, minimize impact of failures🛡️

theAakashOjha's tweet image. Day 8 of #30DaysOfSystemDesign

 Consistent hashing & Sharding🛠️
1️⃣ Scalability: Distribute data across nodes efficiently, no single point of failure📊
2️⃣ Load Balancing: Optimize performance, balance workload evenly🔄
3️⃣Fault Tolerance: Spread data, minimize impact of failures🛡️

Day 9 of #30DaysOfSystemDesign 🛠️ Bloom Filters & Data Replication: 1️⃣Efficiently check set membership, save space, reduce false positives 🔍 2️⃣Enhance availability, fault tolerance by storing data copies across nodes 🔄 3️⃣reduce latency, ensure data integrity in DS💡

theAakashOjha's tweet image. Day 9 of #30DaysOfSystemDesign 🛠️

Bloom Filters & Data Replication:

1️⃣Efficiently check set membership, save space, reduce false positives 🔍 
2️⃣Enhance availability, fault tolerance by storing data copies across nodes 🔄 
3️⃣reduce latency, ensure data integrity in DS💡

Loading...

Something went wrong.


Something went wrong.


United States Trends