#27156
The Drupal Database Design is a Comedy of Errors 
Drupal's database design is stupid! it sucks! it is crap! To things clearer I am talking about design errors. Yes, they do exist. Some say that design errors are the basic cause of bugs in a system. They are right. Rather than go through a bunch of queries or rather hundreds of queries, I will just say that the database design has no relational qualities that would optimize and speed up the system what so ever. This a glaring whole in the knowledge of the Development team so if you are a joiner and want to contribute to the project then think about helping them out with the database design first.
Hiveminds (2005). Articles>Content Management>Software>Drupal
#27127
Drupal Has Terrible Access Control
After a week of fighting with it I have come to the conclusion that Drupal access control modules are all inadequate and are based on some weak database design. Taxonomy access and node access are flawed from the start. This type of access control where the assets are assigning their own internal security is not scalable and suffers from very high database overhead.
Hiveminds (2005). Articles>Content Management>Software>Drupal
#27376
The Ockham's Razor Principle of Content Management Systems
Unless we manage to make Drupal more accessible to new users and to get back to the basics, we'll find the ground shifting beneath our feet.
Buytaert, Dries. Poynter Online (2004). Articles>Content Management>Software>Drupal
#32581
Five Reasons Why the Drupal CMS is Not Ready for the Enterprise
Many Open Source content management systems written in PHP want to be recognized by the business industry as being "enterprise" ready. This is not only a mark of prestige and status but places them in a position where large companies are ready to invest in the software as a platform for their projects. Drupal is now trying making its move to be enterprise ready but has a long way to go.
McDade, Carl. Hiveminds (2008). Articles>Content Management>Software>Drupal
