←back to thread

175 points chilipepperhott | 2 comments | | HN request time: 0.008s | source
Show context
myflash13 ◴[] No.44474202[source]
Closest thing to true “serverless”: entire MVC app (Django/Rails/Laravel) in the browser with WASM and data persistence by SQLite over CDN.

All the server has to do then is serve binaries, all the business logic is in the client.

replies(2): >>44474217 #>>44474669 #
gjsman-1000 ◴[] No.44474217[source]
Brilliant… but now you need to validate that the client did all their business logic correctly without tampering. That alone can be so complex it defeats the point.
replies(1): >>44474340 #
justinrubek ◴[] No.44474340[source]
No... you don't need that. Not for the overwhelmingly vast majority of cases. Let people use their own software. Tampering? Not my problem. Let people do it if they want.
replies(3): >>44474357 #>>44474599 #>>44474690 #
1. Terr_ ◴[] No.44474690[source]
The "overwhelmingly cast majority of cases" will be an employee of a larger company, a person/computer that cannot be trusted with arbitrary access to data and exceptions to business rules in code.
replies(1): >>44475398 #
2. drdaeman ◴[] No.44475398[source]
If it's a single-user app, you can only load data the user actually needs and is cleared to access. And/or lock down the device.

Multi-user app (and if we're talking about companies, it's multiple users by the very definition) where users are not trusted almost always needs either a central service with all the access controls, or a distributed equivalent of it (which is, indeed, very hard to implement). “Local-first” in those cases becomes less relevant, it’s more of a “on-premises/self-host” in this case.

But I think while end-user non-business software can be small compared to enterprise stuff, it is still a fairly big market with lots of opportunities.