4 ms·

I found Shopify’s post very easy to read, and learned about some features of MySQL. On the other hand, I didn’t get any value from reading your comment. You s

by akamaka 1mo ago

I found Shopify’s post very easy to read, and learned about some features of MySQL. On the other hand, I didn’t get any value from reading your comment. You seem to have a bunch of opinions about how things should be done, but haven’t given any details about how you came to these conclusions.

trueno 1mo ago
I've done multiple large scale implementations with shopify paired with many flavors of order managmeent systems as well as competing offerings in the space. The only one i haven't touched that i'd like to get my feet wet with is commerce tools. I really just disagreed with the assessment that redis is not good enough for the job for a reservation system. I use sql database all the time, I prefer them. But I'm seeing a claude written article here that seems to heel turn on a proven technology, it would at most be insightful if there was human content in here from actual engineers at shopify who want to vouch for and explain the challenges they were up against with redis rather than just expect me to take claudes word for it. Anyone who's been dabbling with AI knows damn well that you can convince claude to write up a dissertation on any hill you want to die on.
- akamaka 1mo ago
  It’s unfortunate that the writing style wasn’t up to par, but I want to point out that I read the entire article and it doesn’t contain any criticisms of Redis. From the sounds of it, Redis worked perfectly and achieved what they wanted, which was beyond the capabilities of a simple MySQL implementation of the system. In the end, they found a way to make it all work on MySQL, which solved some of the inherent complexity of using multiple databases side by side (but again this isn’t a criticism of Redis, the same problem would exist for any pair of databases).
dawnerd 1mo ago
I found it really hard to read, the llm-isms are just too distracting. Does no one proof blog posts anymore?

by akamaka 1mo ago

trueno 1mo ago

I've done multiple large scale implementations with shopify paired with many flavors of order managmeent systems as well as competing offerings in the space. The only one i haven't touched that i'd like to get my feet wet with is commerce tools. I really just disagreed with the assessment that redis is not good enough for the job for a reservation system. I use sql database all the time, I prefer them. But I'm seeing a claude written article here that seems to heel turn on a proven technology, it would at most be insightful if there was human content in here from actual engineers at shopify who want to vouch for and explain the challenges they were up against with redis rather than just expect me to take claudes word for it. Anyone who's been dabbling with AI knows damn well that you can convince claude to write up a dissertation on any hill you want to die on.

akamaka 1mo ago
It’s unfortunate that the writing style wasn’t up to par, but I want to point out that I read the entire article and it doesn’t contain any criticisms of Redis. From the sounds of it, Redis worked perfectly and achieved what they wanted, which was beyond the capabilities of a simple MySQL implementation of the system. In the end, they found a way to make it all work on MySQL, which solved some of the inherent complexity of using multiple databases side by side (but again this isn’t a criticism of Redis, the same problem would exist for any pair of databases).

dawnerd 1mo ago

I found it really hard to read, the llm-isms are just too distracting. Does no one proof blog posts anymore?