Urgent.News

What's breaking now, across thousands of outlets.

Tech

[ Video ] Stories from the Vibe Coding Trenches – Accidentally Overpaid $150 to Cloudflare

I’m starting a new series of videos: stories from the vibe coding trenches, with real life situations encountered during my vibe coding endeavors. As you already know, I have 15 apps in the App Store already, and I started all this in February this year. The first story is about how I overpaid $150 to Cloudflare, because of a rookie mistake. Full video is at the top of the article. I launched…

In a new series of videos, the author shares a story from their coding experiences titled "Stories from the Vibe Coding Trenches." The first episode details an accidental overpayment of $150 to Cloudflare. This began with the launch of an app called Flight Lens, which monitors air disruptions and delays, allowing users to track ticket prices.

The app uses an expensive API to process flight delay data and plans the engine to stay within the beginner plan of the API. The API cost around $45 a month, and the backend was deployed on Cloudflare for approximately $5. After two months of refining the app, the author launched the product, and it received positive feedback from users.

However, the Cloudflare invoice arrived, revealing a payment of $150, which was three times the cost of the API. The author initially had no idea how this happened. Upon further investigation, they discovered that database reads and writes are charged separately. They were writing roughly 150 million times a month, which exceeded the write limit, causing the extra charges.

The author then optimized the code again, monitoring both API limits and database write ceilings. They also set up billing alerts to get notified before any charges became too high. This experience taught the author the importance of paying attention to service charges, as even experienced coders can be surprised by hidden fees.

The author concluded that this story highlights the need to stay vigilant and aware of how services are billed to avoid unexpected expenses.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Deploy a Hono backend on AWS Lambda without an adapter layer

A Hono app may already have a normal HTTP server, routes, middleware, and database calls. Moving that app to Lambda used to mean adapting the request lifecycle or adding a bridge layer.

  • Deploy Hono backend on AWS Lambda Web Functions without adapter layer.
  • Node.js HTTP server listens on port, using AWSLAMBDAHTTPENDPOINT.
  • Evaluate app's startup behavior, authentication, regions, and cost impact before deployment.

Farmora: my Next.js shop stalled up to 6s a page, so I made it local-first

What Farmora is Farmora ("From Local Farms to Your Door") is a farm-to-door marketplace. Farmers list what they've harvested and customers buy straight from them.

  • Farmora marketplace connects local farmers with customers for fresh produce.
  • Local-first approach implemented to ensure quick page loads despite backend issues.
  • Cached data merged with seed data and browser changes for immediate response.

More from Wednesday 14 October →