What is the industry standard (or best practice) in database design for different product types with various attributes?

I have seen a lot of answers (from 2009 to couple years ago) addressing database design for product catalogs where each (possibly group of) product(s) has(have) different attributes, e.g. shoe with size, and color, and laptop with cpu, and ram. Methods go from class table inheritance, EAV, to json field, and even NoSQL, etc.

It's 2022, and there are tons of large e-commerce websites in the wild. I would like to know what method these people in the industry are using these days?

I would appreciate a response. Thank you.