*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
-
Created by
user-0432d, last updated on Feb 25, 2021
1 minute read
Understanding the structure of 2 workflows and 5 teams
The project is divided into 2 workflows: online and offline
The members are divided into 5 teams: frontend-app, frontend-web, backend-online, backend-offline, infra
The table below gives a roughly good idea to understand the relations between 2 workflows and 5 teams
| Workflow | User | Interface (frontend) | API (backend) | database |
|---|---|---|---|---|
| Online | ​e.g. Parents uploading data/photo | ​app (iOS, Android) | ​APIs | ​Database named "BioHPC" |
| (by frontend-app team) | (by backend-online team) | |||
| Offline | e.g. Scientists view data | web (React) | APIs | Should also be on "BioHPC" |
| (by frontend-web team) | (by backend-offline team) |
You might notice infra team is missing in the table. Infra team builds up the environments (servers/GitHub/certs/domains/etc) to support other teams.
In one word, infra team underlies all other teams.
Workflows
To understand the workflows, from the link below, read the the last diagram in the bottom