InfoQ: Twitter, an Evolving Architecture
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
Bookmark History
Saved by 15 people (0 private), first by anonymouse user on 2009-06-26
- Hexybaby on 2009-10-01 - Tags twitter , 系统架构
- Leinte on 2009-07-15 - Tags architecture , 技术架构
- Atreyu_bbb on 2009-07-03 - Tags twitter , architecture , infoq
- Joel on 2009-07-03 - Tags twitter , architecture , Performance
- Carlos_santos on 2009-07-02 - Tags via:chl , twitter , architecture
Public Sticky notes
Most of the tools used by Twitter are open source. The stack is made up of Rails for the front side, C, Scala and Java for the middle business layer, and MySQL for storing data. Everything is kept in RAM and the database is just a backup. The Rails front end handles rendering, cache composition, DB querying and synchronous inserts. This front end mostly glues together several client services, many written in C: MySQL client, Memcached client, a JSON one, and others.
The middleware uses Memcached, Varnish for page caching, Kestrel, a MQ written in Scala, and a Comet server is in the works, also written in Scala and used for clients that want to track a large number of tweets.
Highlighted by leinte
Highlighted by joel
Highlighted by joel
Highlighted by leinte
Highlighted by joel
Highlighted by leinte


Public Comment