Database-Driven Websites

The difference in practical terms

On a static site, every page is a file someone made. Changing your phone number means editing every page it appears on.

On a database-driven site, the page is a template and the content is a record. Change it once and every page showing it updates. Add a new item and its page exists automatically.

That difference doesn't matter at ten pages. At two hundred it's the whole ballgame.

When it becomes necessary

• Visitors need to search or filter. Anything with browsing — inventory, listings, a directory, a catalog.
• The same fact appears in many places. Prices, hours, service areas, staff.
• Content has structure. Each item has the same fields, so each page should be generated the same way.
• Different people see different things. Logged-in customers seeing their own records — see client portals.
• Information arrives from visitors. Form submissions, bookings, quote requests that need to be stored rather than emailed and forgotten.

What "designing the data" means

Before any screens get built, the decision is what gets stored and how records relate. This is the part that's expensive to change later.

For a service business, typically: customers, jobs, appointments, invoices, staff. A job belongs to a customer. An invoice belongs to a job. An appointment has a customer and a staff member. Getting these relationships right at the start is why an application can grow instead of needing a rebuild.

Where it goes wrong

• Queries inside loops. One page firing hundreds of separate queries. The classic cause of a database site being slow.
• No indexes. Fine with a hundred records, unusable at fifty thousand.
• Unsanitized input. User input concatenated into a query is how databases get compromised. Prepared statements are not optional.
• No backups of the database itself. Backing up files but not data means restoring an empty shell. Covered in hosting and site management.

What you get from it

Beyond pages that maintain themselves: you now have data. Which services get requested most, where your customers actually are, how long jobs take, which months are slow.

That information already exists in your business but is trapped in emails and paperwork. Once it's structured, it can be looked at — which is what business dashboards are for.