StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14792340
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-09T22:29:57.847
FavoriteCount
0
LastActivityDate
2013-02-09T22:48:35.730
LastEditDate
2013-02-09T22:48:35.730
LastEditorUserId
495593
OwnerUserId
495593
ParentId
14552519
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Not sure if I quite understand your complete use case. Is it that you simply want to distribute reads/writes across the different databases for different API calls ? If it is a small application why don't you have all 3 applications on site 1, site 2 and site 3 connect to the same database instance ? Following options: <ol> <li>Master Slave Replication In your case you would have 1 master db and 2 slave db. Data will be read and written to the master db but will be replicated to the slaves. You can then configure your rails application to do reads across selected databases. You can use <a href="https://github.com/tchandy/octopus" rel="nofollow">Octopus</a> to distribute writes/reads between slaves and master. <blockquote> When using replication, all writes queries will be sent to master, and read queries to slaves. </blockquote></li> <li>MySQL Cluster I have not used MySQL cluster yet but should be using it soon. If your requirement is to distribute reads/writes across all the databases while having the data remain consistent across all nodes MySQL cluster looks like a good candidate. The data is distributed across a pool of data nodes. Every MySql server has access to all the data nodes and as result when a server within the cluster changes data example by inserting rows, this new data is immediately accessible and seen by the other MySql servers in the cluster. See more here <a href="http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-overview.html" rel="nofollow">MySql Cluster</a></li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POReplicated Master/Slave Servers and databases
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSkillachie
UserOwnerUserId
1. USSkillachie
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.