This link has been bookmarked by 82 people . It was first bookmarked on 18 Jun 2008, by Jean-Jacques Arnal.
-
24 Mar 14
-
19 Dec 12
-
01 Feb 12
-
14 Jan 12
-
04 Jan 12
-
27 Sep 11
Jochen FrommPost that summarizes the key parts of the LinkedIn architecture. Their approach is using a central in-memory, social graph. "The Cloud" is a server that caches the entire LinkedIn network graph in memory.
-
01 Jun 10
-
19 May 10
-
27 Feb 10
-
04 Nov 09
-
11 Sep 09
-
29 Jun 09
-
24 Jun 09
-
14 Jun 09
-
05 Apr 09
-
29 Mar 09
-
05 Mar 09
-
31 Dec 08
-
12 Dec 08
-
25 Nov 08
-
09 Nov 08
-
01 Sep 08
-
11 Aug 08
-
23 Jul 08
-
22 Jul 08
Jose M AragonThis post summarizes the key parts of the LinkedIn architecture. It’s based on the presentations above, and on additional comments made during the presentation at JavaOne
-
20 Jul 08
Joaquim Rendeiro«- Can’t use just one database. Use many databases, partitioned horizontally and vertically.
- Because of partitioning, forget about referential integrity or cross-domain JOINs.
- Forget about 100% data integrity.
[... many more interesting points]»linkedin architecture scalability performance clustering design to_headlines imported-delicious
-
08 Jul 08
Brent Sordyl# 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 -
04 Jul 08
-
03 Jul 08
-
02 Jul 08
-
01 Jul 08
-
21 Jun 08
-
20 Jun 08
-
19 Jun 08
-
18 Jun 08
-
13 Jun 08
-
12 Jun 08
-
10 Jun 08
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.