Which architecture is more suitable for keeping bots running?

[vindisel]

I'm writing a farm and I have about 50 steam accounts. At the moment, it looks like this: I made a store where I put each logged-in account, then I use the steamid to access the desired one and perform an action.

const BotInstance = new Bot('login', 'password', 'shared_secret', 'identity_secret', 'steamid');

const newBot = await accountsStore.add('steamId', BotInstance);

newBot.login();

 

const getBot = await accountsStore.get('steamId');

getBot.addFriend('friendSteamId');

How would it be more efficient to leave it as it is or implement it all through a cluster?
what kind of power is needed to support such a large number of accounts? and won't I have a problem if they're all on the same ip?

Edited yesterday at 05:46 AM by vindisel

[Dr. McKay]

It depends on what you're doing and how you're doing it. If you're using node-steamcommunity for all those accounts, you're going to hit rate limits unless you're performing actions infrequently. And if you're logging in that many accounts from one IP, that'll rate limit you as well.

[vindisel]

7 hours ago, Dr. McKay said:

It depends on what you're doing and how you're doing it. If you're using node-steamcommunity for all those accounts, you're going to hit rate limits unless you're performing actions infrequently. And if you're logging in that many accounts from one IP, that'll rate limit you as well.

Yes, I use node-steamcommunity. Requests will be frequent on all bots. Thanks, so I need to provide a proxy server for each account. What about the cluster? Will it be redundant?
The problem is that I don't understand what kind of power I need. I've had a couple of bots for a long time now, and everything was fine on a cheap vps, but now I want to make more bots, but I'm afraid to run into the limitations of single-threaded of node.js

Edited 8 hours ago by vindisel