Hacker News Reader

I think this will face the same problems as Next.js edge runtime: your database cannot be moved to the edge

There are already edge databases.

Also, not everything requires a database.

Honest question, what kind of requests are you thinking of? In my projects I’m always fetching or changing data in a database on each request and if I’m not then I’m probably moving that logic to the frontend.

A basic example is some compute service, say image transformation. You just run computations where all the input is in the request, and all the output goes to the response.

I feel like you still need to the DB for that, for auth at a minimum (which might not need to hit your main DB I guess) if not for logging (spend credit/record usage/just analytics). I guess all of that could be skipped with something like a JWT and log ETL process.

I'm intrigued by edge computing but the DB always seems like the bottleneck so thank you for the example.

Reply on news.ycombinator.com