|Drupal CMS Strengths and Weakness?|
Can someone help please, is drupal good for a very large site?
I am thinking to use Drupal for my new site which is going to be a news site, ever growing with news stories.
However, I realize that Drupal has a limit as to how many news stories it can remember in the database. I was thinking possibly about Wordpress, but I understand that Wordpress is not good for voting, has limitations too.
Any suggestions? Can Drupal's this weakness be overcome?
I am just starting to look into CMSs myself.
My short-take on Drupal - I can't make heads or tails of the menus, as they appear to have been designed for idiots. :)
On the other hand, typo3 appears designed for people with VERY good eyesight who are also willing to learn a whole new lexicon in order to be able to even write their first page.
Drupal's taxonomies and nodes take a while to get accustomed to. I use it on several sites and I'm still not sure about some of it. You need to play around with it a bit to get the feel for it.
|I realize that Drupal has a limit as to how many news stories it can remember in the database. |
I haven't heard of this. Drupal can run on several different databases. They're even testing out Oracle as a backend now. Where is this limitation of which you speak?
I read about the limitation in Drupal's forum. Can't find it now, but I read it.
I also read that Type3 is more complicated.
Can drupal handle a very large site?
Any CMS can handle a large site, as they almost all store their data in a MySQL database. There should be essentially no limitation on size, unless the authors have done something REALLY stupid.
If what you mean by "large" is "lots of traffic", there definately are variations.
I have test installations of Drupal, Xoops, and Typo3 on a VPS (1/9 of a dual 2200mHz AMD system). (Going to add ModX, as well - the first 3 were a snap with Installatron, ModX doesn't have an Installatron script). I also installed Plone on a local machine, which is a 2000mHz AMD X2.
If you have a control panel with Installatron, I would encourage you to do a test install of those CMSs that are available and that you are interested in, and play.
The three above were EASY installs - I completed the 3 of them within 10 minutes. MUCH better to compare them without the 2-hour time limit of that CMS comparison site, and on YOUR hardware with a known load.
BTW, Plone absolutely DRAGS compared to the others, despite the fact that it has nearly 10 times the CPU resources available to it! Plone is for masochists. You HAVE to have a caching proxy in front of it as a practical matter. Basically, you need a dedicated machine - or two - or three (for the database backend) - to run Plone effectively. (It has it's own web server, so no way you can run it on a shared site - at minimum, you need a VPS, but a VPS wouldn't have enough CPU power.)
OK, installed MODx on the VPS.
MODx running on 1/9 of a server, accessed over the Internet, beats Plone running locally on a dedicated server over a Gig-E connection hands-down.
So far, MODx is the speed demon of the bunch.
AFIK, there is no limit to how many stories you can run on a Drupal site.
Some pretty big sites - the Onion, MTV UK - run on Drupal.
When you get a huge user base, you have to do some stuff to keep performance at acceptable levels. The Lullabot guys who put up the MTV site have posted some stuff, I think, about some of the things they did to deal with a lot of traffic and keep it fast. I know they talked about it at the Drupalcon in Brussels last month, and videos of the talk are or will be up.
When you get a very extensive taxonomy, you might also have performance and presentation issues. I suspect any non-static site with tens of thousands of categories and sufficient traffic would need tuning, however.
The whole taxonomy thing is kind of hard, but itīs also a way to force you think through things you ought to be thinking about before you get past the point of no return. The taqxonomy terms they use are academic terms, but once you get used to them they make sense. The first few days with Drupal are not, however, all that easy.
The best thing about Drupal, if you have long range plans to stick with the CMS you start with, is that it comes with a very strong community of really smart core developers, and allows easy extension of capabilities through its API and the existing modules. Itīs not the easiest CMS to get off the ground with, but you can go a lot, lot further with it, and I think itīs going to keep getting better for the foreseeable future.