Middleware Basics vs Smart Abstraction
Both are commonly confused. Here is a side-by-side breakdown of what each one does, when to reach for it, and when it would be the wrong choice.
Middleware Basics
Middleware = Code that checks every request before it reaches your app. Like a security guard at the entrance, one checkpoint instead of checking IDs at every door.
Read full block →Smart Abstraction
Smart Abstraction = One function that tries multiple ways to get the job done. Primary fails? Try the backup. Backup fails? Use the cache. Your app keeps working.
Read full block →When to use each
Use Middleware Basics when
-
Multiple pages need the same check
If 10 pages all need "user must be logged in," that's middleware. Write the check once, apply it everywhere.
-
You want to track every visitor
Want to know who visited what page and when? Instead of adding tracking code everywhere, middleware sees every visitor in one place. Like a guest book at the entrance.
-
You need to block unwanted visitors
Fake accounts, banned users, suspicious activity: stop them at the entrance before they cause trouble. No need to check at every room.
Use Smart Abstraction when
-
You call external APIs that might fail
AI providers have outages. Scraping sites go down. Payment APIs hit rate limits. A smart function retries and falls back automatically, so your users never see "Service Unavailable."
-
You want to switch providers without rewriting code
Today you use OpenAI, tomorrow you want Claude. With smart abstraction, you update ONE function. Without it, you hunt through 50 files changing API calls.
-
You need to reduce costs with cheaper fallbacks
Use the expensive fast API for speed, but fall back to a cheaper option when budgets are tight. Or use free scraping first, then paid APIs when free fails.
-
Your app can't afford downtime
Production apps need reliability. A smart function with fallbacks means one provider's bad day doesn't become your bad day.
When to avoid each
Avoid Middleware Basics when
-
Only ONE page needs the logic
If only your admin page checks for admin role, just put that check in the admin page. Don't overcomplicate.
-
You're building a tiny app
A 3-page website doesn't need middleware architecture. Keep it simple until you actually need it.
Avoid Smart Abstraction when
-
You're building a quick prototype
If you're just testing an idea, don't worry about fallbacks yet. Get it working first, then add resilience when you know it's worth building.
-
Only one provider exists for your use case
Some APIs are unique. If there's truly no alternative, smart abstraction can still help with retries, but fallbacks need somewhere to fall back to.
-
The operation is local and reliable
Reading a local file doesn't need fallback logic. Smart abstraction is for unreliable external dependencies, not internal operations.