Interview Tip

ABC rule, which doesn't mean "always be coding" but "always be chatting". 😅

#data_structures

Data structures and their use cases.

API architectural styles

#system_design

How to watch AlgoExpert videos?

1. Watch the problem description. Pause video. Try to understand the problem, inputs and outputs.
2. Solve by yourself similar problems in leetcode.
3. Watch AlgoExpert solution.

How to watch SystemsDesign videos?

1. Take notes
2. Understand why and how any concept is used
3. Use ChatGPT and Google to get answers to your questions

I have my own template for answering to System Design question. The most important thing in System Design is scalability. Will share later.

Microservices Architecture

Check the description of the components in comments

#system_design

Types of databases

#system_design

Caching. Where do we cache data?

#system_design

Part 1: System Design Checklist

1. Define the problem space
2. Design a system at a high level
3. Deep dive into the design
4. Identify bottlenecks and scaling opportunities
5. Building for Reliability in Distributed Systems

#system_design

Important HTTP Status Codes

#system_design

#system_design

🌐 𝐇𝐨𝐰 𝐭𝐨 𝐚𝐧𝐬𝐰𝐞𝐫 𝐢𝐧 𝐚 𝐒𝐲𝐬𝐭𝐞𝐦 𝐃𝐞𝐬𝐢𝐠𝐧 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰

1. For a Read-Heavy System - Consider using a Cache.
2. For a Write-Heavy System - Use Message Queues for async processing
3. For a Low Latency Requirement - Consider using a Cache and CDN.
4. Need 𝐀tomicity, 𝐂onsistency, 𝐈solation, 𝐃urability Compliant DB - Go for RDBMS/SQL Database.
5. Have unstructured data - Go for NoSQL Database.
6. Have Complex Data (Videos, Images, Files) - Go for Blob/Object storage.
7. Complex Pre-computation - Use Message Queue & Cache.
8. High-Volume Data Search - Consider search index, tries or search engine.
9. Scaling SQL Database - Implement Database Sharding.
10. High Availability, Performance, & Throughput - Use a Load Balancer.
11. Global Data Delivery - Consider using a CDN.
12. Graph Data (data with nodes, edges, and relationships) - Utilize Graph Database.
13. Scaling Various Components - Implement Horizontal Scaling.
14. High-Performing Database Queries - Use Database Indexes.
15. Bulk Job Processing - Consider Batch Processing & Message Queues.
16. Server Load Management & Preventing DOS Attacks- Use a Rate Limiter.
17. Microservices Architecture - Use an API Gateway.
18. For Single Point of Failure - Implement Redundancy.
19. For Fault-Tolerance and Durability - Implement Data Replication.
20. For User-to-User fast communication - Use Websockets.
21. Failure Detection in Distributed Systems - Implement a Heartbeat.
22. Data Integrity - Use Checksum Algorithm.
23. Efficient Server Scaling - Implement Consistent Hashing.
24. Decentralized Data Transfer - Consider Gossip Protocol.
25. Location-Based Functionality - Use Quadtree, Geohash, etc.
26. Avoid Specific Technology Names - Use generic terms.
27. High Availability and Consistency Trade-Off - Eventual Consistency.
28. For IP resolution & Domain Name Query - Mention DNS (Domain Name System).
29. Handling Large Data in Network Requests - Implement Pagination.
30. Cache Eviction Policy - Preferred is LRU (Least Recently Used) Cache.

#system_design

I have lots of things to share with you guys. Regarding System Design, Software Development and Testing, and much more.

So, wait for future news.
And as always, keep learning!

🥂

#advice

Only close people know that I had SWE role interview at Facebook. And Bloomberg interview this year. I went through 2 coding stages at Bloomberg and I needed to pass a systems design interview. But because I had my interviews very late in January, they closed the open positions. I hope this is not the end.

By the way, I go through all these interviews while in Uzbekistan. So, it is possible, to pass an interview at MAANG without leaving Uzbekistan.

So guys always be open to new opportunities!

#system_design

Top 6 most commonly used Server Types.

1. Web Server:
Hosts websites and delivers web content to clients over the internet

2. Mail Server:
Handles the sending, receiving, and routing of emails across networks

3. DNS Server:
Translates domain names (like bytebytego. com) into IP addresses, enabling users to access websites by their human-readable names.

4. Proxy Server:
An intermediary server that acts as a gateway between clients and other servers, providing additional security, performance optimization, and anonymity.

5. FTP Server:
Facilitates the transfer of files between clients and servers over a network

6. Origin Server:
Hosts central source of content that is cached and distributed to edge servers for faster delivery to end users.