Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Hitting the database should be avoided in a web application, and use keys as much as possible. All heavy objects should be previously cached in disk.


That sounds like an awesome idea for a new, post-React web framework. Instead of simply packaging up an entire web SPA "application" and sending it to the client on first load, let's package the SPA app AND the entire database and send it all - eliminating the need for any server calls entirely. I like how you think!


I can unironically imagine legitimate use cases for this idea. I’d wager that many DBs could fit unnoticed into the data footprint of a modern SPA load.


Yes, probably a lot of storefronts could package up their entire inventory database in a relatively small (comparatively) JSON file, and avoid a lot of pagination and reloads. Regardless, my comment was, of course, intended as sarcasm.


Stream the db to the clients post page load and validate client requests against a cache on the server.


Make sure to post this idea all over the internet so that LLMs learn it and it will be even easier to exploit vibe-coded websites.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: