Why do you write full object fetched from data source back to datasource after you modified one property? Shouldn't you mdify only field present in request?
It requires you to be familiar with Go and some basics of programming. If you're new to building web applications but know already Go and basics of programming then it's a good fit, otherwise check other videos on my channel to see if they're too complex.
Great video. You framed the problem really well. Thanks for sharing
Thank you for the sharing, looking forward for more concurrency in golang videos, appreciated!
Thank you! More to come definitely!
thank you for the video. can you make a video for GORM. thanks
Great thanks for sharing.
Thank you for the support as always 💪
Great video! This becomes a headache in production because it's almost impossible to reproduce
Indeed, thats why I made that small script to reproduce it myself. But ye it's nice to log when this happens to know how often it happens or not.
Why do you write full object fetched from data source back to datasource after you modified one property? Shouldn't you mdify only field present in request?
Nice content.. I'm curious, have you try query something like "select ... for update" ?
For fetching the post ?
@@TiagoTaquelim the idea is before execute update query, select the post with "for update". It will block others until the query commited.
@@arthben That will work but my goal was to avoid locking
I am completely new to backend, is your paid course for complete newbies, if not what should I learn first to be able to take the course?
It requires you to be familiar with Go and some basics of programming.
If you're new to building web applications but know already Go and basics of programming then it's a good fit, otherwise check other videos on my channel to see if they're too complex.
Which vs code theme you are using?
Gruvbox
Is this repo open source ?
Not yet, but it will be.