InfoQ Homepage Presentations Decomposing Twitter: Adventures in Service-Oriented Architecture
Decomposing Twitter: Adventures in Service-Oriented Architecture
Summary
Jeremy Cloud discusses SOA at Twitter, approaches taken for maintaining high levels of concurrency, and briefly touches on some functional design patterns used to manage code complexity.
Bio
Jeremy Cloud is the Tech Lead of the Tweet Service team at @twitter, and oversees one of Twitter's core infrastructure services. His team is responsible for ensuring the scalability and robustness of the tweet read and write paths.
About the conference
Software is Changing the World. QCon empowers software development by facilitating the spread of knowledge and innovation in the developer community. A practitioner-driven conference, QCon is designed for technical team leads, architects, engineering directors, and project managers who influence innovation in their teams.
Community comments
Adventures in Service-Oriented Architecture
by Nick Hrycan,
Deployment of changes that span across services
by Aniket Bhatnagar,
Transcript?
by FERNANDO CHAVES,
Adventures in Service-Oriented Architecture
by Nick Hrycan,
Your message is awaiting moderation. Thank you for participating in the discussion.
very interesting stats on twitter use and helpful lessons learned from the evolution of the twitter architecture
Deployment of changes that span across services
by Aniket Bhatnagar,
Your message is awaiting moderation. Thank you for participating in the discussion.
I was thinking that one solution could be to version the services. While discovering services, a dependent service must specify a version. Finagle could keep track of version and could support multiple versions of services discover-able at the same time.
Also, does something like Akka/Actor system solve this problem by perhaps versioning messages?
Transcript?
by FERNANDO CHAVES,
Your message is awaiting moderation. Thank you for participating in the discussion.
Transcript?