I've chosen Postgresql for my website. I expect around 80 thousand to lakhs of users on certain days. So Im worried about the scalability issue. Postgresql doesn't support clustering I guess. So is there an alternative?
yes but i have read and heard quite a bit about mysql's instability. Don't know how true the statements are. BUt im a little apprehensive about going in for mysql. Just can't afford to lose any data at all. Postgres is however known for its stability. The db is going to be huge...millions of records easily.
if that's what you want, then mysql or postgres are just fine. a DB server isn't just going make records disappear for no reason. so it's not a matter of which DB software you choose; it's a matter of how you implement that software and the kind of server hardware and OS you buy. your focus on which software package is too narrow.
for example, you could want the safest car possible. but if you focus on if the car simply has air bags and ABS brakes, you ignore other things like how prone the car is to rolling, how many and what type of airbags do you have, what kind of tires the car has, etc.
if you want better information than a flamewar of mysql vs. postgresql, you're going to need to be a LOT more specific about your requirements than you have been so far.
Originally Posted by afrika
Truth is a database system is as good as you design & implement it
I have never seen any RDBMS which is "bad" or unstable.
Yahoo uses MySQL as thier primary db. But i doubt if its the same MySQL out of the box.
I have also seen, companies, web portals do some serious "MAGIC" with different db(s). Though i havent heard much about postgres, i hear its mainly universities that deploy them.
Bad expiriences: I have seen two seperate senarios.
1. [GOOD DESIGN, BAD IMPLEMENTATION] A badly implemented solution, that threw a multinationals fiscal year to the dogs
2.[BAD DESIGN] A badly designed db, with a popular enterprise db system, that was like mouse traps in an old dark house
I had similar questions when i first got into db systems. There is a db for everyone's conviction out there.
I would advice you to look at the features of all enterprise db systems and see what you are comforatble with, it goes beyond clustering.
Personally, it boils down to your design and implementaion.
I have a friend, who uses flat text files, saying RDBMS is just a gimmick, but HEY ! thats his conviction.