I'm curious what kind of heavy load performance once can expect out of solidus? It's all DB backed so I imagine locking the inventory tables for reduction/addition is the bottleneck

Yes, that’s a valid point. By the way, the actual inventory units decrease is done on order completion only, so it’s usually concerning when a lot of people actually complete the purchase at the same time, not just adding to cart, which is usually a good problem to have. Another scenario potentially critical we saw in the past is with carts that have a lot (like thousands) of inventory units per order.

Good to know!

Thanks for the kind words ❤️ Usually that’s not a big problem in the Solidus world, at least from what I saw in the wild. We had stores running with high-volume without a lot of needs in terms of resources. Also, based on the specific requirements, Solidus is flexible and can be adapted quite easily if you have special needs.

Just wanted to point out that there's lot of parts of Solidus that can have a Redis cache in front of them which has sped up our store a lot. I know it's not a part of Solidus core but I imagine a lot of other developers use some kind of cache in front of the store, which makes it less DB bound. We haven't done that yet for inventory management in particular but I could potentially see it in the future, I heard of one person doing that with a non-Solidus e-commerce solution

What do you all do at your peak? (If it's something you can share)

What do you all do at your peak?

In a limited edition sale we did 1000-ish orders in 15-ish minutes...