Super Fast Page Load Ecommerce Platforms



Agreed with above. Cheapest & easiest way is minify assets (images, css, js), caching, and Nginx instead of Apache.
 
Magento is fucking ridiculous, it does something like 500 database queries just to load a product category page.

I built my own platform using a noSQL database. ONE QUERY, MOTHERFUCKERS. Considering releasing it either as a basic hosted platform and\or standalone installation eventually.

Fuck Shopify with their transaction fees too.

I'm getting the use of 2 small Microsoft Azure virtual machines at the moment for free, that's nice for hosting.

transactions / pipelines?
 
transactions / pipelines?

Not sure what you mean by pipelines but as far as transactions go most ecommerce platforms that don't have integrated inventory tracking won't use database transactions. Most transactions are going to be atomic anyway, even if you do tie say a purchase to inventory adjustments you wouldn't want to rollback a purchase record insertion if an inventory adjustment update failed.

Financial stuff like banking or stock trading, hell yeah, relational DB all the way. But with ecommerce (at the scale greenleaves or johnmatrix is talking about) I don't see a scenario where a roll back is warranted over proper exception handling with the appropriate follow up workflow. But even NoSQL is getting ACID transactions now, RavenDB advertises as having them.
 
What are you using, Mongo, Raven, Couch or something else?

Settled on MongoDB.

Almost used Amazon's DynamoDB but ultimately decided I didn't want it to be tied to a specific hosting platform.

transactions / pipelines?

Transactions can be easily implemented in the application layer. As justo_tx said, it's not such a big deal at this scale.

This is why Magento is slow:
184232nFN.png
 
MongoDB is epic for game development so probably excellent for web apps.

For games you can use it's geospacial indexing and grab large chunks of indexes out of the db to return to multiple clients. There's a 48 hour mmo tutorial where the guy uses javascript, mongodb, node.js, and socket.io to make an mmo board game. It's pretty badass on a technical note.
 
Consider using the shopping cart as nothing more than a web service that allows you to send in orders via API. This way you can control all the elements on the page and only send / collect what you need. With AJAX you can even call and render products from the cart.
 
I get sick and tired of indian losers on linkedin pimping it likes it's the best thing ever.

I am too because none of them can actually do any competent custom work on it. It's an absolute shit show trying to hire people to customize Magento. I ran with it for over a year and went through 7 different programmers from Vworker, Odesk, Elance, referrals, friends, and then said fuck it and switched to OpenCart.
 
If you aren't caching your site in production, you are 100% doing it wrong.

Caching is kind of like slapping makeup on an ugly woman. Using Magento as an example, caching sped up the frontend considerably, but then when you want to log in to the backend and print invoices off and set items as shipped, it's back to being slow as fuck because the underlying structure is atrociously complex. No caching will fix that.
 
Magento is a bigger failure than Ruby of Fails. I hate that shit. It's slow, just to be slow. Looks pretty, but having 2 engines to run one shopping cart, come on..

Would you also say that Shopify (RoR) is comparatively slow too? Or do you think RoR is a fail for reasons other than speed?

I trialed Shopify and their transaction fees were a dealbreaker but I thought it was pretty zippy speedwise.
 
Caching is kind of like slapping makeup on an ugly woman. Using Magento as an example, caching sped up the frontend considerably, but then when you want to log in to the backend and print invoices off and set items as shipped, it's back to being slow as fuck because the underlying structure is atrociously complex. No caching will fix that.

I'm sure that's the case. A lot of times you can just throw some hardware at the problem and things will be fine (most people here bitch about performance when they're hosting on hostgator bullshit shared hosting instead of a big boy server).

Magento is a bigger failure than Ruby of Fails. I hate that shit. It's slow, just to be slow. Looks pretty, but having 2 engines to run one shopping cart, come on..

Don't criticize Rails unless you have actual experience with real production sites with it. The amount of anti-fanboys for rails is nearly as much as actual fanboys for rails, and most people on both sides don't know a single fucking thing they're talking about.
 
Would you also say that Shopify (RoR) is comparatively slow too? Or do you think RoR is a fail for reasons other than speed?

I trialed Shopify and their transaction fees were a dealbreaker but I thought it was pretty zippy speedwise.

Don't criticize Rails unless you have actual experience with real production sites with it. The amount of anti-fanboys for rails is nearly as much as actual fanboys for rails, and most people on both sides don't know a single fucking thing they're talking about.

7hMaokk.gif


I only said ROR was a fail since I saw dchuk was in here and I wanted to rustle his Jimmies. ;)

The programming language is insignificance, it's the coders/developers that's makes the language work or not.
 
7hMaokk.gif


I only said ROR was a fail since I saw dchuk was in here and I wanted to rustle his Jimmies. ;)

The programming language is insignificance, it's the coders/developers that's makes the language work or not.

Word. Shopify being slow would be for a whole bunch of reasons, Rails only being a part of it. But seeing as how a few of the Shopify guys are or have been Rails core developers, I doubt performance is an issue for them.

Give me the fastest framework in the world and I can build a piece of shit site, and give me the slowest framework in the world and I can build something snappy. Most performance issues of popular frameworks are caused by the developers, not the frameworks.

Note: Rails and Magento are not comparable. Rails is just a framework, no different than CodeIgniter or Django in the sense that it comes with nothing out of the box. Magento is more comparable to something like VBulletin in the sense that it was built to do something specific.

Now, the problem with Magento is similar to most ecommerce platform performance issues: ecommerce is a really really hard problem to solve, much less for building a generic platform solution. This makes them inherently slow. In most cases, I would assume a custom built ecommerce platform will outperform anything prebuilt, but you have to weigh the costs against the benefits there.
 
Standalone interspire shopping cart. Out of the box I have under 2 second first load times. Magento would be awesome if it wasnt soo sloooooowwwwwwwwwwwwwwww.
 
TBH, what you have now (wordpress) works just fine, you just don't have an optimized site (theme).

Regardless of what platform you use, they can all get close to a 1 second load if you optimize their performance. If you want to get into the ultra low ms then you need to pick your system carefully.
 
Here's a javascript and html5 game engine I was working on a couple years ago before moving on to c# that only draws the items in view and not stuff outside the screen.

For stress testing I made 150,000 entries in an array to draw the tiles, and a second array to store the physics. The map is 32,000 x 19,200 pixels which is huge. http://simplehotkey.com/Tiles/main.html

There's gotta be some way to do that shit with items on an ecom site. I guess whoever figures it out will be rich. I believe with ajax you can retrieve chunks of entries asynchronously.