fairy tales are more than true:not because they tell us dragons exist,but bcos de tell us dat dragons can be beaten - G.K Chesterton
Building @versitybook 📖
Starting in February I'm going to start a (free) new live coding series where I build a handful of these apps with a recent college graduate that works with me.
I think it will be a great tutorial for people who want to learn aspects of engineering you don't get in school. #staytuned
Pelumi’s e-commerce backend was handling 200 users comfortably.
Then they ran a promo.
800 users hit the platform in 45 minutes.
The server didn’t crash because of traffic.
It crashed because of one line of code that had been sitting in the codebase since day one
Brought out clothes to wash, told myself "let me check my phone quick", 1 hour later, the clothes still here untouched! My discipline level has fallen by 90% and I feel awful man!
Ji! Imọlẹ ji!
@Akintola_steve I appreciate this, if you would do a post on idempotency as well, it would be nice. Either as a follow up to this or a standalone thread.
A developer was building a job application platform.
Simple idea.
Candidate submits application. The company receives it.
But one small architectural mistake quietly turned the system into a disaster under real traffic.
This thread covers:
• Synchronous vs asynchronous systems
• What message queues actually do
• Producers, consumers, ACKs
• Retries and duplicate processing
• At-least-once delivery
• Worker crashes
• Why users spam-click buttons
�� How queues protect UX and infrastructure
Carefully read through this.
By the end, you’ll understand why most scalable systems eventually introduce queues.
I’m looking for people who are ready to lock in with zero distractions for the next 3 months.
Let’s commit to this roadmap and actually follow through.
Forget the AI noise for now. Focus on becoming solid in backend engineering and system design.
It might sound unrealistic, but you’ll be surprised at how much you grow by the end of June / early July.
Read below 👇🏿
@Akintola_steve Thanks for this.
Now that a load balancer has been introduced to a system. Won't the problem still persist since there's only one load balancer facing these thousands of requests.. or will there be multiple load balancers to avoid a single point of failure?