We’re talking about pushing compute workloads across a distributed set of devices where that workload is linearly scalable by the number of devices involved, compute, storage, failovers…etc scale elegantly. Cloud computing can give you the tools to make such a thing a reality within the scope of the cloud provider, but it most definitely is not distributed computing just by existing.
Also the fediverse is NOT distributed computing either, at least for Lemmy. There is no distributed compute available for Lemmy. You can’t have a few hundred users toss up their own compute to handle loads for an instance. Each instance is limited to a single database, and can have webservers behind a load balancer to spread out the compute. And that’s about the best you’ve got. Not distributed, you can’t just spin up 100 nodes for a Lemmy instance to handle more load and everything “just works”. It’s a very “classic” architecture in a way.
A K8 cluster isn’t distributed computing until you build a distributed application that can elegantly scale with more and more nodes. And is fault tolerant to nodes straight up dying.
Kafka for example, is an actual distributed application. One which you could run on a K8 cluster, it self-manages storage, duplication, load balancing, failovers, rebalancing…etc elegantly as you add more nodes. It doesn’t rely on a central DB, it IS the DB, every node. Lemmy is not.
Cloud computing is… Not distributed computing.
We’re talking about pushing compute workloads across a distributed set of devices where that workload is linearly scalable by the number of devices involved, compute, storage, failovers…etc scale elegantly. Cloud computing can give you the tools to make such a thing a reality within the scope of the cloud provider, but it most definitely is not distributed computing just by existing.
Also the fediverse is NOT distributed computing either, at least for Lemmy. There is no distributed compute available for Lemmy. You can’t have a few hundred users toss up their own compute to handle loads for an instance. Each instance is limited to a single database, and can have webservers behind a load balancer to spread out the compute. And that’s about the best you’ve got. Not distributed, you can’t just spin up 100 nodes for a Lemmy instance to handle more load and everything “just works”. It’s a very “classic” architecture in a way.
A K8 cluster isn’t distributed computing until you build a distributed application that can elegantly scale with more and more nodes. And is fault tolerant to nodes straight up dying.
Kafka for example, is an actual distributed application. One which you could run on a K8 cluster, it self-manages storage, duplication, load balancing, failovers, rebalancing…etc elegantly as you add more nodes. It doesn’t rely on a central DB, it IS the DB, every node. Lemmy is not.