We Deleted Tokio from Our Payment System and Cut Cloud Costs by $127,000
1–6 of 6 posts
Re: We Deleted Tokio from Our Payment System and Cut Cloud Costs by $127,000
#2Re: We Deleted Tokio from Our Payment System and Cut Cloud Costs by $127,000
#3The comments posted on the original article are not impressed.
Re: We Deleted Tokio from Our Payment System and Cut Cloud Costs by $127,000
#4> One database query took longer than expected. That blocked an async task. Which held up the executor.
This only happens if you're using blocking code in the event loop, right? This article seems like an admission of over-engineering from the get go.
Re: We Deleted Tokio from Our Payment System and Cut Cloud Costs by $127,000
#5The comments posted on the original article are not impressed.
Haha, ya that Medium account seems to post daily, I doubt it's a real professional engineer, seems like just an SEO medium account milking sub money.
Re: We Deleted Tokio from Our Payment System and Cut Cloud Costs by $127,000
#6The first thing I thought when I read this weird article was "wait...do they use their database synchronously in an asynchronous environment or am I missing something here?".
Most of us have been bitten by this naive mistake and I'm sure we have learned our lesson.