godlosa.blogg.se - In comparison with flat file systems, databases:

I coded my own CMS (several) and have been quite happy on security and specially performance. Drupal (my fav choice) has better history and reputation because at the end a lot depends on code implementations, anyway if your file security is not good, even Drupal will fail. Let's not forget the many CMS and commercial software solutions relying on databases (like WP, Joomla, etc.) being hacked. So, the same file access & security implementation works on both areas (code and data).Amazingly nice to manage versions and backups.You can have them on the same place, disk or wherever you want to. Code and data are files you can see, copy, etc.And how much time you need to recover from failure (backups and restoring it).

It sucks trying to work with git or whatever version management, you have full control of your code but data needs extra steps.

It can be the opposite: having your data altered while your code is intact.

You might have great code security while having your database failing on that, or just exposed.

It's not like "set up and go" you need to secure both areas.

Code and data are in separate places, it's too much bad luck to have them both exposed.

The main difference about flat file databases is one has to build the system and features, but let's focus on security. The intention of this thread is not that, it's security. The first thing most people think of when talking about flat files VS databases is a ghost discussion about speed & features (mysql, postgreSQL, etc).