I need to know which one is better to store data.For example in a site like orkut or myspace. i need to store the scraps of users .it is expecting millions of users Which is better to store datas-database or xmls?i Know there is security problem with xmls but i plan to store xmls in amazon s3.So i think there wont be anymore of a security issue. So anyone can help me in finding a better pick of the two .We should think of scaling it to millions of users.When we think of database, there is problem when server is down or crashed we loses all datas with it,but when datas are on xmls stored in amazon even if one server is down backup servers can fetch it from amazon?.But some say there can occur some problem with datatransfers if we are using xmls ,when we scale it to millions of users.I ahvent found yet a good solution of the two.I am really confused.Please help me to find the better choice.
Note:Very security related datas are not to be stored on xmls.
2006-11-08 22:22:44 · 5 answers · asked by stevesolanki 2 in Computers & Internet ➔ Programming & Design
Are we all missing something vital here?
It seems everybody assumes that by Xmls you mean XML. If you don't mean XML then we may well be answering the wrong question.
If you are looking for a solution that scales to millions of users then I'd suggest following the lead of the people who already have solved this problem. Firms like CraigsList have to deal with that sort of volume. What do they use? As far as I know they use mySQL. If it's good enough for them then it's good enough for you.
Pick a company that does something like what you think you want to and follow their development model, that's my advice.
///
2006-11-08 22:45:23 · answer #1 · answered by jan 7 · 2⤊ 0⤋
If you plan to store a large amount of data as you are claiming you will, XML is not a realistic option.
An XML file at the end of day is a static file with some rules enforced that allow you to read it and interpret it correctly. As the amount of data increases, very soon, the file bloats up. Reading it to add/remove data becomes a HUGE pain.
A DB is your best bet for real time support of massive amount of data. And most databases do a brilliant job of backup and recovery (you only need to know how to do it). Failover mechanisms are much better incorporated on Databases than anything else (or the modern world as we know it would crash!)
I think you have not thought this though
- You cant really build an application targeting million customers.
- You need to start small and build it up based on demand.
I suggest you implement a MySQL Database based solution and then see how it goes from there. MySQL is smaller than other databases like Oracle and it is a better option than XML
Just my 2 cents
2006-11-08 22:33:07 · answer #2 · answered by Neil 5 · 1⤊ 0⤋
From my experience, database is a better option. It is easier to maintain and detect errors. Finding an error in a large XML file is real time consuming and a big problem as many editors in Linux have a problem opening files larger than a particular size. Coding to insert into the DB and read from the DB are also simpler.
2006-11-08 23:26:20 · answer #3 · answered by jo 1 · 0⤊ 0⤋
Go for databases and also take help of the replication...
2006-11-08 22:26:46 · answer #4 · answered by Vaibhav 4 · 0⤊ 0⤋
xml..if u can implement it properly.database is the easier opt
2006-11-08 22:34:47 · answer #5 · answered by Demo 3 · 0⤊ 1⤋