StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4611299
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-01-06T02:43:47.013
FavoriteCount
0
LastActivityDate
2012-08-03T02:10:22.923
LastEditDate
2012-08-03T02:10:22.923
LastEditorUserId
1288
OwnerUserId
372679
ParentId
732648
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I've worked on a similar problem, although Spring was not involved. We developed pointing against a local instance of MySQL (each developer had one on their box), and the production system was a Master/Slave replication ring. We actually went a step further and co-located the application server with the database server, so there was a four-node cluster at both the application and database level. Our application ran in JBoss. It was fairly light, but did have some serious clustering at the application server level. With all that, we were able to get upwards of 300 requests/second, and sometimes close to 1000 requests/second (depending on the application processing). The database was never a bottleneck - even at those rates, we rarely saw the connection pool go above 5 connections. In both cases (mine and yours), since the JDBC URL points to the local server, there isn't really any functional difference from the perspective of the application. I had to play some interesting configuration games with the auto-increment setup to keep data from getting stepped on; if you only have a single point of deployment (and therefore one point of access to the MySQL instance(s)), you shouldn't need to worry about any of that. So, no code changes, and no configuration changes. It'll just work. Under standard conditions, the fact that you're backed by a Master/Slave instance pair or a cluster won't make a difference, as you'll most likely be pointing at either the Master or the MySQL instance fronting the cluster (in MySQL, the cluster is behind one or more database servers, replicating data). What kinds of load are you looking to handle? MySQL has been <a href="http://blogs.oracle.com/realneel/entry/mysql_scalability_on_nehalem_systems" rel="nofollow">benchmarked</a> in the past at >1000 TPS, but the results tend to vary based on the underlying system characteristics (memory, CPU cores, processor speed), your application's responsiveness and concurrent threads.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMySQL Cluster (Master/Slave) and Hibernate
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBill the Lizard
UserOwnerUserId
1. USmlschechter
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.