# Share-Nothing architecture

**URL:** <https://www.ruby-forum.com/t/share-nothing-architecture/129179>\
**Category:** Rails\
**Created:** [February 15, 2008, 5:14am UTC](https://www.ruby-forum.com/t/share-nothing-architecture/129179 "2008-02-15T05:14:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ayyanar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/82dd89/32.png) [@ayyanar](https://www.ruby-forum.com/u/ayyanar)\
**Post date:** [February 15, 2008, 5:14am UTC](https://www.ruby-forum.com/t/share-nothing-architecture/129179/1 "2008-02-15T05:14:39Z")

</div>

In this forum, people are talking about share-nothing architecture. I  
don’t understand what this term means and how this improves the  
scalability

---

<div class="post-metadata">

**Author:** ![ayyanar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/82dd89/32.png) [@ayyanar](https://www.ruby-forum.com/u/ayyanar)\
**Post date:** [February 15, 2008, 8:39am UTC](https://www.ruby-forum.com/t/share-nothing-architecture/129179/2 "2008-02-15T08:39:08Z")

</div>

“Share Nothing Architecture” is a common pattern for scaling out Web  
applications.

Generally speaking, the idea is to remove dependency between the scaling  
units, which in the case of a Web application means the Web Servers.  
Once these units become independent from each other, you can easily  
scale them just by adding more units. You can then load-balance the  
incoming requests among the different Web Servers.

[http://www.zefhemel.com/archives/2004/09/01/the-share-nothing-architecture](http://www.zefhemel.com/archives/2004/09/01/the-share-nothing-architecture)  
[http://www.gigaspacesblog.com/2007/04/06/shared-nothing-architecture-redefined/](http://www.gigaspacesblog.com/2007/04/06/shared-nothing-architecture-redefined/)