This sees the database and flat-file systems pretty much neck and neck. Databases are regularly attacked by hackers, so they can inject malicious code.

SecurityĪs all the files are stored on the server with no database you get benefits of a reduced security risk, as one less point of attack. Some sites will really see a speed benefit from using flat-files, others not so much. Once in the real world, all the other things going on may mean the user of the site is totally unaware of any real improvement. However, given the many other things that have to happen (the data must be transmitted to the visitor, the visitor’s browser has to display the data, etc) this speed improvement may well be simply theoretical. With no database engine to add latency, data can be accessed much quicker. You may well have guessed that one of the big benefits of a flat-file system is speed. This is in contrast to a database system, which needs a special language and software engine to add, change and delete entries from the database. How does a flat-file CMS work?Ī flat-file CMS stores data as text files on the server, It creates separate files for parts of the website and its content. The technical methodology behind it all takes second place to how the pros and cons of each system fit in with your specific needs.

No matter if a website is static, dynamic, database-driven or flat, they all have one thing in common. As with all website tech, there are pluses and minuses. This month it’s the turn of flat-file CMS. We’ve talked recently about static Vs dynamic Content Management Systems.

Flat file cms