After weeks of building, testing, fixing bugs,
Qademy is finally LIVE on the App Store & Google Play 🎉
Built for students to access department updates, course materials, timetables, announcements, and more all in one place.
This is the beginning 🚀
Built with @thisisperryy🤝
A good dev writes clean code.
A great dev understands what runs between the code and the database — and designs for it.
System design isn't advanced knowledge. It's foundational.
Please RT if this helped so share the knowledge 🙏 Happy Sunday!
Building websites isn't just about writing code or letting an AI write it for you to speed up delivery.
The real skill is knowing what happens when you push your code to production.
Here is a thread on something most tutorials skip 🧵
These aren't edge cases.
They're production bugs wearing the costume of infrastructure issues or bad luck.
The fix isn't more code. It's correct system design from the start.
Starvation
High-priority traffic (bulk product reads) hogs the connection pool.
Lower-priority ops like sending a verification email - never get their turn.
Your user never gets their OTP. You never know why.
Live-lock
Both operations keep reacting to each other.
They're "running" but making zero actual progress.
Worse than a crash because it's harder to diagnose.
It gets dangerous.
When transaction pooler and session pooler traffic compete on the same DB without proper management, you get classic CS concurrency problems.
Most devs don't know these by name. They just call it a "slow day." 👇
Here's a real-world way to think about it.
Imagine Jumia:
- Millions of users browse products → transaction pooler (fast, stateless reads)
- Sellers verify accounts, get emails, update profiles → session pooler (persistent sessions)
Both hit the same database.
These 3 options exists for a reason:
Direct connection → local dev & migrations
Transaction pooler → production reads (users fetching posts - short, stateless)
Session pooler → persistent ops (auth, emails, verifications)
Picking wrong silently breaks things.
I recently added a blog system, admin dashboard & partnership portal to a company site backed by Supabase (PostgreSQL).
Everything worked locally. Then came the question nobody warns you about:
How do you connect your DB correctly across environments?
@Kadotttt@mathjuma Well, Given the problem specifications in your case, The passed requirements are
An Encryption and Handshake (very necessary)
UDP or TCP communication protocols
Stealth/obfuscation features
DNS leak protection.
Kill switch.
@Kadotttt@mathjuma When you purchase a data plan, you use their public Ip for internet access, which makes them able to see the requests you sent to different sites.
The only solution is to either use a proxy or a strong VPN that encrypts all your communications.