Forum Administrators
@signal15 documentDB is not compatible with NodeBB. It is supposed to be a drop in replacement for MongoDB but the clients that we have that tried using it ran into some issues 
Otherwise if you run into issues with FarGate, do post here and we'll work through them 
@wellenreiter hi there! Can you post this onto our GitHub tracker?
Thanks for the kind words @NoduleJS @scottalanmiller ... We always try to keep NodeBB fast, and a lot of what @baris does day to day is doing the unpopular grunt work that makes NodeBB faster and faster, so if there is someone to applaud I think it would be him!
The fun (/s) part about pagespeed and other similar services is that the goalposts are constantly moving, so it pushes us to make the product better and better as expectations rise.
I will admit many sites just embrace the fact that a js heavy site is going to be a slow one. It does make it easier to stand out when your competitors don't try 
@scottalanmiller I agree, but I don't want to find out what would happen were it to be challenged in a court of law
So far as I know multiple domains works fine so long as the appropriate socket.io origins are configured.
There will always be one canonical URL, however, which is what is defined in config.json
Should be possible but I am not sure if mongodb transactions work on standalone servers yet, I think they are only for sharded clusters and replica sets.
In version 4.0, MongoDB supports multi-document transactions on replica sets.
In version 4.2, MongoDB introduces distributed transactions, which adds support for multi-document transactions on sharded clusters and incorporates the existing support for multi-document transactions on replica sets.
To use transactions on MongoDB 4.2 deployments(replica sets and sharded clusters), clients must use MongoDB drivers updated for MongoDB 4.2.
More info here https://docs.mongodb.com/manual/core/transactions/
Redis has multi for transactions so we could aim for something like this in our dbal layer.
const tx = db.transaction();
tx.setObject('user:' + uid, data);
tx.sortedSetAdd('users:joindate', Date.now(), uid);
await tx.exec();
So both commands are executed atomically.
You can fix the counts by running the following query in mongodb for each group that has the wrong member count.
// get number of users
db.objects.count({_key: "group:<replace_with_group_name>:members"});
// update group object
db.objects.update({_key: "group:<replace_with_group_name>"}, {$set: {"memberCount": <replace_with_value_from_previous_query>}});
