A backend practice that might crash your system.
33,065 次观看
19 条评论
评论来自 X (Twitter) 上的原帖

@thawhyte
Bro, just let your Db handle the unique constrain on create before debit.
6 个赞

@0xdefiprof
This is quite safe but can still easily be hacked 🥲.
2 个赞

@itsvalakov
Hmm
1 个赞

@folaoftech
🎥/tk: @tobio133
1 个赞

@Designerytg
This code sef isn’t safe enough
1 个赞

@Shettima349
skill issue , your database design should handle this !
1 个赞

@folaoftech
How
1 个赞

@StanleyMasinde_
Good stuff. I recently wrote something on the same. Let us talk about idempotency.
1 个赞

@megamindcodex
He didn't explain this well enough. But okay.
1 个赞

@busayo9ja
Fintech engineers, i greet una😂😂

@OderaPG
I nearly got wrecked by this. Thank God my user reported the bug on time.

@ElchapiD
Everything is pay pay pay pay pay can’t you guys ever code anything else ?

@ayindejo
More of that waiting for me tomorrow morning 🥺

@kennystonnne
I'd recommend 2-phase commit

@VencedorZest
🙏

@NickieNickiee
Let's connect

@Amospikins
Sharrrrppppp

@novhakaze
The principle of idempotency when dealing with payments or checkout: Your system must return the same result when given the same input. So here a payment exists just return 200 or 201. This useful for situations where a payment request is sent more than once.

@charleeotaru
This is not idempotency. You are simply returning everything response to the caller. That is not what idempotency is about.