Hello Dp members, I have a database driven website & I want to improve its performance so that pages can load quickly at client side. So i think I can use text files instead of database & I will update text files as well with programming if I will update my database from admin session. It means text file will remain same as database all the time or I will just not use database any more. I will only work with file system. But before doing this I have couple of questions regarding file system vs database system performance. 1. If I read data from text file or XML file instead of database tables, Will it give any positive effect to my website performance ??? 2. Like Databases have limited number of connections that number of limited users can access the database at same time.So is there any same type of limitation on accessing text files or XML file which are located on hosting server ??? 3. Which type of programming language (server-side programming language such as PHP or client-side programming language such as JAVASCRIPT) will be best to access the text file or XML file (which is located at hosting server) so that it can take maximum performance ??? 4. If I will access data from file instead of database then will I able to protect my data from to be copied and what type other hacking issues may rise ??? Thanks for your valuable time, Jimmy
1. Reading a database is much faster than reading text files or xml files, especially if you have a large number of records. 2. Most databases are good at handling concurrent access, all you need to make sure is that you open a connection when you need to and close it afterwards. 3. Its best to access your files using a server-side script for security reasons, I think. 4. From what I read here, I think you greatly underestimate the performance of databases.
Yup, caching is your way to go, I know asp.net allows you to cache even database driven web-apps, and only change on varying specifics that you choose. For instance, if the person's name is the only thing that changes... you can set it up to cache all but what varies, which is the block that renders the person's name...
I agree with fly26. It really is good to opt for Database rather than a text file. Updating and maintaining relationship among tables is a concern where text files fail to perform. If you want frequent updations, deletions, addition, retrieval; you should better go for a Database. And yes a text file can be seen by anybody. You have to encode the name and file on regular basis to avoid any sort of unwanted disclosure of data which may become a daunting task. If you opt for database, you can change the login ID and password to save your precious data.