This is an interesting engineering experience I just had with a popular Nigerian savings platform.
I changed my withdrawal account. The normal withdrawal flow correctly showed my new account.
But when I tried to sell an asset, the platform showed my OLD withdrawal account.
My first thought: is this a database design problem, duplicated state, stale cache/read replica, or simply different business logic behind the two flows?
Either way, it raises an important question:
What is the single source of truth for a user’s withdrawal destination?
I asked ELITE operator and ex-CMO of MTN @adiaspeaks about the G.O.A.T moment in Nigerian tech that made her think anything was possible.
Adia: "My G.O.A.T moment is not a popular one. The first company that got called a unicorn is @InterswitchGRP. They got an investment from Visa that put their valuation at a billion dollars.
Nobody talks about Interswitch enough. I think it’s because their products don’t seem as sexy as we’ll expect, so the hype is different.
That’s a company we should give a lot more flowers."
100% agree with this!
@precious_tagy Before you comment make sure you have atleast read or experienced the challenges outline in this book: Mobile Apps at Scale: 39 Engineering Challenges (15 Apr) https://t.co/IbGAhGqG9B
I swear we didn't plan this, but just today, we finally NUKED our entire AWS account at the 37signals company meetup! This followed moving out compute+dbs in 2023, then S3 this summer, and now finally the entire account is GONE 🎉