The feasibility of using Joomla

Question

Joomla

Not at all for the sake of holivar, but for purely informative purposes.

There is a site with a very large number of visitors (~50.000/day according to GA). The site now consists of a large number of completely unrelated components running on different engines within their own subdomains. I don’t want to write crutches for interconnecting all engines by authorization and profile, but no ready-made solutions were found specifically for these purposes.

In this connection, it was proposed to use Joomla + JFusion as the main platform for the site, where to embed (like there are modules) the entire zoo of engines and resources, thereby making a single authorization.

Question: how useful is this? How safe and easy to maintain? Well, won't it gobble up a lot of resources? I ask such questions because I have no practical experience in supporting sites on Joomla, and opinions on the Internet about Joomla are very different. The main goal is to tie the whole zoo together.

Answer 1

How about Drupal with multi-site? Pomoymu, the most it)

Answer 2

It seems to me that rewriting and debugging a project of such complexity as you indicated is in any case more difficult than writing your own small OpenID in the framework of projects.

Answer 3

What, finally, did someone seriously decide to take on *.ubuntu.ru? :-)
On the merits of the question: if Joomla is used as a link plus some news, there will be no heavy load, not such a serious attendance. Again, it will be possible to work with your head and optimize everything right and left. In terms of security, Joomla's main headache is third-party components, the authors of which, in addition to the bydlocode, are weird right and left. This is what you should pay attention to. And of course all sorts of openbase_dir, disable_function, apache2-mpm-itk + mod_security, etc. and also means of Joomla itself to close.
Another question is that somehow it all needs to be put together - for example, a single 404 page, design, and so on.

Answer 4

I recently read team.ubuntu.ru/taskpool/main - that's why I made a completely reasonable assumption. :-) In general, you can make a test - deploy all this on a separate hardware or virtual machine and test a little. Give a load and see what and where will fall off.

Answer 5

In my opinion, the expediency of using Joomla not in your particular project, but in general is very doubtful - too often, almost daily and more than once, Joomla is highlighted on exploit-db.com
Here again, 10 minutes ago www.exploit-db. com/exploits/16001/

Answer 6

Will Joomla pull such a zoo ...
maybe it's better to write something more narrow-minded. on something like django?
I think even the developers can be found on the same forum, who is happy to scoff the site in a team?

Answer 7

I worked with Joomla at one time and I will tell you that it is not a very trivial task to make a common authorization for more than two components, since basically these are some kind of crafts, there is, let's say you pair the authorization of Joomla and the forum, everything seems to work, then screw the gallery and put a common Authorization and then fall in love with either a forum or a Joomla from the general authorization to fall off.
+ It is necessary to consider how to pair current users.

Answer 8

It depends on how many pieces you have, if two or three, then it can and costs, if more, then it’s not worth it.

Answer 9

State the parameters of your hosting. As far as I understand, there are no plans to move?

Answer 10

If you install Joomla with this zoo, then it's better not to hang up any more tasks on this CMS: let it work as a single login system and that's enough from it. Otherwise, the result may not please you.

Answer 11

Interest Ask. To be honest, I’m racking my brains myself, because soon I’ll have to write a rather loaded portal ... I’ve been developing sites on Joomla since the release of version 1.5 and I had to do a lot of interesting things with it, and I want to note that if you don’t use third-party components, then everything works pretty stably. At first, there were stories about the inability to fully use AJAX, then there were problems with SEO and caching, but in my practice I managed to solve a lot and, on the whole, I was satisfied with the system.
All problems with AJAX are solved by mootools or jquery, embed the whole thing into a template -
caching is no problem: joomla works with xCash, eAccelerator, memcached and apc - choose and test.
problems with SEO - you can always solve the jrouter class and in the end no one canceled .htaccess
See here a list of cons of Joomla straight 2 or 3 links in Google. But in my opinion, this is some kind of nonsense of a person who did not finish watching or did not understand something.
It’s enough to look at this and it’s not so scary anymore, you see.
Dear friends! Let's try to put together a really detailed and reasoned list of pros and cons.