Earlier quoted context omitted.
It's honestly weird Claude converges on this language because it's incredibly wordy and hard to parse. One would think semantic density would win out in training.
Who knows. I wish ant harshly penalized speaking litotically because it’s essentially reward hacking as it can often be read multiple ways. It’s also annoying as a human because Claude et al rate their own writing very highly, putting human LLM interactions at a disadvantage to human->LLM LLM interactions.
We replaced Redis with MySQL for inventory reservations and it scaled
101–110 of 281 posts
Re: We replaced Redis with MySQL for inventory reservations and it scaled
#102The lengths companies will go to avoid running different pieces of software...
Re: We replaced Redis with MySQL for inventory reservations and it scaled
#103"But the hardest lesson wasn't about database design. It was discovering that the real bottleneck wasn’t what we were observing and measuring."
It's honestly weird Claude converges on this language because it's incredibly wordy and hard to parse. One would think semantic density would win out in training.
Re: We replaced Redis with MySQL for inventory reservations and it scaled
#104Earlier quoted context omitted.
that's why I mentioned active carts in my post, there are ways to define active cart to get rid of abandoned carts ( ignore carts where last user action was > N seconds ago). Ok, let's accept the design goal that whoever paid first wins. You can use the same metric (how many milliseconds ago did user click PAY) and impose a global monotonic non-decreasing counter to distribute the scarce inventory. This is how order…
Most payment methods in the world don't support separate authorization and capture.
Re: We replaced Redis with MySQL for inventory reservations and it scaled
#105Earlier quoted context omitted.
that's why I mentioned active carts in my post, there are ways to define active cart to get rid of abandoned carts ( ignore carts where last user action was > N seconds ago). Ok, let's accept the design goal that whoever paid first wins. You can use the same metric (how many milliseconds ago did user click PAY) and impose a global monotonic non-decreasing counter to distribute the scarce inventory. This is how order…
Most payment methods in the world don't support separate authorization and capture.
https://docs.stripe.com/payments/place-a-hold-on-a-payment-m...
https://support.authorize.net/knowledgebase/Knowledgearticle...
Re: We replaced Redis with MySQL for inventory reservations and it scaled
#106Re: We replaced Redis with MySQL for inventory reservations and it scaled
#107The lengths companies will go to avoid running different pieces of software...
Re: We replaced Redis with MySQL for inventory reservations and it scaled
#108This section is badly written. For example, it refers to different table names than those previously introduced.
The slop shows. While I appreciate the post, I wonder why they didn't bother using an LLM in a way that would at least ensure internal consistency.
Re: We replaced Redis with MySQL for inventory reservations and it scaled
#109not the best design to have 1000 rows for each shop*SKU combination. If a candidate proposed this solution during Shopify's System Design interview, i doubt he would be vetted for Senior+ position. Instead of having 1000 rows per shop*SKU, why not just have one row per shopping cart*SKU? That way a single row would represent a single cart, and will hold info of multiple items of the same SKU. No need a cludge with 10…
Re: We replaced Redis with MySQL for inventory reservations and it scaled
#110The lengths companies will go to avoid running different pieces of software...