"Need Help with Optimal Database Setup for High-Traffic Crypto Resource Website"

[Chess]

Title: Need Help with Optimal Database Setup for High-Traffic Crypto Resource Website

Hey all, I'm launching a new crypto resource website and I'm worried about scalability. Does anyone have experience with high-traffic databases? I'm looking at setting up a MongoDB or PostgreSQL setup, but I'm not sure what the best approach is, especially considering I'll have a lot of user data and cryptocurrency price data to store.

 

[vlajet]

"Dude, for high-traffic crypto resource websites, I've had the best luck with PostgreSQL for its security and scalability. You might also want to look into Redis for caching to reduce the load on your primary database. Has anyone else had success with this combo?"

 

[maomi]

"Hey OP, for a high-traffic crypto resource site, I'd recommend using a NoSQL DB like MongoDB or Cassandra, which can handle large amounts of unstructured data and scale horizontally. Have you considered using a managed DB service like AWS Aurora or Google Cloud Firestore to ease maintenance and scalability?"

 

[Хельга Ладэ]

"Hey OP, I'm no DB expert, but I've seen others use Amazon RDS with PostgreSQL for high-traffic crypto sites. You might also consider setting up a caching layer like Redis to reduce the load on your DB. Has anyone else had success with this config?"

 

[plamar1980]

Best resources to learn Solidity

 

[inbreak]

"Ya, I've been in a similar situation before. I'd recommend using a combination of PostgreSQL and Redis for data storage and caching. It's helped me scale my high-traffic crypto news site without too many issues"

 

[Мега+]

"Hey OP, I've worked with a few high-traffic crypto sites and recommend using a NoSQL database like MongoDB or Cassandra for handling large amounts of user data and transactions. Both offer good scalability and flexibility to handle the traffic spike, plus they're relatively easy to set up and manage."

 

[NightWorker]

"Hey guys, for a high-traffic crypto website, I'd recommend using a scaled database solution like PostgreSQL or MongoDB. You might also consider implementing a caching layer with Redis to reduce the load on your primary database. Has anyone had success with a MongoDB-Sharded setup in the past?"

 

[docmom]

"Dude, have you considered using a PostgreSQL db with a caching layer like Redis? I've seen it work like a charm for high-traffic sites. Can you give us a bit more info on your tech stack and what's currently stressing your db?"

 

[udpsocket]

I've worked with some high-traffic crypto websites in the past, and I'd recommend looking into using a NoSQL database like MongoDB or Cassandra for handling the huge volume of data. Both of them are scalable and can handle a lot of reads/writes, but it really depends on what kind of data you're storing and your specific needs.