The API tests passed. The database didn't.

A comparison of two releases of a Node.js and MariaDB products API found that conventional HTTP tests passed despite v2 adding 80 SQL queries, startup schema changes, an audit-table write workload, and 70 milliseconds of additional database time. The account argues that API contract testing verifies responses but cannot detect database regressions such as N+1 queries, changed query shapes, added columns, or unintended migrations, a concern amplified by faster AI-assisted development. Using proxymock to record HTTP and MariaDB wire traffic from equivalent test runs, teams can compare normalized SQL workloads without database credentials, ORM instrumentation, agents, or live schema introspection. Its reports identify new, removed, changed, and persistent statements, normalize performance by query volume, flag sufficiently sampled latency changes, and show table-level and schema-related drift. The approach can run locally or in CI and complements observability tools by explaining which SQL statements and tables caused performance changes before a release reaches production.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.