Does anyone use Magento in production?

I have used several shopping platforms and I consider Magento to be far superior to other shopping platforms that I have used – although, at first I was pretty critical of it.<p>My initial criticisms of Magento (particularly versions before 1.4) were around its performance issues. However, they have improved this significantly and are getting better although like anything, if you want Magento to be fast and scalable you need to have some knowledge of PHP and Web Server configuration so that you can easily optimize Magento’s caching to your particular store(s).<p>Having said that, some "quick wins" I found to improve performance and scalability of Magento were:<p>Reduce HTTP Requests - Optimising your theme, cropping your images etc<p>Use a CDN<p>Enable Block Caching where it makes sense - have a look at <a href="http://www.magentocommerce.com/wiki/5_-_modules_and_development/block_cache_and_html_ouput" rel="nofollow">http://www.magentocommerce.com/wiki/5_-_modules_and_developm...</a> for more details<p>Instead of using mod_php use FastCGI to Run PHP – if you have to use mod_php turn KeepAlive Off<p>Delve into the Configuration settings &#38; disable modules which aren’t essential to your store - System -&#62; Configuration -&#62; Advanced -&#62; Advanced<p>Likewise, some other big/notable players using Magento include:<p>Warby Parker - <a href="http://www.warbyparker.com/" rel="nofollow">http://www.warbyparker.com/</a><p>Overstock Deals - <a href="http://www.overstockdeals.com/" rel="nofollow">http://www.overstockdeals.com/</a><p>Gap/Blue Navy/Banana Republic/PiperLime/Athleta – <a href="http://www.gap.com" rel="nofollow">http://www.gap.com</a>

I have several friends at a Magento consulting company. You need to do two main things:<p>1. Run Magento Enterprise on the <i>best</i> servers. Enterprise scales better with SKUs and traffic, and you don't want a lot of servers because you pay a lot per year per server for Enterprise. I'm talking about 192GB RAM and so on.<p>2. Cache everything using Magento's tools and by putting lots of Varnish servers, Memcached, balancers etc. in front of your Magento server(s). Be very careful about clearing Magento's caches because it'll probably bring your site down.

Magento is a beast, but more than capable of handling heavy load and a large set of products <i></i>if configured correctly.<p>Currently we host a 6 node enterprise cluster; utilizing varnish and memcached.<p>The biggest downside to magento is learning the platform, there are lots of quirks and oddities that tend to pop up.<p>Also beware of magento connect! It's not that most of the modules available are bad (believe me there are a bunch that are), but when you never want to use the auto-install functionality built into the admin. I have seen a few attempts where people (mostly unqualified) will go ahead and install something to get a particular feature. This ends up leading to the entire installation becoming hosed.<p>(<a href="http://alanstorm.com/category/magento" rel="nofollow">http://alanstorm.com/category/magento</a>) This guy has a bunch of extremely useful information about magentos' internal functionality and is a great place to start when questions arise.<p>heres a link to a performance white paper they put out a little while back, but is still relevant.<p>From magento <a href="https://info.magento.com/PerformanceWhitePaper.html" rel="nofollow">https://info.magento.com/PerformanceWhitePaper.html</a> (they will send an email with link to download) OR download directly here <a href="http://www.filedropper.com/magentoperformancewhitepaper-eev1-91" rel="nofollow">http://www.filedropper.com/magentoperformancewhitepaper-eev1...</a>

Every experience I've had with Magento and Virtuemart has been horrible. I always got the systems to do what I wanted but it always felt like hacking. Too many hoops to jump through. If you have the skill, I would make a system that does exactly what you want.

1. Resource hog<p>2. Bad code structure rooted in Zend Framework<p>3. Has fostered a community of developers that create poor-quality extensions or dev. shops that will bleed you dry.<p>4. Not built to work well out-of-the-box with the various caches you'll need to make it usable.<p>5. Horrible docs<p>It's not worth the headache.

It's a resource hog, suffers from XMLitis and theming is much more complex than your typical CMS without giving you any significant advantage.

Thanks for the suggestions/advice. I'll need to think seriously about whether to go with this or look for something else proprietary.

toms.com uses it.