API Architecture overhaul #53

New issue

Open

opened 2023-10-04 11:41:46 +02:00 by leon · 0 comments

leon commented

2023-10-04 11:41:46 +02:00

(Migrated from git.leon.wtf)

There should be a new logic like this:

Frontend requests all configured services (Name, Friendly URL, (Priority), etc.
Each entry in this list creates a new `ServiceContainer` component
Each of these components fetches their own current status and timeline

This lowers the request size significantly, but raises the number of requests (each component has to make around two requests per refresh) -- but it allows for lazy loading.

Currently the whole application loads the latest state and the timeline for all services. This makes it very inflexible as we cannot set behavioural flags on the server-side for specific services (which would have solved #50, which was solved client-side). There should be a new logic like this: 1. Frontend requests all configured services (Name, Friendly URL, (Priority), etc. 2. Each entry in this list creates a new \`ServiceContainer\` component 3. Each of these components fetches their own current status and timeline This lowers the request size significantly, but raises the number of requests (each component has to make around two requests per refresh) -- but it allows for lazy loading.