3 ms·
For a non-signed in session I can see some advantage in improving the swiftness of implementing supporting changes on the server for the client developers. For
by jebblue 11y ago
For a non-signed in session I can see some advantage in improving the swiftness of implementing supporting changes on the server for the client developers. For signed in sessions, you can't get around the database and an API update for it when the client needs some new feature or access so in the signed in case; I think the benefits of this nodejs part would be diminished.
- madeofpalk 11y agoI'm not sure if I quite understand your comment. You can still use authentication with an API... You don't need direct access to the database to do that.