"Database Dilemma: Scaling for 100,000+ Users?"

[katkov-ao]

Title: Re: Database Dilemma: Scaling for 100,000+ Users?

Hey guys, I'm having a major scaling issue with my web app's database. We've got a growing userbase and our MySQL setup is getting bottlenecked - latency's spiking and queries are taking ages to load. Has anyone else out there dealt with similar database scaling problems and can share some advice?

 

[Juliia Hofman]

"Been there, done that. For our project, we ended up using a distributed database solution and sharding the data to handle the increased traffic. Works like a charm, but it requires some serious dev resources to set up and maintain."

 

[palez]

"Heya, scaling for 100k+ users is a beast of a problem . I'd say look into distributed databases like Cassandra or MongoDB, they're designed to handle massive traffic. We had success with MongoDB at work, might be worth checking out."

 

[Lukyanov]

"Definitely gotta consider distributed DBs like Cassandra or MongoDB for scalability. We've had good luck with them in the past, but it really depends on your specific use case. Anyone have experience with graph databases for user relationships?"

 

[firstking]

"Yikes, that's a lot of users! Have you considered going with a managed cloud database like AWS Aurora? It's handled our scaling needs for our crypto trading platform."

 

[emx25]

"Hey guys, been there, done that. For scaling databases with high user counts, I've had good luck with distributed databases like Cassandra or even NoSQL solutions like MongoDB. Anyone else have experience with sharding for large-scale apps?"

 

[АААНДРОНААА]

"Hey guys, just wanted to chime in on this. We've been dealing with something similar at my old startup, and in the end, we went with a distributed database setup (using MongoDB in our case) to handle the scalability issues. Has anyone else had success with this type of setup?"

 

[rdrm]

"Y'all, I've been in a similar situation with a project I worked on, and we ended up using a sharded database approach. It helped us distribute the load and scale more efficiently. Has anyone else tried something like PostgreSQL with Citus?"