I am developing two web-sites having - one having few tables and the other having over 50 tables. I am using PHP and MySQL.
Some of the tables of both the web-sites are expected to receive well over a hundred-thousand rows every year. I have read in some post in StackOverflow that a few hundred-thousand row is not a problem for MySQL. But in my web-site, the row count will be "HUGE" in about 10 years or more.
Also, the number of database access from those tables will be VERY HIGH in expected peak hours.
So, I have two questions. First, is MySQL ready for VLDB or the like scenario? Secondly, can MySQL handle large number of requests under extreme load, even if use techniques like indexing to speed-up database access? If not, which DBMS should I use instead?
The good news is that computers in ten years will be a lot faster than computers today, so that alone should buy you a lot of scaling.
MySQL can handle your data if you can structure it correctly and tune the server accordingly. Millions of rows is rarely an issue, and some instances have gone even to the billions level with careful planning, as is the case of Tumblr and their Jetpants toolset.
You haven't really given much detail on the frequency or intensity of write or read activity. "Very high" could mean several hundred per minute, or it could mean several million per second.