Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
May 23, 2012 08:05 AM|LINK
I know nothing about ASP or coding in general. But what I can tell you is that the most difficult part is the spare parts catalogue and the relationship between spare parts and vehicles to which they apply.
Normally it will would follow a scheme:
parts > connection attributes > vehicles
Its a triple relationship.
In our catalogue, we have +1 billion possible REAL combinations.
You will probably find out that in faceted navigation with dynamic fields your app can easily crash due to the size of the thing.
Thats the reason why people tend to simplify selection routes by fixing them.
Other, more adventurous, explore dynamic schemes using sharding or newish non-relational dbs.
It also depends on how visible and flexible you want your catalogue to be.