Website Architecture & Database Self-Check Checklist: Pre-Launch Review

The pre-launch database self-check focuses not on benchmark scores, but on confirming there are no obvious performance landmines. The 7 checklists below can be …

Insights:Website Architecture & Database Self-Check Checklist: Pre-Launch Review

1. Query Count Check

  • Home page SQL queries fewer than 20.
  • List page fewer than 10, and does not scale with row count.
  • Detail page fewer than 8.
  • No queries inside loops.

2. Index Check

Check Item Standard
High-frequency filter fields Has index
Sort fields Has index or supports index-based sorting
Composite index order Filter column on the left
Unused indexes Cleaned up
Index selectivity Low-cardinality fields should not have standalone indexes

3. Slow Query Check

  • Enable slow query log with threshold set to 200ms.
  • All top 10 slow SQLs have a resolution (rewrite / add index / acceptable).
  • No temporary tables spilling to disk.

4. Cache Check

  • Page cache TTL is reasonable and can proactively expire after updates.
  • Cache hit rate is trackable (at least log counting available).
  • Personalized content is not cached.
  • XML-type outputs (sitemap, feed) bypass page cache.

5. Connection & Concurrency Check

  • Connection pool upper limit is below the database max connections.
  • Long-running transactions have been checked.
  • Slow requests do not occupy connections for extended periods.
  • No connection exhaustion alerts during peak hours.

6. Data Integrity Check

  • Key tables have unique constraints (slug, email, etc.).
  • Foreign keys or application-layer validation exist.
  • Deletion uses soft-delete or has cascade rules.

7. Rollback and Backup Check

  • A database backup exists prior to launch and has been verified as restorable.
  • Schema migration scripts support rollback.
  • Cache can be flushed within 1 minute.
  • Clear rollback trigger conditions are defined.

24-Hour Post-Launch Monitoring

  • New error log entries.
  • Slow query count vs. pre-launch.
  • Homepage and listing page TTFB comparison.
  • Peak database connections.

If any metric degrades noticeably, roll back cache or index changes first, then troubleshoot.

Common Oversights

  • Adding an index only to a large table without accounting for slower writes caused by the index itself.
  • Flushing the page cache but neglecting category listing caches.
  • Failing to back up launch scripts, forcing manual fixes if something goes wrong.
  • No slow-query monitoring, so issues went undetected for two weeks.

Boundaries

This self-check checklist filters out common problems, but it cannot replace stress testing. For scheduled promotions or ad campaigns, run separate concurrency tests.

Related Articles: