As demands on your cloud-native applications rapidly change, how can you ensure that your database is responsive and highly available? The truth is that modern applications are usually still supported by monolithic shared databases and traditional operational practices. Pivotal and Redis Labs are collaborating to bring developers more agility and autonomy with a highly available, scalable, and high performance Redis database service for their cloud-native applications. Join Roshan Kumar from Redis Labs and Kamala Dasika from Pivotal as they discuss: - How Redis Labs supports real-time use cases for the modern enterprise - How Redis Enterprise provides seamless high availability and disaster recovery for Redis applications - How full life cycle management of your apps and Redis Enterprise via Pivotal Cloud Foundry enables dynamic scale, high performance and uptime Presenter : Kamala Dasika, Pivotal and Roshan Kumar, Redis Labs

1. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
Deliver Performant & Highly Available User
Session Stores for Cloud-Native Apps
Roshan Kumar
@RoshanKumar
Kamala Dasika
@DasikaKN

2. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
Changing Model for Application Delivery
Development Deployment
Sparingly at
designated times
Ready for prod at
any time
Architecture
Abstraction
Layer
“Day 2” Ops
App Server on Machine
App on “disposable”
infrastructure
Monolithic App
Microservices /
Composite app
Linear / Sequential
Short cycles, test
driven, iterative
Many tools, ad hoc
automation
Manage services,
not servers

3. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
The Cloud Native Applications Journey
RUNS ON
LEGACY IT
RUNS ON
PIVOTAL CLOUD
FOUNDRY
RUNS WELL ON
PIVOTAL CLOUD
FOUNDRY
RUNS GREAT ON
PIVOTAL CLOUD
FOUNDRY
Your Exis*ng Apps
Running on Current-Era
Stacks Supported by Time-
Tested People and Process
APPS REPLATFORMING
Suitable Apps Moved to
PCF with Minimal Code
Change; BeKer Ops Thanks
to PlaLorm Automa*on
OPS & ORG TRANSFORMATION
Legacy Apps Refactored
Using 12-Factor Principles
and Modern SoRware
Process (TDD, CI/CD),
Op*mized for PCF
Cross-Func*onal Teams
Delivering Con*nuous
SoRware Updates Into PCF
End-to-End Through
Modern Principles
APPS MODERNIZATION
GREENFIELD, CLOUD
NATIVE APP
DEVELOPMENT

4. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
I. Codebase
One codebase tracked in SCM,
many deploys
II. Dependencies
Explicitly declare and isolate
dependencies
III. Configuration
Store config in the environment
VI. Stateless processes
Execute app as stateless
processes
V. Build, Release, Run
Strictly separate build and run
stages
IV. Backing Services
Treat backing services as
attached resources
IX. Disposability
Maximize robustness with fast
startup and graceful shutdown
VIII. Concurrency
Scale out via the process
model
VII. Port binding
Export services via port binding
XII. Admin processes
Run admin / mgmt tasks as one-
off processes
X. Dev/prod parity
Keep dev, staging, prod as similar
as possible
XI. Logs
Treat logs as event streams
12-Factor Application*
* First introduced by Heroku

5. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
“Stateless” Applications
Execute app as stateless processes
Stateless Processes should not store internal state
Any necessary state is externalized as a backing service
Share
nothing
Data needing to be shared should be persisted
Use local memory or the local file system only as a single transaction
“scratchpad”

6. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
The Platform Difference
§ Provision & Deploy Reliably
- Same experience, many clouds

7. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
The Platform Difference
§ Prefabricated & “Disposable”
Infrastructure
- No more managing individual servers
for each type of service
- Add monitoring, security, whatever
needed on every VM by default
Pivotal Cloud Foundry
vSphere Amazon Azure
PCF
Elastic
Runtime
Others…Redis
Enterprise
Pack for
PCF
Single
Sign- On
for PCF

8. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
The Platform Difference
§ Consistent role-based access across
teams
- Ensures config & credentials across Dev/
QA/Prod are securely isolated
- Uniform across scaled out services
Spring Cloud Config
Dev UAT Staging
Producti
on

9. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
The Platform Difference
§ Administrative dashboards
- Developer self service with operator
governance
- No need for custom work and 3rd party
tools to config, patch, update

10. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
The Platform Difference
§ Built in Scale and Health
Management
VM FailProcess FailApp Instance
Fail
VM VM
Process
VM VM VM

11. Home of Redis
Designing a Session Store with Redis

12. Redise SoluGons and Use Cases

13. 13
About Redis
Open source. The leading in-memory
database plaNorm, suppor*ng any high
performance opera*onal, analy*cs or hybrid
use case.
The open source home and commercial provider
of Redis Enterprise (Redise) technology, plaLorm,
products & services.

14. 14
Redis Uniquely Suited To Modern Apps
High Speed
Transac*ons
Caching Analy*cs Messaging
Fast Data
Ingest
Geo spa*al
Indexing
Job & Queue Time Series Search
Machine
Learning
A full range of capabili*es that simplify and accelerate next genera*on applica*ons

15. 15
Redis Powers a Range of SoluGons
Metering
IoT
Real-Gme
Fraud
Detec*on
Social Apps
E-commerce
Personaliza*on
…AND MANY MORE

16. IntroducGon to Redis Enterprise

17. 17
Redise Technology
Redis Database
Instances

18. 18
Redise Technology
Cluster Manager
Enterprise Layer
Open Source
Layer
REST API
Zero latency proxy

19. 19
Redise Technology
Enterprise Layer
Open Source
Layer
Zero latency proxy
Cluster Manager
REST API
Redise Node

20. 20
Redise - Shared Nothing Symmetric Architecture
Cluster
Management
Path
Proxies
Node Watchdog
Cluster Watchdog
Node 1 Node 2 Node N (odd number) …
Redis
Shards
Unique mul*-tenant “Docker” like architecture enables running hundreds of databases over a single, average cloud instance without performance
degrada*on and with maximum security provisions
Data Path
Distributed Proxies
Single or Mul*ple Endpoints

21. 21
Redise Benefits
Effortless Scaling Always On Availability Substan*ally Lower Costs
Simple, Seamless
Clustering. Linear scaling
ACID Compliance in Cluster
Architecture
Cluster Support for Redis
Modules
Instant Failure Recovery, No
Data loss
Ac*ve-Ac*ve Geo
Distribu*on
Stable and Predictable High
Performance
Run on Flash as a RAM
extension
Fewer resources, lower
overhead
Top notch 24x7 expert
support

22. 22
Redise: True HA for Redis
Type of outage
Essen/al features for high availability
*Auto-failover should run on same nodes as Redis deployment
Redis Labs provides all the essen*al HA features that protect against every type of outage
Process failure Node Failure Multi-node failure Network Split Zone/Rack failure Region/Cloud failure
In-memory replication Instant recovery* Instant recovery* Instant recovery*
Multi-DC/Zone replication Instant recovery* Instant recovery*
Auto-failover Instant recovery* Instant recovery* Instant recovery* Instant recovery*Instant recovery*
AOF Data Persistence Slower recovery Slower recovery
Backup(using snapshots) Slower recovery Slower recovery
Multi-region/Cloud replication Fast recovery Fast recovery

23. Session Store For PersonalizaGon

24. 24
PersonalizaGon: Different ManifestaGons
Dynamic Pricing Targeted Ads Catalog RecommendaGons
Credit Risk AnalyGcs Game Experience

25. 25
PersonalizaGon: Real-Gme Needs
Machine
Learning
Caching and Session
Store
High Speed
Transac*ons
Fast Data
Ingest
Analy*cs Job & Queue Search JSON/Geo
FUNCTIONS ESSENTIAL TO PERSONALIZATION
Dynamic
Pricing
Targeted Ads Catalog RecommendaGons Credit Risk
AnalyGcs
Game
Experience

26. 26
Is a session store not the
same as a cache?

27. 27
Cache vs. Session Store
App Cache
Data
Source
App
Session
Store Data
Source
Session start:
Load session data
Read from
cache
Missing data fetched from the
source and cached
Data wriKen to
cache and storage
Session end:
Store session data
In session:
Data read
and wriKen to the
session store
Cache is ephemeral, but should be
highly available
Session store requires
durability in addi*on to
high availability

28. 28
Designing a Session Store
Session a, 1
Session a, 2
Session a, n
Personalized
Session Data
Decouple Session Store from App Instance
• Make the app resilient to node failures
• Store more session data in in-memory databases

29. 29
Designing a Session Store
Session a, 1
Session a, 2
Session a, n
Session b, 1
Session b, 2
Session b, n
Session x, 1
Session x, 2
Session x, n
Think of: Scalability, High Availability, and Durability

30. Redis Enterprise on Pivotal Cloud Foundry

31. 31
Download Redise Pack from Pivotal Network

32. 32
High Performance Data Microservices at Your FingerGps
hKps://redislabs.com/redis-enterprise-documenta*on/quick-setup/pcf/
1. Import Redis Enterprise Pack Tile
2. Configure Redis Enterprise Pack
(server ips, availability regions,
point & click..)
3. Deploy the Redise Pack cluster

33. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
Learn more: Services Marketplace
Pivotal.io > Build > PCF Marketplace or https://pivotal.io/platform/services

34. © Copyright 2017 Pivotal Software, Inc. All rights reserved.
Deliver Performant & Highly Available User
Session Stores for Cloud-Native Apps
Roshan Kumar
@RoshanKumar
Kamala Dasika
@DasikaKN

35. © Copyright 2017 Pivotal Software, Inc. All rights reserved.