<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>API on Ben Petito</title><link>http://peti.to/tags/api/</link><description>Recent content in API on Ben Petito</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 16 Aug 2026 09:00:00 +0930</lastBuildDate><atom:link href="http://peti.to/tags/api/index.xml" rel="self" type="application/rss+xml"/><item><title>What Happens When Someone Asks Your API for Everything at Once?</title><link>http://peti.to/posts/api-for-everything-at-once/</link><pubDate>Sun, 16 Aug 2026 09:00:00 +0930</pubDate><guid>http://peti.to/posts/api-for-everything-at-once/</guid><description>&lt;p&gt;A client had been bulk-loading data straight into the database with SQL, to speed up onboarding new customers. It&amp;rsquo;s a reasonable instinct, SQL is fast and easily repeatable with minimal effort, but writing directly to the database skips the permission checks, validation and auditing the application does for you. So I suggested our platform&amp;rsquo;s built-in REST API instead, and built them a Postman collection to try it. Somewhere in the testing they sent off a couple of requests with no page size on them, and the development server ran out of memory and fell over. Then it did it again.&lt;/p&gt;</description></item></channel></rss>