There are two groups of people in CS who want to control your program’s interaction with the outside world–the operating system people and programming language people–and they are always fighting over who will have this honor. The operating system people want to provide a set of functionality that is available to any programming language, and [...]
A search exponentially faster than binary search, and a use for it.
Just came back from the 1st ACM Symposium on Cloud Computing at Indianapolis. The conference is collocated with Sigmod and lasts a day and half. A total of 7 people from LinkedIn were at SOCC and the blog below reflects the notes that we took collectively. There were three keynote speeches, all of which are [...]
We finally added some documentation for Norbert, our open source cluster management and RPC system.
Users of Voldemort have the option of using a binary protocol for efficient network communication between clients and nodes. This is implemented on the server side using an abstraction known as a SocketServer. Previously the only implementation of the voldemort.server.socket.SocketServer used the classic thread-per-socket blocking I/O approach to handling the network communication. Recently my NIO [...]
A well-known lesson in scalability is that writes are 40x more expensive than reads and if your application becomes write-intensive as it is easily the case when you are dealing with sufficiently large number of users, you will be in trouble if you don’t design to scale. For example, if you are using MySQL, you [...]
Tagged hadoop, lookery, read-onlyMany of LinkedIn’s products are critically dependent on computationally intensive data mining algorithms. Examples of these include some modules like People You May Know, Viewers of This Profile Also Viewed, and much of the Job matching functionality that we give to people who post jobs on the site. To support these data-intensive products we have [...]
Tagged hadoop, linkedin, read-onlyBy popular demand. Fork us.