The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Background jobs become risky when retrying them can repeat the business action.
In production SaaS systems, workers can crash, messages can be delivered again, APIs can timeout, and jobs can partially complete.
I design asynchronous workflows around idempotency, controlled retries, atomic state transitions, dead-letter handling, and observability, so recovery doesn’t create duplicate orders, payments, notifications, or integrations.
If asynchronous processing is becoming a reliability bottleneck as your product scales, this is the kind of backend architecture I enjoy working on.
#SaaS #BackendEngineering #SystemDesign #DistributedSystems #FullStack
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Challenges
View all
Related posts
Design it. Build it. Ship it. Repeat.
I'm a full-stack developer and designer who doesn't stop at the mockup — I take ideas from Figma to a live, working product. React front ends, Node/Python backends, and the brand identity to tie it all together.
Currently open to freelance web + design projects. Let's build something.
Nice
I’ve been building SabiFlow for a while, and honestly, the most interesting part of the project isn’t the code.
It's the problem.
Because it's personal.
I've experienced that thing where money comes in and somehow, without you really noticing, it starts disappearing.
Not because you don’t earn enough.
Not necessarily because you're irresponsible either.
Sometimes money simply has no job when it arrives.
And as an engineer, that got me thinking:
What if the problem isn't budgeting? What if the problem is that we’re asking people to make too many good decisions at the exact moment they have the most temptation to make bad ones?
That question became the foundation for SabiFlow.
Instead of telling someone, "You should save 20% of your income," I started thinking about what would happen if the system simply helped assign every inflow a purpose the moment it arrived.
That led me down a rabbit hole.
Funnels.
Automated distribution.
Wallet infrastructure.
Virtual accounts.
User behaviour.
Transaction flows.
KYC.
Compliance.
Even the psychology behind notifications.
And this is probably my favourite part of being both an engineer and a founder.
I don’t just ask:
"How do I build this feature?"
I ask:
"Why does this problem exist, and what kind of system could make dealing with it easier?"
Then the engineer in me comes along and asks:
"Okay… but how do we actually make this work reliably?" 😂
That tension between the founder thinking about the problem and the CTO thinking about the system is probably what I enjoy most about building SabiFlow.
I’m still figuring a lot of it out.
But I'm curious:
What’s a problem you’ve experienced personally that eventually made you want to build something around it?
The framing around “why does this problem exist?” is exactly the kind of product thinking that keeps a financial tool from becoming another dashboard. SabiFlow sounds strongest where the behavioral insight meets the practical system design—especially around notifications and reliable follow-through.
Potato Bazaar Founding Engineer
Built the platform from scratch as the Founding/Solo Engineer, connecting farmers, buyers, and traders through live market prices, listings, storage, transport, and market insights.
Developed the complete marketplace, dashboards, real-time data flows, and location-based market intelligence.
