Linkedin 架构

From: http://hurvitz.org/blog/2008/06/linkedin-architecture

Linedin是美国最大的职业人士网络，我也有一个帐号：http://www.linkedin.com/in/hugozhu

网站的一些数据：

Site Statistics

• 22 million members
• 4+ million unique visitors/month
• 40 million page views/day
• 2 million searches/day
• 250K invitations sent/day
• 1 million answers posted
• 2 million email messages/day

Software

• Solaris (running on Sun x86 platform and Sparc)
• Tomcat and Jetty as application servers
• Oracle and MySQL as DBs
• No ORM (such as Hibernate); they use straight JDBC
• ActiveMQ for JMS. (It’s partitioned by type of messages. Backed by MySQL.)
• Lucene as a foundation for search
• Spring as glue

今天的架构：

使用到的Java技术：

他们在实践中的一些经验教训：

• Centralizing updates into a single service leaves a single point of
  failure
• Be prepared to spend time tuning the HttpConnectionManager
  (timeouts, max connections)
• While the system was stabilizing, it was affecting all users; should
  have rolled the new service out to a small subset!
• Don’t use “Least Frequently Used” (LFU) in a large EHCache—very
  bad performance! (改用LRU–Least Recently Used)