News for hackers. Stuff that matters.
Re:Do not build your Gov.uk service as a single-page applica... by stavros on Sunday September 29, 2024 @09:30AM (#41687275)
The main part is to avoid holding state in two places (frontend and backend) if you can do with holding state in only one (either frontend or backend).
Re:Do not build your Gov.uk service as a single-page applica... by redman25 on Sunday September 29, 2024 @10:00AM (#41687462)
Unless you're building an app that holds data locally, for most web apps, you should be pushing state down into the backend. Fat models should be your single source of truth, skinny controllers, and service functions in order to separate data from code for testability.

Avoid caching as much as possible until you absolutely need to. As soon as you introduce caching you now have multiple sources of truth instead of one.

Re:Do not build your Gov.uk service as a single-page applica... by bdangubic on Sunday September 29, 2024 @12:45PM (#41688564)
or be stateless… ;)