A gem that allows you to use data access using plastered mysql databases while maintaining the use of Activerecord

Question

This is a relatively complex issue that I think of, so please suggest changes or comments in parts that you are not aware of. I will update and repeat based on your comments

I am thinking of developing a rail pearl that makes it easy to use plastered tables, even if most of your data is stored in relational databases. I find this to be similar to the concept used in Quora or Friendfeed when they hit a wall scalable with traditional mysql, with most potential solutions requiring massive migration (nosql), or just being very painful (completely sticking w) p >

• http://bret.appspot.com/entry/how-friendfeed-uses-mysql
• http://www.quora.com/When-Adam-DAngelo-says-partition-your-data-at-the-application-level-what-exactly-does-he-mean?q=application+layer+quora+ adam +

Essentially, how can we continue to use MySQL for many things that are really good on it, but allowing parts of the system to scale? This will allow someone to start using mysql / activerecord, but hit the scaling to easily scale parts of the database, which makes sense.

For us, we use Ruby on Rails in an entrenched database and store drops of JSON in them. Since we cannot do joins, we create tables for relationships between objects.

For example, we have 10 different types of objects. Each object can be linked to each other using large relationship tables.

. (Id1, Id2..., type), JSON.

• Id, type, {json data}
• Id1, Id2, type {json data}
• Id1, Id2, Id3, type {json data}

- (, , , )

: , , , ..

, - , , , ,

? , , .

Answer 1

- . BEA, , , TUXEDO (TUXEDO == UNIX Extended ). TUXEDO - TPC-C Unix.

WRT , , . , , , . ( RoR) , .

, CONNECTION , , , . "" , , , , , , .