StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9359598
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-20T10:27:12.360
FavoriteCount
0
LastActivityDate
2012-02-20T10:27:12.360
LastEditDate
LastEditorUserId
0
OwnerUserId
263052
ParentId
9306714
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
What Tim means is that this is not an apples to apples comparison. If you are solely concerned with the performance of a single point to point connection to transfer data, a direct link will give you a good result (although DIY is still a dubious design decision). If you are building a system that requires the transfer of data and you have more complex functional requirements, then a broker-based messaging platform like ActiveMQ will come into play. You should consider broker-based messaging if you want: <ul> <li>a post-office style system where a producer sends a message, and knows that it will be consumed at some point, even if there is no consumer there at that time</li> <li>to not care where the consumer of a message is, or how many of them there are</li> <li>a guarantee that a message will be consumed, even if the consumer that first handle it dies mid-way through the process (transactions, redelivery)</li> <li>many consumers, with a guarantee that a message will only be consumed once - queues</li> <li>many consumers that will each react to a single message - topics</li> </ul> These patterns are pretty standard, and apply to all off the shelf messaging products. As a general rule, DIY in this domain is a bad idea, as messaging is complex (see <a href="http://www.ohloh.net/p/activemq/estimated_cost" rel="nofollow">http://www.ohloh.net/p/activemq/estimated_cost</a> for an estimate of how long it would take you do do same); and has many existing implementations of various flavours (some without a broker) that are all well used, commercially supported and don't require you to maintain them. I would think very hard before going down to the TCP level for any sort of data transfer as there is so much prior art.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the performance overhead of Apache ActiveMQ vs. raw sockets?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJakub Korab
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.