I see now how sloppy my post was. I rewrote the entire article and simplified it as much as I could. I will keep every future post simple and easy for the readers.
Your comment is valuable. It nudged me to invest time into improving my writing skills. I'd appreciate it if you share future feedback.
This is a good article but the constant *bold* around words is driving me nuts.
hey, thank you for the feedback - accepted.
I see now how sloppy my post was. I rewrote the entire article and simplified it as much as I could. I will keep every future post simple and easy for the readers.
Your comment is valuable. It nudged me to invest time into improving my writing skills. I'd appreciate it if you share future feedback.
Thank you.
So SQL with scalability solution for write like partitioning/sharding/replication are the solutions for high-read with somewhat high write QPS system?
Out of context question, then what do you think is the use case that we want for a NoSQL database ? Only extensive-write systems with low read?