This document discusses planning a cloud strategy and provides guidance on key considerations. It recommends having a strategy for using cloud services, federating cloud identities, developing applications in the cloud, and running applications in the cloud. It also discusses how containers and Kubernetes can help manage applications across cloud environments and how WSO2 products like the API Manager, ESB, and Identity Server can help with integration, identity management, and running applications on Kubernetes.

1. Planning
Your
Cloud
Strategy
S.Uthaiyashankar
VP
Engineering,
WSO2
shankar@wso2.com

2. Why
We
Need
Cloud
Strategy?
Picture
Credit
:
h=p://dilbert.com/strip/2009-­‐11-­‐18

3. Cloud
Strategy
• Using
Cloud
Services
• FederaLon
of
Cloud
IdenLLes
• Development
in
Cloud
• Running
Your
ApplicaLon
in
Cloud

4. Cloud
Services
• Tons
of
Useful
Services
• Standing
on
the
Shoulders
of
Giants
• You/Your
Customers
might
already
using
some
of
these
services

5. Cloud
Iden::es
• Increased
numbers
of
Social
IdenLLes
• Gartner
predicts,
by
the
end
of
2015,
50%
of
all
new
retail
customer
idenLLes
will
be
based
on
social
network
idenLLes
• Your
users/employees
already
have
one
or
more
social
idenLLes

6. Applica:on
Development
• Agile
• API
Driven
• Polyglot
(language,
technology,
data)
• Requires
Quick
Releases
• Supports
Long
Tail
of
Apps

7. Applica:on
Run:me
• Microservices
Architecture
• Unpredictable
Load
• Varied
scalability
between
components

8. Relationship with IT
2 days to
create a
user
½ day to
reset a
password
3 days to
create a
database
1 week to
provision
a VMruntime
policies
devops
policies
Picture
Credit
:
h=p://web.zizinya.com/blog/

9. This
oAen
leads
to
Shadow
IT…

10. What
You
Need?
• Self
Service
• Heterogeneous
RunLmes
• Polyglot
Programming
Model
• Workflow
Driven
• API
Driven
• Accept
CreaLve
ExperimentaLon
• Low
Cost
Development,
RunLme
Environments

11. Rise of the Containers
Enterprise Docker, Adrien BLIND, Aurelien GABET, Arnaud MAZIN

12. And
the
Fancy
Cousins…
torical usage, and key network statistics.
These various parts can be distributed across different machines for
scale or all run on the same host for simplicity. The key difference
between a master and a node comes down to who’s running which
set of processes.
Figure 2-2. The Expanded Kubernetes Layout
Picture
Credit
:
Kubernetes
:
Scheduling
the
Future
at
Cloud
Scale

13. And
the
Madness
Con:nues…
Urbernetes Control Plane
Kubernetes Cluster 1
GCE
Kubernetes Cluster 2
AWs
Kubernetes Cluster n
Private
Standard
Kubernetes API
Urbernetes API
Policy Engine
Auth
Desired
Federation
State
MigraLon
Controllers
https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/federation.md

14. How
WSO2
Helps?

15. WSO2
API
Manager
• Controlling
which
cloud
APIs
can
be
used
by
the
applicaLons
• IdenLfying
which
applicaLons
are
using
what
APIs
and
how
much
they
are
using

16. WSO2
ESB
and
Connectors
• IntegraLon
with
cloud
services
• Cloud
to
Cloud
and
Cloud
to
Enterprise
IntegraLons
• ESB
Connector
Store
:
hKps://store.wso2.com

17. WSO2
Integra:on
Cloud
• Managers
and
executes
integraLon
templates

18. WSO2
Iden:ty
Server
• SSO
and
IdenLty
FederaLon

19. WSO2
Iden:ty
Server
• IdenLty
Provisioning

20. Running
WSO2
Products
on
Kubernetes
Pod 1 Pod 2
Manager Cluster
Service
Pod 3 Pod 4 Pod n
Worker Cluster
Services
Manager
Replication
Controller
Worker Replication
Controller
Client
Gov
Reg
Conf
Reg
User
Store

21. WSO2
Private
PaaS
IaaS Provider 1
Kubernetes Cluster 1
Load
Balancer
1
Load
Balancer
2
Load
Balancer
n
Central Load
Balancer
N1 N2 N3 NnM
Kubernetes Cluster 2
N1 N2 N3 NnM
Kubernetes Cluster n
N1 N2 N3 NnM
IaaS Provider n
Client

22. WSO2
App
Factory

23. WSO2
Cloud
(hKp://wso2.com/cloud)

24. Thank
You