lightblue Migration

lightblueMigration Strategy

● Background● Migration Process● Migration Phases● Migration Phases Detail● Q&A

Agenda

Background

Migration Process

Migration Phases

Initial State

● Current state● Existing service in production● Existing service clients● Existing datastores● Expected SLAs● Done!

Dual Write - First Phase● Existing service proxies

updates to lightblue● Updates to data are written to

legacy & lightblue datastores ● Gradually increase use of

lightblue with updates● Consistency checker verifies

data in both datastores● Clients continue using legacy

services

Dual Read - Second Phase● Data is read from lightblue &

legacy datastores ● Gradually increase use of

lightblue with reads● Existing service continues

proxying to lightblue● Updates continue to both

datastores● Consistency checker

continues to verify datastores● Clients continue using legacy

services

lightblue Proxy - Third Phase

● Data is read only from from lightblue datastore

● Updates occur only in lightblue datastore

● Existing clients continue using legacy services

● New and existing clients can access lightblue directly

● Legacy datastores decommissioned

lightblue - Fourth Phase

● End state of lightblue migration

● All data managed with lightblue

● All clients accessing lightblue directly

● Legacy service decommissioned

● Done!

Want more?

● Documentation○ http://lightblue.io

● Source○ https://github.com/lightblue-platform

● OpenShift Cart○ https://github.com/lightblue-platform/openshift-lightblue-cart

● Forums & IRC○ http://forum.lightblue.io/○ http://freenode.net/ #lightblue

Q&A