If each instance is a separate application than must scale on it’s own, then no distributed computing is occuring.
There is one database, and you can have the instance itself behind a load balancer.
Lemmy is not a distributed program, you can’t scale it linearly by adding more nodes. It’s severely limited by it’s database access patterns, to a single DB, and is not capable of being distributed in it’s current state. You can put more web servers behind a load balancer, but that’s not really “distributed computing” that’s just “distributing a workload”, which has a lot of limitations that defeat it being truly distributed.
Actual distributed applications are incredibly difficult to create at scale, with many faux-distribited applications being made (Lemmy being n-tier im a per instance basis).
Think of Kafka. Kafka is an actual distributed application.
Lemmy is… Not distributed computing.
If each instance is a separate application than must scale on it’s own, then no distributed computing is occuring.
There is one database, and you can have the instance itself behind a load balancer.
Lemmy is not a distributed program, you can’t scale it linearly by adding more nodes. It’s severely limited by it’s database access patterns, to a single DB, and is not capable of being distributed in it’s current state. You can put more web servers behind a load balancer, but that’s not really “distributed computing” that’s just “distributing a workload”, which has a lot of limitations that defeat it being truly distributed.
Actual distributed applications are incredibly difficult to create at scale, with many faux-distribited applications being made (Lemmy being n-tier im a per instance basis).
Think of Kafka. Kafka is an actual distributed application.