Various people have been voicing different types of opinions about Magento. Some say that it is highly complicated and always offers an unpleasant experience. This opinion can be described as a harsh one.From the perspective of technical guy, this platform creates a good number of problems while handling bigger and advanced projects.
There is a mixed opinion about eBay’s recent acquisition of Magento. What prompted eBay to make such a decision? If you question the logic behind this acquisition, nobody can complain because this open source ecommerce platform does not support more than 200000 customers and it can be a major constraint in the future. You can easily doubt that eBay, undoubtedly one of the leading online auction systems, had some other interests in making this acquisition a reality and they may be planning to sell its own engine on this trade mark. Otherwise, the logic behind this acquisition is too complicated to digest.
Many experienced developers are of the opinion that the two-leveled framework of Magento known as Zend and Mage and, Magento core; create a lot of complications while handling big projects. When the number of visitors per minute increases, especially when it goes past 100000 per minute; you will get frustrated with the performance of this two-leveled framework. Bigger projects always have to handle more than 15,000 to 16000 visitors per minute and due to the inefficiency of Magento framework, you often have to deal with deadlocks while handling these types of projects.
Whenever you introduce changes in your core files, the support functions become inefficient to support anything that made those changes. This platform offers a solution to this issue and it has been done by providing special functionality that builds your Magento for these cases. But it is extremely difficult to maintain code of more than 20000 files and even if you neglect this aspect, it can be really laborious to restrict this change for everybody else.
Magento enterprise edition also fails to deliver and many people think that it is a good concept only to dream big. In reality, most of the modules do not work properly and finding out modules for special models of EE is also a hazardous task. The Entity attribute value (EAV) architecture used in this platform will adversely affect your flexibility and you may end up searching for hours to find the right line of code.
Every custom change causes some problems and finding an answer to this problem eats up a lot of your valuable time. It is not all advisable to do migration for products using Magento models and on the other hand; you can try to extend their model with more simplified MySQL queries by reaching Zend adapter. You may face a lot of problems and deadlocks without a nice set up and effective use of caching and, in order to process the locks faster, cache reduces the workload of database. But life becomes difficult when you get more.
In a nutshell, it can be said that Magento can be useful for small shops with 1 to 4000 users and for bigger projects; it is not at all advisable to develop on this platform