Comment on Delusions of a Protocol

<- View Parent
INeedMana@piefed.zip ⁨1⁩ ⁨day⁩ ago

But is that a limitation of AP?

As far as I understand one could split a fediverse instance into three parts: data, backend and UI.
The data is not shared 1to1 - each instance gets a copy of the activity and from that creates it’s own copy. Hence the same post on different instances will have different id
The problem we are speaking about is the capability of the backend to process incoming copies. Meaning, I also understand that the part that serves the local data to UI should not be the problem

What if there was a queue at the front and from the backend a scalable ingestion worker would be split off? Those would only do the putting the actions onto the data. Probably with per community(?) FIFO topics/partitions, so we can process data in parallel and not worry about an updoot for a post that does not exist yet

Those would still be fairly easy to deploy and be vertically scalable, right?
Or is there some bottleneck in the protocol itself?

source
Sort:hotnewtop