Over the last two years at LinkedIn, we have been working on a distributed key-value database called “Venice.” Venice is designed to be a significant improvement to Voldemort Read-Only for serving derived data. We’ve built out the rest of the functionality to complete the dream that motivated the construction of Venice: the ability to consume data from both...
Venice Articles
-
- Topics:
- Performance,
- Venice
-
We build a lot of our own infrastructure systems here at LinkedIn. Many people have heard of Kafka, our distributed message buffer. We also run various databases, blob stores, and stream and image processing systems, all of which we develop, deploy, and maintain in-house. One of the systems we've been working on recently is Venice, a distributed derived...
- Topics:
- Venice,
- Craftsmanship,
- Distributed Systems
-
Background Like many internet companies, LinkedIn has faced data growth challenges. Naturally, distributed storage systems became the solution to handle larger volumes of data and queries per second (QPS). But, aside from scaling issues, the variability in access patterns also grew quickly. For example, some scenarios require no more than simple put/get...
- Topics:
- Venice,
- Distributed Systems,
- Cluster Management,
- helix