4 ms·
In this case it will just move into the database. You'll have to start writing procedures and rules in the database instead of in your web framework and only e
by Periodic 17y ago
In this case it will just move into the database. You'll have to start writing procedures and rules in the database instead of in your web framework and only expose those instead having only trusted code interact with the DB.
- mechanical_fish 17y agoYou'll have to start writing procedures and rules in the database instead of in your web framework This will not fool anyone. You can't fold the business logic into the database and then pretend that you've eliminated the business-logic layer on the server. It's still there. You've just driven it into hiding.
- Periodic 17y agoExactly. I don't think there is an equivalence between server code and client code. There are some things you just can't trust the client to do, so there will always have to be server code to do it. Whether that code is in a web server, a framework, a database, it doesn't matter. Someone has to write it. However, I could see some of the code, such as the code that actually builds the page the users sees, being pushed into the browser. But then, don't we already have that with XML and XSLT (or whatever?)
- voidfiles 17y agocouchDB folks are trying to create auth in client, they haven't succeeded yet, the crypto algorithms are a bit taxing on the browser, but they are trying.