title: Using Spider for mysql
body: <p>I'm looking for solution to shard my data in mysql w/o changing application code and this project shows up pretty deep in google search result.</p>
  <p>While there's not much document available about this, this seems to be a promising out of the box solution to shard ur data across many db.</p>
  <p>This is their project description <a href="https://launchpad.net/spiderformysql" rel="nofollow noreferrer">spider for mysql</a></p>
  <blockquote>
  <p>The spider storage engine enables tables of different MySQL instances to be treated like a table of a same instance. Because xa transaction and partitioning is supported, it can do decentralized arrangement to two or more servers of data of same table.</p>
  <p>The new storage engine &quot;Spider&quot; does work for its strong scalability to access other storage engine of MySQL, to idea to the most considerations are below;</p>
  <p>1:Scalability</p>
  <p>2:Faster Access</p>
  <p>3:Data Synchronizations</p>
  <p>4:Reduce The Cost</p>
  </blockquote>
  <p>It's still quite an active project (it supports mysql 5.5.14 currently) but I don't see many results on the search engine. can you guys tell me why.</p>
  <p>Since I don't have much knowledge in this field to assess this, I want to ask about advantages and disadvantages when use this kind of approach. Is the Spider storage the SPOF?</p>
  <p>Can I have multiple Spider storage, will it affect transaction committing if I do so?</p>
  <p>I need to consider this approach before making a decision to switch to MongoDB.
  My application is a write intensive app (a social network project).
  And it really needs perfect horizontal scaling in the future.</p>