RKB (@rkbdevir7) header
RKB (@rkbdevir7) profile picture

22 • full-stack developer • learning Go

India
Joined April 2024
Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)Photo by RKB (@rkbdevir7)
hey @grok what's the most liked tweet of all time?
1
53
What programming language is this?
32
WTF is happening with my YouTube. Why can't I scroll down
13
why the hell is auto-scroll still not available on Instagram for iPad, @instagram ? 😭 it's 2026. how am i still manually scrolling reels?
1
4
153
Today I learned about database Connection Pooling. Instead of opening and closing a database connection for every request, we maintain a pool of reusable connections. Also learned why managing these pools becomes important when an application runs multiple backend instances.
6
2
67
↳ We can configure smaller pools or use tools like PgBouncer to manage database connections more efficiently. Connection pooling isn't about unlimited connections. It's about reusing and managing a limited number of them.
5
↳ Each backend instance can have its own connection pool. For example, 4 instances with 30 connections each can create 120 potential connections, even if the database allows only 100.
6
↳ What happens when all connections are occupied? New requests have to wait until a connection becomes available. If they wait too long, they can time out.
10
↳ A request borrows an available connection, executes its database query, and returns the connection to the pool. Another request can then reuse that same connection instead of creating a new one.
16
F1 fans really wake up at 5 AM to watch 20 rich guys drive in circles and call it the greatest sport ever invented 💀
the f1 film could never
27
Learning System Design: Spent some time learning about ACID today. The bank transfer example actually helped me understand why these properties matter. A simple transfer involves more than just moving money from one account to another. Here are the 4 things I learned 👇
4
2
185
Durability = Committed changes survive. Once a transaction is successfully committed, its changes should remain saved even if the database server crashes and restarts.
6
Isolation = Transactions shouldn't interfere improperly. Imagine two people transferring money from the same account simultaneously. The database must coordinate these transactions to prevent incorrect results.
10
Consistency = Database rules remain valid. For example, if an account isn't allowed to have a negative balance, a transaction that violates this rule must be rejected.
12
Atomicity = All or Nothing. When transferring ₹500, the database must either deduct it from Account A AND add it to Account B, or undo the entire transaction if something fails.
19
Learning System Design Things I learned: ↳ API Gateway: Routes API requests and handles auth. ↳ Load Balancer: Distributes traffic across instances. ↳ Reverse Proxy: Forwards requests to backend servers. Code and implementation next! 🚀
Learning System Design: Today I learned how sharding uses horizontal partitioning to distribute rows across database nodes using a shard key. Poor key distribution creates hot shards, while cross-shard queries can require expensive scatter-gather operations. More to learn 🚀
3
1
44
A Reverse Proxy sits between clients and backend servers. It forwards requests on their behalf and can also handle caching, SSL termination, and compression.
8
A Load Balancer distributes incoming requests across multiple instances of the same service. It can also perform health checks and stop sending traffic to unhealthy instances.
4
An API Gateway acts as a single-entry point for clients. It can handle authentication, rate limiting, request validation, and routing to backend services.
15