Products database Design: Entity-Attribute-Value (EAV) model or No SQL or another alterative models?

Question

Please, What is the best model to design and create an products database if I'm planning on having many products in the database: is Entity-Attribute-Value (EAV) model (By using Magento) or No SQL database or another alternative models?

Answer 1

There are pros and cons for both models:

Pros for EAV(Entity_Attribute_Value):

• Facilitates a generic architecture (easy to add|remove attributes)
• Relatively easy to implement

Cons for EAV

• Slow, resource consuming

  - Not scalable

Pros for NoSQL

• Fast, increased performance, easy to get all the needed information, usually will be stored in the same document.
• Easy to scale

Cons for NoSQL

• This is a hell to implement, when the times comes to manage generic stuff.

In conclusion I will suggest to choose NoSQL the biggest pro that I see is scalability.