Sunday Prince 📟

Backend/Systems Engineer · Building systems in Go · Writing about how systems actually work

[Sunday Prince 📟 @sundayprincedev]

Just set this account up properly.

Backend/Systems Engineer. Building systems in Go from the ground up.

I write about how systems actually work — concurrency, error design, architecture — using analogies that make it click.

3 articles already live on Medium.
Follow Along!

[Sunday Prince 📟 @sundayprincedev]

@its_shreeja21 Like the notes

[Sunday Prince 📟 @sundayprincedev]

Project Update ‼️ The resolver path is DONE ✅

Following up on the core worker pool from my last post, I've just completed the resolver path for driving existing jobs to a terminal state safely using atomic transactions.

#fintech #golang #concurrency #ledger #BuildInPublic

[Sunday Prince 📟 @sundayprincedev]

@sadia82105 22hours

[Sunday Prince 📟 @sundayprincedev]

@NickpxJ Yes tbh

[Sunday Prince 📟 @sundayprincedev]

@thatorongirl03 Self Efficacy

[Sunday Prince 📟 @sundayprincedev]

@Shay_Slay_ The version of myself who knew a lot and refused to implement...

[Sunday Prince 📟 @sundayprincedev]

@mcancoskuncan Hopefully you can be mine

[Sunday Prince 📟 @sundayprincedev]

@niqudrift Community

[Sunday Prince 📟 @sundayprincedev]

@thecatzeus3 I catered for that window properly only ledger layer left...
In the worker block, there is panic isolation, which catches the exact state of the Stack when the worker/process failure happens, then the cordinator runs a check on job status using that jobID to see that work started

[Sunday Prince 📟 @sundayprincedev]

Update on the job worker: the core is mostly DONE ✅

Code is live at: https://t.co/m6j0yGw0sT

Feel free to check it out, and also leave questions. For more context check out my previous post, and how ive been on this as well
#golang #fintech #BuildInPublic

[Sunday Prince 📟 @sundayprincedev]

@mitansh_j07 Thank you!
Feel free to check out the repo

[Sunday Prince 📟 @sundayprincedev]

@Palak3312 Agree

[Sunday Prince 📟 @sundayprincedev]

@marieolivie Takes even more time than first job

[Sunday Prince 📟 @sundayprincedev]

@NanouuSymeon Mehn…aren’t we supposed to be?

[Sunday Prince 📟 @sundayprincedev]

@DmitryBBLV Of course!

[Sunday Prince 📟 @sundayprincedev]

Job worker skeleton live → https://t.co/m6j0yGw0sT
Built after conversations with @ahmedilgendy1 on atomic states, panic isolation, crash windows.
Today: https://t.co/tIg10NCQaj registry + two-path routing (fresh vs existing jobs)
More to come..
#golang #fintech #BuildInPublic

[Sunday Prince 📟 @sundayprincedev]

@danellisona I was consistent on here for just 2 days, and i saw reasons to keep it that way

[Sunday Prince 📟 @sundayprincedev]

@ahmedilgendy1 Thank you for this, tomorrow ill be officially launching the full project, and you can run this test properly.
I also have Panic/Crash isolation in place to make sure retry mechanism picks up that jobID and resolves to terminal state after verifying write met with ledger rules.

[Sunday Prince 📟 @sundayprincedev]

Todays Update: PANIC ISOLATION AND IDEMPOTENCY ⚠️

Tomorrow: full JOB_WORKER build. The concurrency skeleton for my marquee project—a DOUBLE-ENTRY LEDGER where every cent moved carries full proof.

#fintech #golang #concurrency #idempotency #PortHarcourt #BuildInPublic

[Sunday Prince 📟 @sundayprincedev]

@DmitryBBLV I just completed another layer today...
Tomorrow ill build the full Job worker with tests, push to git and you can test yourself too

[Sunday Prince 📟 @sundayprincedev]

SIGTERM HANDLING TODAY.
Especially how it relates to finance systems, keeping evidence of process termination.
more soon.
#buildinpublic