How to organize the storage of attributes in an e-commerce application on ZF2 + D2?

Question

Doctrine ORM

E-commerce on ZF2+Doctrine2. It is known that there will be several tens or hundreds of groups of goods, All of them will have from five to twenty characteristics. It was decided to abandon the eav model, because. a bunch of joins to cling - do not really want to? and filtering within the category is necessary. As a result, I mapped the superclass, extended it with the first entity with a predefined set of characteristics. Everything seems to be working. And now the main question: what am I doing wrong? Did you make a mistake at the design stage and should you change your approach and choose some more efficient template for the implementation of the task?

Answer 1

As far as I know, all e-commerce products just use eav, and very successfully. And words like "reject the eav model, because you don't really want to chain a bunch of joins" are very similar to premature optimizations, which very often turn out to be erroneous. First, file it the way most people do, and then optimize it when there are code benchmarks. About premature operations from bitter personal experience *