2. 2
About
the
Presenter
o Samisa
Abeysinghe
VP
Delivery
samisa@wso2.com
o Samisa
Abeysinghe,
Vice
President
of
Delivery
joined
the
company
in
September
2005.
Prior
to
the
current
role,
Samisa
used
to
be
VP
of
Engineering
and
managed
the
development
of
WSO2
Carbon
based
product
plaGorm.
3. 3
About
WSO2
o Global
enterprise,
founded
in
2005
by
acknowledged
leaders
in
XML,
web
services
technologies,
standards
and
open
source
o Provides
only
open
source
plaGorm-‐as-‐a-‐service
for
private,
public
and
hybrid
cloud
deployments
o All
WSO2
products
are
100%
open
source
and
released
under
the
Apache
License
Version
2.0.
o Is
an
AcQve
Member
of
OASIS,
Cloud
Security
Alliance,
OSGi
Alliance,
AMQP
Working
Group,
OpenID
FoundaQon
and
W3C.
๏ Driven
by
InnovaQon
๏ Launched
first
open
source
API
Management
soluQon
in
2012
๏ Launched
App
Factory
in
2Q
2013
๏ Launched
Enterprise
Store
and
first
open
source
Mobile
soluQon
in
4Q
2013
8. Challenges
of
the
SupporQng
Environment
IT and Infrastructure
● Poor Agility
● Lack of continuous integration/build and
DevOps
● Use of wrong tool stacks and
dependencies
e.g. Which library version to use?
● No consistency
External
● Too complex for 3rd party developers
● Hard to access APIs infrastructure
● No App Store/ No API Store
Governance
● Costly compliance with regulations
( HIPAA, SOX etc)
● Governance is manual hence costly and
inconsistent
● Management have no insight into
development
Environments
● Hard to create and maintain
environments
9. Enterprise
Use
Case
An
organizaQon
wants
to
provide
o
Infrastructure
that
is
o
Connected
o
Automated
o
Shared
o
To
its
app
development
team
o
With
all
useful
tools
o
Then
manage
the
applicaQon
across
its
lifecycle
10. Enterprise
Use
Case
:
ObjecQves
● Increase
developer
producQvity
● Shared
infrastructure,
ready
to
use
setups
● Reduce
the
Qme
to
provision
tools/
environments
needed
for
the
applicaQon
development
● Enforcing
best
pracQces
-‐
reuse,
dependency
management
● Increasing
collaboraQon
and
monitoring
25. ProducQvity
and
InnovaQon
● Connect
people,
systems
and
processes
● Self-‐service
nature
● Instant
response
from
infrastructure
● Integrated
developer
experience
● Increase
re-‐use
and
visibility
● CollaboraQon
26. Enterprise
Agility
● What
is
enterprise
agility
○ Sense
environmental
change
○ Respond
effecQvely
on
Qme
● What
hinders
Enterprise
Agility
○ Rigid
procedures
and
systems
○ Too
many
dependencies
and
no
governance
○ No
central
overview
which
is
synced
with
business
27. Enterprise
Agility
● What
is
required
for
enterprise
agility
○ Rapid
applicaQon
development
○ Responsive
IT
○ ElasQcally
scaling
shared
infrastructure
○ Environments
■ Ease
of
provisioning
environments
to
develop
and
test
■ Test
environments
which
are
idenQcal
to
real
environments
■ Spend
less
Qme
on
sefng
up
and
more
Qme
on
doing
actual
work
28. Governance
● Why
governance
?
● Governance
Process
■ Configurable
life
cycle
stages
■ Govern
ALM
■ Policy
definiQon
for
governance
■ Governance
using
configurable
system
flows
■ Ability
to
add
human
tasks
to
system
flows
● ReporQng
status
of
governance
acQviQes
34.
Redefines
applicaQon
development,
lifecycle
management
&
deployment
with
cloud
based
technologies
and
connecQng
all
parQes,
systems
in
an
enterprise