Reputation: 5693
I'm tasked with building a large eCommerce site for a retailer. We are using packaged software for it. The package is difficult to tailor, and inflexible, but it scales on a solidly tested java application.
In the background though, I've been considering trying to use this as a reference workload to build a custom Ruby on Rails eCommerce application - just for interest sake and to learn the framework. But before I start too far down the path, I guess I'm looking for a high level is determination if it's even possible to reach this type of workload with ROR.
The app would have to capture about 2000 orders per hour, but each order is big, so would be processing about 140,000 line items per hour. Concurrent customers are relatively straightforward, at about 5,000 active in an hour. But browse to shop is high, with a conversion of about 45% of customers coming to the site to shop so majority of processing is order capture rather than search & browse of most sites.
So my question is, what is "large workload" when it comes to ROR? Is this a feasible NFR to meet with a ROR application? What considerations should I make?
Upvotes: 0
Views: 410
Reputation: 8288
Actually, as a web framework, RoR does not impose any restrictions on the work load limit.
The work load limit depends on:
Upvotes: 3