mike | Shared With: Everyone - 9 days ago | counter, appengine, scalability, sharding
mike | Shared With: Everyone - Aug 28 2008 | xmpp, twitter, scalability
Quoted: A component is a trusted piece of an XMPP server that can send and receive arbitrary stanzas. Components speak a different protocol to communicate with the server. Because the name of a component is a domain (example: arbiter.chesspark.com), a component can pretend to be many users. Any stanza addressed to user@component.server.com will be delivered to component.server.com no matter what the value is of ‘user’.
mike | Shared With: Everyone - Jun 17 2008 | twitter, data center, scalability
Related Content from Around Faves
-
7 FaversViewed: 9 TimesQuoted: Twitter is a great service, but it would be nothing without the other sites, tools, and apps that help you ...
- mike - Sep 03 20081 FaverViewed: 5 Times
- mike - Aug 25 20081 FaverViewed: 8 Times
data center
-
Nothing too surprising here...but that's what makes it useful. Helps you understand the free tools that are generally used in operating scalable Web services.
1 FaverViewed: 14 TimesQuoted: Ask Ron - our Systems Engineering Lead - the exact number of servers we have in production and he’ll probably respond with, “I don’t honestly know.” I can say we’ve got dozens of web servers and dozens more DB servers. I can say with certainty it takes six specialized graph database servers to run the Recommendation Engine and we have another six to ten machines that serve files from MogileFS
- derek - Aug 21 20081 FaverViewed: 10 Times
- mike - Jun 17 20081 FaverViewed: 3 Times


