Talk:Shared nothing architecture

From Wikipedia, the free encyclopedia

[edit] Not just databases

I notice in the history that there has been some question about where this term is applicable. It originally referred just to databases, as shown in the Stonebreaker citation, but the SN term is no commonly used for PHP and Ruby on Rails web applications even when there is no database involved. The category probably needs to be broadened, but I'm not sure what to use. David 17:06, 26 April 2006 (UTC)

[edit] Rails?

I question that Rails is a shared nothing architecture. By default, it has file-based sessions, as well as a single process runner which doesn't get reset between requests. If you set a global variable in one request, it'll be there in the next (assuming you end up at the same backend). --Happygiraffe 07:45, 1 October 2006 (UTC)

[edit] Inappropriate examples

--Dnjclarke 19:16, 21 October 2006 (UTC) I agree with Happygiraffe and David. PHP and Rails are not appropriate examples of Shared Nothing architectures, and J2EE is not an example of the opposite. Programming languages are not architectures. They may lend themselves to implementing certain distributed architectures, but all the examples are flexible enough to implement any kind of architecture, be it shared memory, shared file, or shared nothing.

It's about a year later; I removed the (growing list) of popular du jour frameworks, API's and/or programming languages from "examples" of SN architecture. (Specificially removed this line: Three popular web development technologies, PHP, Django, and Ruby on Rails, all emphasize an SN approach, in contrast to technologies like J2EE that manage a lot of central state. (One wouldn't say that C or C++ "emphasizes shared-nothing, even though many (most?) SN arch implmentations are often actually implemented in C/C++?) Michael (talk|contrib) 21:59, 30 June 2007 (UTC)