Skip to content

1.1. Architecture

Jump to bottom
Haris Chaudhry Mendívil edited this page Dec 11, 2024 · 8 revisions

General architecture ideas

  • Standalone backends that solve a particular set of problems represented by a 'problem domain'
  • The app should behave in the same way when switching backends (platform-agnostic)
  • For each domain we can have some common ground, most likely as a universal API contract

Components

overview-diagram-1

A frontend solution 'X' would present a problem domain 'A' (could be many) which can be implemented by a backend solution 'P' (or others). In the frontend solution we can configure the backend that would implement the domain.

(In the frontend, in addition to the domain features, we need global features to switch between domains and configure backends per problem domain).

Flow of the app

For a particular frontend solution:

  1. Problem Domain selection
  2. Backend solution selection (for the domain, only available / running ones)
  3. Presentation of the selected solution for the problem domain

Clone this wiki locally