continuing the evolution for the digital economy at marriott – couchbase connect 2016

Continuing Evolution for the Digital Economy at Marriott

Tom Vidnovic, Solutions ArchitectThomas.Vidnovic@marriott.com

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Agenda

2

Decision to Re-platform

Why Open Source and NoSQL

Why Couchbase

Project Overview

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

About Us

3

Delivering excellent service for almost a century

5,700 110PROPERTIES COUNTRIES

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

About Us

4

Better compete in the Digital Economy, but need to transform legacy infrastructure.

Core Technology Decisions

OPEN SOURCE

vs.PROPRIETARY

1RELATIONAL

vs.NoSQL

2WHERE

TOSTART

3

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

About Us

Deciding on a new data store

Transforming legacy infrastructure

Continuously evolving infrastructure

Finding more use cases

5

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

About Us

6

MARSHA CentralizedReservationSystem

10 CPU engines | 160GB of memory | 2.4K writes / second | 2M I/Os per second

$40+ BillionRESERVATIONS

99.995%AVAILABILITY

IBM z13MAINFRAME

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Decision to Re-platform

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Decision to Re-Platform

Legacy vs. distributed

Data driven vs. embedded logic

Application development costs

Infrastructure costs

Cloud strategy

8

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Why Open Source and NoSQL

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Why Open Source?

Cloud deployment

Commodity hardware

Open standards

Flexible choices

Licensing costs

10

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Why NoSQL?

Object-oriented development– JSON to Java, Documents to Objects

Scalability and High Availability– With commodity hardware

Zero downtime– Online upgrades and maintenance– SLAs approaching 99.999% uptime

Performance– High throughput, low latency

11

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Why Couchbase?

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Why Couchbase?

Large companies using it for similar use cases Performed well against competitors in a POC

Has a built-in cache Distributes data across the cluster

Easy to add nodes – horizontal scaling (no downtime!)Replicates data within a cluster

Can replicate between clusters for business continuity

13

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Why Couchbase?

N1QL

LDAP and auditing

XDCR filtering

Multi-Dimensional Scaling

Sub-document API

Certified on Docker14

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Couchbase Status and Challenges

4.1 in production, 4.5.1 planned (end of year)Key-value and views, transitioning to N1QLNow in multiple projects, enterprise standardBiggest challenges: sizing for N1QL

– Sizing for indexes– How to use primary and secondary indexes

15

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Project Overview

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Initial Success 2014 (Datacenter)

Marriott Data Center

Compute Cluster Couchbase ClusterMARSHA

zTPF

JSON DocumentsReservation Data

Internal Users

17

Single 4 Node Couchbase Cluster

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Evolving Success 2017 (Datacenter)

Marriott Data Center

Compute Cluster

Reservations ClusterMARSHAzTPF

JSON DocumentsReservation Data

Revenue Mgt ClusterAPI Cache Cluster

Marriott.com Marriott API

Revenue Mgt

Systems

Queri

es/Ins

erts

Servi

ce Ca

llsMobile

18

3 Node Couchbase Caching Cluster

6 Node Couchbase Revenue Management Cluster (N1QL Enabled)

6 Node Couchbase Reservations Cluster (N1QL Enabled)

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Cloud Technologies

Expand microservices architecture (Akka/Play)

Run microservices (and CB) in containers (Docker)

Deploy a PaaS for scalability/elasticity (OpenShift)

Implement queuing / streaming with CB (Kafka)

19

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Preliminary 2016 (Cloud)

20

4 Node Couchbase Cluster per Cloud site

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Evolving Success 2017 (Cloud)

21

5 Node Couchbase Cluster per Cloud Site (N1QL Enabled)

3 Node Couchbase Caching Cluster per Cloud Site

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Conclusions

Open source + commodity hardware– Rivals performance and reliability of mainframes– Offers more flexible data access

NoSQL is mature, entering the mainstreamCloud is not just a buzzword, becoming usefulRisk adverse are looking open source + cloudTechnologies becoming available “as a service”

22

©MARRIOTT INTERNATIONAL for Couchbase Connect 2016

Thought for the day

23

“Technology is the campfire around which

we tell our stories.”– Laurie Anderson