Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
lightblue 
Migration Strategy
Agenda 
● Background 
● Migration Process 
● Migration Phases 
● Migration Phases Detail 
● Q&A
Background
Migration Process
Migration Phases
Initial State 
● Current state 
● Existing service in production 
● Existing service clients 
● Existing datastores 
● Exp...
Dual Write - First Phase 
● Existing service proxies 
updates to lightblue 
● Updates to data are written to 
legacy & lig...
Dual Read - Second Phase 
● Data is read from lightblue & 
legacy datastores 
● Gradually increase use of 
lightblue with ...
lightblue Proxy - Third Phase 
● Data is read only from from 
lightblue datastore 
● Updates occur only in 
lightblue data...
lightblue - Fourth Phase 
● End state of lightblue 
migration 
● All data managed with 
lightblue 
● All clients accessing...
Want more? 
● Documentation 
○ http://lightblue.io 
● Source 
○ https://github.com/lightblue-platform 
● OpenShift Cart 
○...
Q&A
Nächste SlideShare
Wird geladen in …5
×

lightblue Migration

Outlines process for migrating legacy SOA services to lightblue platform (http://lightblue.io/).

  • Loggen Sie sich ein, um Kommentare anzuzeigen.

lightblue Migration

  1. 1. lightblue Migration Strategy
  2. 2. Agenda ● Background ● Migration Process ● Migration Phases ● Migration Phases Detail ● Q&A
  3. 3. Background
  4. 4. Migration Process
  5. 5. Migration Phases
  6. 6. Initial State ● Current state ● Existing service in production ● Existing service clients ● Existing datastores ● Expected SLAs ● Done!
  7. 7. 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
  8. 8. 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
  9. 9. 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
  10. 10. lightblue - Fourth Phase ● End state of lightblue migration ● All data managed with lightblue ● All clients accessing lightblue directly ● Legacy service decommissioned ● Done!
  11. 11. 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
  12. 12. Q&A

×