Membase Meetup 2010

Membase Meetup

Technical Overview and Architectural Discussion

2

Tonight

• Membase Overview

• Use Cases and Deployment Examples

• Membase Architecture

• Demo!

• Developing with Membase

• A Glimpse into the Future

What is Membase?

Before: Application scales linearly, data hits wall

Application Scales OutJust add more commodity web

servers

Database Scales UpGet a bigger, more complex server

4

Membase is a distributed database

5

Membase Servers

In the data center

Web application server

Application user

On the administrator console

6

Built-in Memcached Caching Layer

Memcached

Membase Database

Memcached

Membase Database

Memcached Mode Membase Mode

Membase development team has contributed over half of the source code to the Memcached project.

Deployment options

7

applicationlogic

OTC memcached

client

data operations

applicationlogic

OTC memcached

client

data operations

cluster operations

11211

serverlist

OTC Memcached Server

11211

Membase Server

serverlist

proxy vbucketmap

applicationlogic

OTC memcached

client

Membase Server

localhost

proxyvbucket

map

applicationlogic

NEWmemcached

client

Membase Server

vbucketmap

Embedded proxy Standalone proxy “vBucket-aware” client

Deployment Option 1 Deployment Option 2 Deployment Option 3

11210

data operations

cluster operations

11211

proxy vbucketmap

11210

data operations

cluster operations

11211

proxy vbucketmap

11210

Secure multitenant support

8

Membase data servers

In the data center


Application user


Bucket 1

Bucket 2

Aggregate Cluster Memory and Disk Capacity

Five minutes or less to a working cluster• Downloads for Linux and Windows

• Start with a single node

• One button press joins nodes to a cluster

Easy to develop against• Just SET and GET – no schema required

• Drop it in. 10,000+ existing applications already “speak membase” (via memcached)

• Practically every language and application framework is supported, out of the box

Easy to manage• One-click failover and cluster rebalancing

• Graphical and programmatic interfaces

• Configurable alerting

Membase is Simple, Fast, Elastic

9


10

Predictable• “Never keep an application waiting”

• Quasi-deterministic latency and throughput

Low latency• Built-in Memcached technology

• Auto-migration of hot data to lowest latency storage technology (RAM, SSD, Disk)

• Selectable write behavior – asynchronous, synchronous (on replication, persistence)

High throughput• Multi-threaded

• Low lock contention

• Asynchronous wherever possible

• Automatic write de-duplication


11

Zero-downtime elasticity• Spread I/O and data across commodity

servers (or VMs)

• Consistent performance with linear cost

• Dynamic rebalancing of a live cluster

All nodes are created equal• No special case nodes

• Clone to grow

Extensible• Filtered TAP interface provides hook points

for external systems (e.g. full-text search, backup, warehouse)

• Data bucket – engine API for specialized container types

• Membase NodeCode [FUTURE]

Leading cloud service (PAAS) provider

Over 65,000 hosted applications

Membase Server supporting over 3,000 Heroku customers

Proven at small, and extra large scale

12

Social game leader – FarmVille, Mafia Wars, Café WorldOver 230 million monthly usersZynga is a core contributor to and large scale user of Membase Server

After: Data layer scales like application logic layerData layer now scales with linear cost and constant performance.

Application Scales OutJust add more commodity web

servers

13

Database Scales OutJust add more commodity data

servers

Scaling out flattens the cost and performance curves.

Membase Servers

Membase - A practical path to “NoSQL” adoption

14

Use Cases

17

Use case – Ad targeting

eventsprofiles, campaigns

profiles, real time campaign statistics

40 milliseconds to come up with an

answer.

2

3

1

18

Search and Gaming Portal

Database

Membase Architecture

20

Clustering

• Underlying cluster functionality based on erlang OTP

• Have a custom, vector clock based way of storing and propagating...– Cluster topology

– vBucket mapping

• Collect statistics from many nodes of the cluster– Identify hot keys, resource

utilization

20

22

TAP

• A generic, scalable method of streaming mutations from a given server– As data operations arrive, they can be sent to arbitrary TAP

receivers

• Leverages the existing memcached engine interface, and the non-blocking IO interfaces to send data

• Three modes of operation

24

Clients, nodes and other nodes

25

Data buckets are secure membase “slices”

Membase data servers

In the data center


Application user


Bucket 1Bucket 2

Aggregate Cluster Memory and Disk Capacity

27

vBucket mapping

29

Disk > Memory

Dataset may have many items infrequently accessed. However, memcached has different behavior (LRU) than wanted with membase.

Still, traditional (most) RDBMS implementations are not 100% correct for us either. The speed of a miss is very, very important.

Membase Demo

31

Thanks!

Key-Value Patterns

33

Key-Value

(with a replica)

Items have:KeyValueExpirationFlagsCAS (more on this later)

Operations include:Get/SetIncrement/DecrementAppend/Prepend

34

Membase Datatypes

• byte[]– Does your data have 1s

and 0s?

“Any customer can have a car painted any colour that he wants so long as it is black.”

• Items do have flags– Many clients use flags

– Data type options• Google protobuf• Thrift• Avro

35

Transactions

• Lock == slow me down

• CAS operations– Optimistic locking

• Very useful with complex datatypes– Imagine two clients trying to

update a complex item

• You’re likely using CAS already... if you use a CPU

User 1

Fail!

User 2Success

36

Common Use: Sessions

• Web user sessions– Highly read, less writes in many case– Protocol advantage of memcached

• Options already for PHP, Ruby and Java

• Application state– Not necessarily “entity” style things– May be appropriate for a “cache” pool

37

Common Use (cache): Rate Limiting

• Want to provide API calls into the system– Twitter search– Google search services

• Use the atomic increment– Set an item with a unique ID– Upon API request, increment

and check• HTTP 420: go away and come

back later

Your Users

Your App

¡Ouch!

Looking Ahead: NodeCodeFrank Weigel, Membase

39

Beyond key-value • Indexing/Range Queries• Advanced Data Structures• Sub-object direct manipulation

Validation and In-flight transformation• Block mutations failing validation• Enrich or transform objects

Connectors (Integrate easily with other systems)• Solr• Hadoop• MySQL

NodeCode – Motivation

40

NodeCode - What is it?

Method for extending & customizing Membase

Separate code modules

Defined interface to datapath and cluster manager

Notification on events• Synchronous• Asynchronous

41

Simple• Packaged modules for easy install and enable• Library of “off the shelf” modules• Module monitoring• Straight forward development and debugging

Fast• Low latency/high-throughput• Per-bucket process isolation• Don’t break data manager performance/correctness

Elastic• Automatically migrate and instantiate on rebalance• Provide support for migration of internal data• Leverage native Membase engine for internal data

storage

NodeCode – Drivers

42

Block-level architecture

43

Java only– jar format

Must implement minimal module API• Initial module startup• Module removal• Association with bucket

NodeCode library helper functions• Register synchronous & asynchronous listeners/callbacks• Register protocol extension/callbacks • Register rebalance callback• Register cluster manager event callbacks• Membase data access

NodeCode 1.0 Plans

45

Q&A

46

Attributions

• http://commons.wikimedia.org/wiki/File:Flag_of_China.png

• http://commons.wikimedia.org/wiki/File:Flag_of_South_Korea.svg

• http://commons.wikimedia.org/wiki/File:Flag_of_Japan.svg

http://commons.wikimedia.org/wiki/File:Flag_of_China.png



Membase Meetup 2010

Technology

Transcript of Membase Meetup 2010