Thanks for checking.
We don’t need full database replication. We are just replicating activities that other servers are subscribed to. So the Comments table, only some of the rows will be “replicated”. Not sure if/how CouchBase handles this.

Can you provide a link? Only thing I see on Couchbase is for NoSQL databases.

Buying $10000 of Apple stock in 1997 wouldn’t really move the market. TSLA, GOOG, AMZN, MSFT, NVDA, and so on. Lots of stocks where I could buy a small about and get 500x-1000x returns some 10 years later.

I remember reading an issue where the scheduled task to update hot and active was breaking shortly after reboot. So those lists were getting frozen in time, until the next reboot.

The node still needs to receive every subscribed federated action and insert it into the local database. This has to be local to the “main application server”. Your proxy servers don’t reduce the number of federated actions. It only reduces the number of servers needed to communicate with.

I feel that the bottleneck will be the total number of federated actions, not which servers deliver them.

I believe the current implementation wont scale because instances won’t be able to handle every subscribed federated action. Having a hub server doesn’t reduce the number of subscribed federated actions, only whom they come from.

There is no need to “maintain all of the connections”. The server opens a connection, sends the data, then closes the connection.

Yes, it is a “full mesh” diagram. But for each specific “federated” action, it is a simple hub and spoke distribution. The hosting server will send the federated action to each subscribed node. The nodes don’t need to check in with each other for that specific action.

I too believe that Federation is going to have scaling issues. But not due to full mesh