An eCommerce Refactor | Engine Yard Blog

An eCommerce Refactor: Cleaning up a Common Pattern in a Rails eCommerce App

“We can’t add any more features”, I said to Cillian. We had reached that point when building a web app using Rails that if we added another line to that controller, I couldn’t help but feel the whole thing would come crashing down, like placing the last block in a game of Jenga. “We need to refactor.” The code in question was extremely common code: handling customer payments. Like many, many eCommerce setups out there, we wanted to be able to accept payment by PayPal, or by credit card. Since we also wanted to support multiple stores, we wanted to accept multiple payment gateways. The purchase controller logic looked a bit like this: class PurchasesController def create @purchase = Purchase.new( params[ :purchase] ) if @purchase.free? if @purchase.confirm redirect_to @purchase else render :new end else if @purchase.paypal? redirect_to_paypal elsif @purchase.credit_card? if...

Full article: http://www.engineyard.com/blog/2012/ecommerce-rails/?eymk...