Back

Setting user limit at 100,000

  • 0
  • Auth
  • Web
  • Cloud
stranger
13 Aug, 2024, 17:57

How can i set up user limit at 100,000 in my project

TL;DR
Developers want to set a user limit of 100,000. They are exploring options for configuring multiple db instances to handle scaling with a million users. They wish to decouple application data and user data in different databases like MySQL and MongoDB/DynamoDB. They seek guidance on maintaining user counts efficiently. The solution given involves setting up a mechanism to maintain the count and creating new accounts only if the count is below 100K. To set the user limit, developers can access the console at Auth > Security > Users Limit.
Steven
13 Aug, 2024, 19:58

You tagged "Self Hosted" and "Cloud". Are you using both or just one?

stranger
14 Aug, 2024, 04:19

well, both i'm asking for, planned to use self hosted, with cloud currently.

Steven
14 Aug, 2024, 14:30

The settings are in the Console at Auth > Security > Users Limit.

Is there any problem with updating that?

Steven
14 Aug, 2024, 14:31

Oh right...the max is 10k...what's your use case that you need 100K and not 10k?

stranger
18 Aug, 2024, 07:13

I wanted to limit it to 100k or more in self hosted version, needed to know how can we do that, any other ways apart from limiting through the auth console?

Steven
18 Aug, 2024, 17:12

Why 100k? What's your use case that you need 100k and not 10k?

stranger
19 Aug, 2024, 02:03

Not a use case, 10k would be fine for beta but if we get beyond in case, for further scaling, maybe limiting to 50k or 100k till we get a robust infrastructure resilent enough to scale further. Anyways, I needed to know how can we decouple services so that we can autoscale the stateless services while maintaining the data separate, like user data, session data, and application data.

stranger
19 Aug, 2024, 02:05

It is more of a how can we deal when certain scenarios are there, not a use case actually. Thanks for responding btw.

Steven
19 Aug, 2024, 02:13

The problem is counting can be slow with large amounts of date. It's usually best to maintain a running count so you don't have to run through and count everything any time the count is needed.

So, you should set something up to maintain the count. Then, expose a function to create an account. The function can check the count and only create the account if the count is below 100K

stranger
20 Aug, 2024, 04:02

seems like a good idea, thanks.

stranger
20 Aug, 2024, 04:06

I had one more query, in case of scaling, i want to decouple the db, like i want application data to be stored in lets say mysql, and user data and user session data in mongodb or dynamodb, so how can i approach decoupling with differerent dbs offering different functionalities so that i can scale the stateless structure horizontally.

Steven
20 Aug, 2024, 14:30

Appwrite only supports mariadb at the moment

stranger
20 Aug, 2024, 15:00

So is there a way to configure multiple db instances separately for different use cases while scaling the containers horizontally. Basically how can we handle scaling with a user base of let's say 1 million.

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more