Live data from Hacker News

We replaced Redis with MySQL for inventory reservations and it scaled

shopify.engineering

181–190 of 281 posts

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#181
post #14

Earlier quoted context omitted.

Are you implying that vaping is far right?

Sounded to me like they were saying people vape in the office, which would make a bad work environment on top of the far right bros.

> people vape in the office

It's famously a fully remote company.

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#182

I wonder how we could handle that in a simpler way with durable workflows (e.g. Temporal, Restante, DBOS) – which are similar to Erlang processes but with persistent disk storage. This could avoid the need to maintain the 1000 row inventory. Perhaps each shopping cart would have its own workflow, and the inventory item would have one as well. Then, whenever a customer put an item in their cart, their cart workflow wo…

Durable workflows are different, not necessarily simpler, imo. Unless the team is already familiar with them, I wouldn’t introduce one just for this. You also have to account for the infrastructure needed to run and manage the durable workflow itself, which adds complexity.

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#183
post #159

Why even have a blog when you can't be arsed to write the posts. This is so obviously LLM-written. I have a positive view of Shopify engineers, but this kind of made a dent in that confidence.

What exactly makes it "obvious" that this is written by AI? I could totally believe that AI was used to generate parts of it, but I really don't get the sense that the whole thing was written that way. I've seen way worse examples on this site. As software engineers we are constantly told that we need to heavily use these tools for our daily work. So is it surprising that software engineers use the same tools as writ…

The pictures.

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#184
post #159

Why even have a blog when you can't be arsed to write the posts. This is so obviously LLM-written. I have a positive view of Shopify engineers, but this kind of made a dent in that confidence.

What exactly makes it "obvious" that this is written by AI? I could totally believe that AI was used to generate parts of it, but I really don't get the sense that the whole thing was written that way. I've seen way worse examples on this site. As software engineers we are constantly told that we need to heavily use these tools for our daily work. So is it surprising that software engineers use the same tools as writ…

There are some claudeisms here (it's not x, it's y) but it does read like they did at least one human pass on it. Or maybe this is opus 5 writing which is a bit less distinct idk. It doesn't feel as obviously generated slop as some of the stuff posted here with every other sentence a fragment and load bearing and all that nonsense

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#186

Earlier quoted context omitted.

Because the post is just rambling without a clear intent or direction. Why do you need "oversell protection" if you have "transactions". Isn't the whole point of a "transaction" that it handles concurrency and disk failures?

I work with Shopify often and the whole oversell protection thing is like a huge joke. Oversell happens because Shopify doesn't decrement inventory until payment is confirmed. And they apparently would rather die than change that invariant.

It's funny the organizational rules that get written into a company's DNA.

I could see a historical moment where Shopify, sans that invariant, massively fucked up inventory counts from uncompleted transactions... then had to unwind all that when a bunch failed to clear payment.

Ergo, now there's an invariant.

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#187

Earlier quoted context omitted.

Flash sales are a huge scaling issue for Shopify. There are celebrities who want to sell thousands of items in a few minutes window at the end of an advertised countdown. Basically this is an incredibly rare case but a feature that they want to support.

There were woot offs 20 years ago. Flash sales are not some new scaling issue.

Its also not a solved one considering basically no platforms support them.

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#188

Why even have a blog when you can't be arsed to write the posts. This is so obviously LLM-written. I have a positive view of Shopify engineers, but this kind of made a dent in that confidence.

I just wanted to drop a note that I almost never go into an article or blog wondering if its AI or not. I am trying to be a more picky reader and try to actually do something occasionally but I do browse database articles and this is a good one. So I wonder, am I becoming insensitive about AI writing? Am I being hypnotized into taking whatever color pill thats had a color representing a surrender to the AI "hive mind…

> whatever color pill thats had a color representing a surrender to the AI "hive mind"

Obviously the blue pill.

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#189
post #159

Why even have a blog when you can't be arsed to write the posts. This is so obviously LLM-written. I have a positive view of Shopify engineers, but this kind of made a dent in that confidence.

What exactly makes it "obvious" that this is written by AI? I could totally believe that AI was used to generate parts of it, but I really don't get the sense that the whole thing was written that way. I've seen way worse examples on this site. As software engineers we are constantly told that we need to heavily use these tools for our daily work. So is it surprising that software engineers use the same tools as writ…

Well, one thing to remember: AI learned from us (See what I did, there?).

The training these LLMs got, was from endless human-slop, on sites like LinkedIn, and marketing copy, everywhere. In fact, don't be surprised, if we start learning from AI; reversing the process.

But I think that it's only a matter of time, before almost everything will be at least touched by AI.

I posted this, yesterday[0]. It wasn't a particularly popular comment, but I stand by it.

[0] https://news.ycombinator.com/item?id=49219990

Re: We replaced Redis with MySQL for inventory reservations and it scaled

#190
post #159

Earlier quoted context omitted.

What exactly makes it "obvious" that this is written by AI? I could totally believe that AI was used to generate parts of it, but I really don't get the sense that the whole thing was written that way. I've seen way worse examples on this site. As software engineers we are constantly told that we need to heavily use these tools for our daily work. So is it surprising that software engineers use the same tools as writ…

Well, one thing to remember: AI learned from us (See what I did, there?) . The training these LLMs got, was from endless human-slop, on sites like LinkedIn, and marketing copy, everywhere. In fact, don't be surprised, if we start learning from AI; reversing the process. But I think that it's only a matter of time, before almost everything will be at least touched by AI. I posted this, yesterday[0]. It wasn't a partic…

[flagged]
Post reply on HN