Use merb!  Just kidding.

Componentized does not mean parallelized.

Think about it this way.  Merb2/Rails3 will be defined as a standard
for interaction between components.  The relationship between those
components however is 1-to-1.

Even in the event that Rails becomes mountable (the way merb can be,
via slices), there is still a master host app which is incharge of how
things run.  Parallelizing a web framework is an all together
different matter.  :)  And tbh, that's sort of how large scale
deployments work anyway.  You've got a set of app servers, a database
server (or several if you have something like mysql_proxy set up), and
you can increase the number of app servers you need (since they're
interchangeable).

Glad to see that people are thinking about the implications of the
merge!

-Ted

On Jan 8, 5:42 pm, johnswolter <[email protected]> wrote:
> One suggestion I've been thinking about is to make the router into an
> easily replaceable plug-in, if you will.  I can imagine all kinds of
> reasons to have special purpose and feature routers.
>
> Maybe this plug-in idea could be for the whole product.  Every core
> part of Rails would be a plug-in.  Rails then would be defined as a
> structure frame.  This would allow a totally distributed and failsafe
> runtime architecture. It would allow all the core modules to be
> replaced for any purpose.
>
> A site architecture, for example, could be designed using Amazon Web
> Services virtual servers creating execution nodes on demand with
> distributed Rails loosely-coupled plug-in parts running and
> communicating as needed.  A Rails site would then be completely
> dynamically part-wise scalable to any size as needed.  It would be
> swarms of plug-ins working to achieve site goals.
>
> Notice a tightly coupled version on a single machine could still be
> very fast.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" 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-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to