Sistem Design

Question 1

For a Read-Heavy System — Consider using a Cache.

Answer 1

EG:
1.Redis (for REmote DIctionary Server)
- an open source, in-memory, NoSQL key/value store that is used primarily as an application cache or quick-response database.
2.Memcached is a distributed memory caching system designed for ease of use and simplicity and is well-suited as a cache or a session store.

Question 2

For a Write-Heavy System — Use Message Queues for async processing

Question 3

For a Low Latency Requirement — Consider using a Cache and CDN.

Question 4

FOR ACID (𝐀tomicity, 𝐂onsistency, 𝐈solation, 𝐃urability) Compliant DB — Go for RDBMS/SQL Database

Question 5

Have unstructured data — Go for NoSQL Database.

Question 6

Have Complex Data (Videos, Images, Files) — Go for Blob/Object storage.

Question 7

Complex Pre-computation — Use Message Queue & Cache.

Question 8

High-Volume Data Search — Consider search index, tries, or search engine.

Question 9

Scaling SQL Database — Implement Database Sharding.

Question 10

High Availability, Performance, & Throughput — Use a Load Balancer.

Question 11

Global Data Delivery — Consider using a CDN

Question 12

Graph Data (data with nodes, edges, and relationships) — Utilize Graph Database.

Question 13

High-Performing Database Queries — Use Database Indexes.

Question 14

Bulk Job Processing — Consider Batch Processing and Message Queues.

Question 15

Server Load Management & Preventing DOS Attacks- Use a Rate Limiter.

Question 16

Microservices Architecture — Use an API Gateway.

Question 17

For Single Point of Failure — Implement Redundancy.

Question 18

For Fault-Tolerance and Durability — Implement Data Replication

Question 19

For User-to-User fast communication — Use Websockets.

Question 20

Failure Detection in Distributed Systems — Implement a Heartbeat.

Question 21

Data Integrity — Use Checksum Algorithm.

Question 22

Efficient Server Scaling — Implement Consistent Hashing??

Question 23

Decentralized Data Transfer — Consider Gossip Protocol.???

Question 24

Location-Based Functionality — Use Quadtree, Geohash, etc.

Question 25

Avoid Specific Technology Names — Use generic terms.

Question 26

For IP resolution and domain Name Query — Mention DNS

Question 27

Handling Large Data in Network Requests — Implement Pagination.

Question 28

Cache Eviction Policy — Preferred is LRU (Least Recently Used) Cache

Question 29

To handle traffic spikes: Implement Autoscaling to manage resources dynamically

Question 30

Need analytics and audit trails — Consider using data lakes or append-only databases

Question 31

Handling Large-Scale Simultaneous Connections — Use Connection Pooling and consider using Protobuf to minimize data payload