pooling instances to shared VMs #322

Open
opened 2025-04-28 12:36:01 +02:00 by kiara · 0 comments
Owner

As a host,
I want to pool Fediversity instances to shared VMs,
so that usage spikes are ameliorated granting users a smoother experience.

implementation notes

ways to achieve this include:

  • pooling a user's services into VMs shared across their resources (c.f. #339, #341)
  • pooling a service across different users into a shared VM
    • note this comes with security concerns
    • performance gains may particularly impact applications prone to resource usage spikes
    • user-level CRUD likely involves LDAP or Terraform more broadly (in our Nix context possibly using declarative-runtime - vault, postgresql, ldap, applications...)
    • may involve use of SRV records
    • challenge: what does this mean for migration (#100) when hosting providers have a shared single instance differing in version?
      • potentially address by initially making a separate instance of the desired version for this, perhaps with the intent to eventually reconcile this into the shared one
  • this may be addressed for now by #327
**As** a host, **I want** to pool Fediversity instances to shared VMs, **so that** usage spikes are ameliorated granting users a smoother experience. ## implementation notes ways to achieve this include: - pooling a user's services into VMs shared across their resources (c.f. #339, #341) - pooling a service across different users into a shared VM - note this comes with security concerns - performance gains may particularly impact applications prone to resource usage spikes - user-level CRUD likely involves LDAP or Terraform more broadly (in our Nix context possibly using [declarative-runtime](https://github.com/applicative-systems/declarative-runtime) - [vault](https://registry.terraform.io/providers/hashicorp/vault/latest/docs), [postgresql](https://registry.terraform.io/providers/cyrilgdn/postgresql/latest/docs), [ldap](https://registry.terraform.io/providers/Ouest-France/ldap/latest/docs), applications...) - may involve use of SRV records - more on this at https://git.fediversity.eu/vanrein/architecture/issues/1 - challenge: what does this mean for migration (#100) when hosting providers have a shared single instance differing in version? - potentially address by initially making a separate instance of the desired version for this, perhaps with the intent to eventually reconcile this into the shared one - ~~this may be addressed for now by #327~~
Sign in to join this conversation.
No milestone
No project
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.

Reference
fediversity/fediversity#322
No description provided.