Главная
Study mode:
on
1
Introduction
2
USING MANHATTAN
3
ADOPTION
4
BUILDING NEW FEATURES
5
ARCHITECTURE: DATA MODEL
6
ARCHITECTURE: PARTITIONING
7
ARCHITECTURE: MESSAGING
8
ARCHITECTURE: CONSISTENCY
9
BENEFITS OF EVENTUAL CONSISTENCY
10
WHEN IT'S NOT ENOUGH
11
ADAPTING ARCHITECTURE
12
RESULTS
13
A DIFFERENT CONSISTENCY MODEL
14
A DIFFERENT TOPOLOGY TRANSITION
15
A DIFFERENT DEFINITION OF TIME
16
WHAT THE USER SEES
Description:
Save Big on Coursera Plus. 7,000+ courses at $160 off. Limited Time Only! Grab it Explore Twitter's primary distributed key-value store, Manhattan, in this 40-minute conference talk from GOTO Chicago 2016. Dive into the general architecture of the storage system, focusing on motivations, tradeoffs, and flexible database consistency levels. Learn about Manhattan's adoption, data model, partitioning, messaging, and consistency architecture. Understand the benefits of eventual consistency and when it may not be sufficient. Discover how Twitter adapted the architecture to address challenges, and examine different approaches to consistency models, topology transitions, and time definitions. Gain insights into the user experience and the results of implementing these changes in a large-scale distributed system.

Providing Flexible Database Consistency Levels with Manhattan at Twitter

GOTO Conferences
Add to list
0:00 / 0:00