Menu

Post image 1
Post image 2
Post image 3
Post image 4
1 / 4
0

The database has to be a defensive boundary again

DEV Community·Andrea Debernardi·20 days ago
#ulNsN9ti
Reading 0:00
15s threshold

For two decades the database has been able to outsource trust to the application layer. The app authenticated users, sanitized inputs, enforced business rules, and the DB just executed whatever came through the connection pool. That worked because the caller was almost always software written by someone, reviewed by someone, and shipped on a release train. Agents don't fit that picture. Once an LLM with tool access holds a live connection to your production database, the assumptions behind the application-as-perimeter model stop being true: Connections aren't short-lived anymore. A tool-using agent can keep a session open across a long reasoning loop, with the SQL emerging one token at a time. The caller isn't deterministic. Two runs of the same prompt can produce different queries. Sometimes very different ones. Writes aren't intentional in the way a human commit is. An agent will issue an UPDATE without a WHERE clause if its plan says so. Failures don't surface loudly.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More