I don't know about you but writing 25 entries to a table in one second is pretty good for me. I can store 25 articles in 1 second without paying a cent.
Writing is going to be pretty asymmetric, and 25 should be fine, except perhaps for the initial load. Reading though is going to be more problematic. One place I worked the initial page load was ~100 database reads.
You are right. Almost all databases are read heavy, rather than write heavy.
For a real database load that's exposed to public reads, you need to handle the scaling, or in other words, pay up.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It doesn't matter how much it is if you can't access the way you need to.
I don't know about you but writing 25 entries to a table in one second is pretty good for me. I can store 25 articles in 1 second without paying a cent.
Writing is going to be pretty asymmetric, and 25 should be fine, except perhaps for the initial load. Reading though is going to be more problematic. One place I worked the initial page load was ~100 database reads.
You are right. Almost all databases are read heavy, rather than write heavy.
For a real database load that's exposed to public reads, you need to handle the scaling, or in other words, pay up.