ping-multi | Interactively ping multiple hosts from one location | Networking library

What you want to achieve is called horizontal partition or database sharding, have a look Database sharding and JPA

https://www.javaworld.com/article/2073449/think-twice-before-sharding.html

Other option, easy one https://www.mysql.com/products/cluster/scalability.html

Comment markers in VBA are ', but yours are ‘: the VBA compiler doesn't recognize the character as an apostrophe and thus considers it part of an identifier.

Syntactically, an identifier sitting all alone on a line of code has to be a procedure call (or an unqualified member call against some global-scope object).

And a procedure call (or member call) can't be legal in a module's (declarations) section or anywhere outside a procedure's scope, since it's an executable statement.

And then the string delimiters " are ”, which also confuses the compiler.

Fix the single and the double quotes, the code will compile. Ctrl+H to find & replace =)

Rule of thumb, don't copy+paste code from blog posts if they're not formatted as code.

The issue here was I was using the same name for mongodb container across all the hosts. And since all the containers connect to the swarm network, there were 8 mongodb containers with the same name which is quite a silly mistake. It caused an issue when the docker container of composer-rest-server tried to connect to the mongodb container. This connection is defined in COMPOSER_DATASOURCES variable. Using the different name for each of the mongo containers across all the hosts solved this issue.

1. Once a REST client (where the wallet is) has authenticated to the REST Server, that client can add Blockchain identities (one or more) to its own REST client wallet. The wallet is private to that client, and is not accessible to other clients. When a client makes a request to the REST server, a Blockchain identity in the clients wallet is used to digitally sign all transactions made by that client (and the REST server knows who that is on the business network as that identity is mapped to a participant).

   Please note that this feature requires that clients trust the REST server. This trust is required because this feature requires that the REST server stores the clients Blockchain identities as part of the card. Therefore, it is strongly recommended that clients only use REST servers that are managed by a trusted party, such as an administrator within their organization.

   All information regarding authenticated users and their wallets (containing each users business network cards when multiple user mode is enabled) is persisted in a LoopBack data source by using a LoopBack connector. You would normally set up a persistent store such as MongoDB and the REST server would use a Loopback adapter to access the MOngoDB store. REST clients that have authenticated via a strategy will normally get an access token (once they authenticate) and which is stored locally (such as in the browser for OAUTH2)

2. Channels and Peers (which come from Hyperledger Fabric) are configured in connection profiles (connection.json file) which are part of the business network cards built for a participant of the business network. The REST server itself doesn't 'join peers or channels' it knows about it because it is started with a business network card (and the definition of the channel and peers are known to the REST server that discovers the business network to which it relates). Obviously you can stand up many REST server instances to serve the different 'living' business networks deployed (on whatever channels (ledgers) or peers defined in the profile) in an organisation.