On Apr 4, 2011, at 11:25 AM, DavidJ wrote:
> On Monday, April 4, 2011 11:17:34 AM UTC-4, Colin Law wrote:
> I am surprised that whether scaffolding works for you or not is
> relevant.  It is certainly not appropriate for the sort of app you are
> describing.
> 
> 
> It isn't, but being new to Rails I'm uncertain what other Rails functionality 
> uses or assumes AR.  That is, if I don't use AR, what will the impact be and 
> what will be left that Rails is actually bringing to the table?
> Of course, right now, I am in the 'prototyping' phase, so scaffolding would 
> have been 'nice' is all.

Just to ask the obvious question, do you *know* whether this app will need to 
scale yet? There is a thin line between best practices and premature 
optimization. 

Generally if I'm scaling to a bazillion servers, I'm gonna be using a 
functional programming language with one or more NoSQL data store and an 
asynchronous messaging architecture with eventual consistency. If someone is 
asking me to build a first cut for a startup, I'm not gonna try to do that 
using Scala, Lift and Mongo. I'm gonna build it quickly in Rails and then I'll 
refactor performance critical subsystems - initially through caching and 
eventually through re-writing in more appropriate stacks for scaling if for any 
reason Rails isn't taking me where I need to be.

I'm a big fan of Grails, but I generally build most of my web apps in Rails 
unless I'm working with a Java shop (Groovy is less of a conceptual leap than 
JRuby) or need really tight integration with Spring, Hibernate or something 
else quintisentially Java. I find I can usually build something quicker in 
Rails.

So I'd start by just confirming that you really *have* a scale problem. If 
you're rewriting an existing app that already has substantial load, it makes 
perfect sense to be focusing on this now. If it's a start up venture (whether 
within an existing business or not), I'd focus on failing and iterating 
quickly. If your problem ends up being that the stack you started with isn't 
scaling the way you want that is a really high quality (and unfortunately a 
really rare) problem to have. 

Best Wishes,
Peter

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to