How NOT to Design a Database-Driven Web Application

Say you are designing a web application. This application has a few basic components, including vendors, parts, and sales of said parts. How many database tables would you require to make such an application?

If you answered 3-5, you’re thinking waaaaay too small. Think more like 1,300 over the course of a few months of use. Why? Because naturally you’ll want to make a new table with each new sale made by a vendor!

If this is too technical for you, average reader, think of it this way: every customer who comes into a coffee shop to buy something gets their own, dedicated cash register, installed, at the time of purchase.

Yeah, that makes a hell of a lot of sense.

Leave a Reply