fediversity/meta
Watch
18
4
Fork
You've already forked meta
 5
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity

split up architecture to better clarify internals #36

Merged
kiara merged 4 commits from split-arch into main 2026-05-14 15:21:21 +02:00
Conversation 1 Commits 4 Files changed 3 +63 -36
kiara commented 2026-02-09 14:06:18 +01:00
Owner
Copy link

update the architecture diagram to:

  1. clarify the responsibilities of fediversity-core to delegate multi-tenancy to downstream business logic by remote procedure (see #334)
  2. split up the fediversity-core architecture to clarify the existence of the:
  3. reframe the operator VMs to encompass not just the monolithic set-ups combining applications, but also our base scenario of VMs serving a single application on behalf of a single deployment
  4. annotate arrow functions, ideally visible in tooltips somehow tho at least they're legible in source
  5. incorporate flows surrounding the API of fediversity-core (see #334)
  6. limit the overwhelming amount of arrows from secondary VMs

i have been struggling to get it to not make weird positioning tho...

this should get us a step closer to fediversity/fediversity#635.

update the architecture diagram to: 1. clarify the responsibilities of fediversity-core to delegate multi-tenancy to downstream business logic by remote procedure (see #334) - identity management now has been split up to distinguish between that of [downstream front-ends](https://git.fediversity.eu/fediversity/fediversity/issues/673) vs. [those of operators' own deployed applications](https://git.fediversity.eu/fediversity/fediversity/issues/212) 1. split up the fediversity-core architecture to clarify the existence of the: - [build queue](https://git.fediversity.eu/fediversity/fediversity/issues/242) - [SPIFFE server](https://git.fediversity.eu/fediversity/fediversity/issues/633) 1. reframe the operator VMs to encompass not just the [monolithic set-ups combining applications](https://git.fediversity.eu/fediversity/fediversity/issues/322), but also our base scenario of VMs serving a single application on behalf of a single deployment 1. annotate arrow functions, ideally visible in tooltips somehow tho at least they're legible in source 1. incorporate flows surrounding the API of fediversity-core (see #334) 1. limit the overwhelming amount of arrows from secondary VMs i have been struggling to get it to not make weird positioning tho... this should get us a step closer to https://git.fediversity.eu/fediversity/fediversity/issues/635. 
Signed-off-by: cinereal <cinereal@riseup.net>
Signed-off-by: cinereal <cinereal@riseup.net>
Signed-off-by: cinereal <cinereal@riseup.net>
Signed-off-by: cinereal <cinereal@riseup.net>
kiara commented 2026-05-14 15:21:18 +02:00
Author
Owner
Copy link

merging as @armijn ended up stepping back prior to commenting

merging as @armijn ended up stepping back prior to commenting
kiara merged commit 422a751939 into main 2026-05-14 15:21:21 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
WP2
work related with WP2 (from grant agreement)

  
WP3
work related with WP3 (from grant agreement)

No labels
WP2
WP3
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
fediversity/meta!36
No description provided.