diff --git a/components/app/marketing-articles-rate-limit-test.tsx b/components/app/marketing-articles-rate-limit-test.tsx
index b430f9c..972031c 100644
--- a/components/app/marketing-articles-rate-limit-test.tsx
+++ b/components/app/marketing-articles-rate-limit-test.tsx
@@ -3,6 +3,7 @@
import { useState } from "react"
import { useTestRateLimit } from "@/orpc/hooks/use-test"
import { toast } from "sonner"
+
import { parseRetryTime } from "@/lib/utils/rate-limit"
import { Icons } from "@/components/shared/icons"
@@ -278,9 +279,11 @@ export function MarketingArticlesRateLimitTest({
>
{isAtLimit
? (() => {
- const latestError = requestLogs.find(log => !log.success)
+ const latestError = requestLogs.find(
+ (log) => !log.success
+ )
const retryTime = latestError?.retryAfter
- return retryTime
+ return retryTime
? `Rate limit reached! Wait ${retryTime} seconds before trying again.`
: "Rate limit reached! Please wait before trying again."
})()
diff --git a/data/articles/building-bulletproof-apis-rate-limiting-orpc.mdx b/data/articles/building-bulletproof-apis-rate-limiting-orpc.mdx
index ccb4874..652ae4e 100644
--- a/data/articles/building-bulletproof-apis-rate-limiting-orpc.mdx
+++ b/data/articles/building-bulletproof-apis-rate-limiting-orpc.mdx
@@ -1,5 +1,5 @@
---
-id: 3
+id: 1
title: "Building Bulletproof APIs: A Complete Guide to Rate Limiting with oRPC"
description: "Learn how to implement enterprise-grade rate limiting for your oRPC APIs to protect against abuse, DoS attacks, and resource exhaustion. Complete with code examples and interactive demos."
publishedAt: "2025-10-25"
diff --git a/data/articles/region-deployment-importance.mdx b/data/articles/region-deployment-importance.mdx
new file mode 100644
index 0000000..3643ea4
--- /dev/null
+++ b/data/articles/region-deployment-importance.mdx
@@ -0,0 +1,155 @@
+---
+id: 2
+title: "Why Your Database Location Matters: The 200ms Lesson"
+description: "Spoiler: it was just geography. Here's how moving the app closer to the database turned 2 second delays into sub-200ms responses."
+publishedAt: "2025-11-01"
+href: "/articles/region-deployment-importance"
+---
+
+So we deployed Zero Locker and users kept complaining about it being slow. Like, really slow. Everything was taking 2-3 seconds. The weird part? It was instant on localhost.
+
+After blaming the database, the queries, the network, the serverless cold starts - we finally found it. The database was in Frankfurt. The app was in Washington D.C.
+
+## What We Actually Saw
+
+- Click on a credential? 2 seconds to load
+- Create new credential? Another 2 seconds
+- Just navigating around? Everything felt laggy
+
+My first thought was "it works fine locally, so the code is good. Must be something else."
+
+Checked the database - Neon hosted in Frankfurt (eu-central-1).
+Checked Vercel - deployed to Washington D.C. (us-east-1).
+
+That's 3,900 miles apart. Every request was crossing the Atlantic Ocean.
+
+## The Math
+
+```
+Every request: Washington → Frankfurt → Washington
+Round trip time: ~200-300ms
+One page load: 5-10 requests
+Total delay: 1.5-3 seconds
+```
+
+No wonder it was slow. Each API call was bouncing across continents.
+
+Localhost was fast because everything was on the same machine - network latency was basically zero. Production was slow because physics.
+
+
+
+
+
+
+
+
+
+