2. 2
About
the
Presenter
๏ Chris
Haddad
๏ VP
Pla;orm
Evangelism
๏ F500/G2000
Advisor,
Cloudy
DevOps
for
Dev
guy
๏ Learn
more
about
me
๏ Follow
me
๏ @cobiacomm
on
TwiLer
๏ Blog:
hLp://blog.cobia.net/cobiacomm
๏ Profle:
hLp://www.linkedin.com/in/cobiacomm/
๏ On
Google+
too
3. Invention comes in many
forms and at many scales.
The most radical and
transformative of
inventions are often
those that empower
others to unleash their
creativity – to pursue
their dreams.
Jeff Bezos
“ “
4.
5. Tired
of
Big
SOA?
๏ Set
up
a
cross-‐funcUonal
SOA
Working
Group
๏ Develop
a
SOA
AdopUon
Plan
๏ Define
Target
Service
Por;olio
๏ Develop
a
Business
Case
๏ Plan
and
Fund
Development
of
SOA
Infrastructure
๏ Establish
New
Roles
๏ Plan
Training
and
Mentoring
for
Staff
๏ Develop
Corporate
Policies,
Guidelines,
and
Best
PracUces
๏ InsUtute
SOA
Governance
Processes
๏ Establish
New
IncenUves
that
Reward
Good
Behavior
๏ IdenUfy
Candidate
Projects
๏ Establish
PrioriUes
๏ Reassess
Your
So^ware
Development
LifeCycle
(SDLC)
5
6. Start
Small
๏ Implement
SOA
principles
on
a
project-‐by-‐project
basis
๏ Focus
on
run-‐Ume
environment
concerns
instead
of
design-‐
Ume
concerns.
๏ Successful
IT-‐driven
Small
SOA
teams
promote
consumer
adopUon
stories,
track
service
subscribers,
and
publicize
usage
growth.
6
7. PragmaUc
SOA
๏ Share
and
reuse
assets
๏ simplify
best
pracUce
adopUon
by
mentoring
teams
and
delivering
automated
governance
๏ balance
enterprise
governance
with
project
autonomy
๏ Consolidate
redundant
funcUonality
into
fewer
moving
parts
๏ offer
accelerator
packs
(i.e.
infrastructure,
tooling,
frameworks,
and
API/service
building
blocks)
๏ Conform
projects
to
common
standards
and
best
pracUces
๏ Don’t
force
common
(yet
complicated)
standards
๏ mindful
of
skill
gaps
and
adopUon
hurdles
7
12. 12
API
Strategy
๏ Embrace
the
Managed
API
๏ Make
APIs
Easy
for
Developers
to
Access
๏ Employ
API
Lifecycle
Governance
๏ Monitor
API
Use
๏ Establish
a
MoneUzaUon
Model
13. PragmaUc
API
Design
๏ Make
data
and
services
maximally
accessible
๏ Low
barrier
to
entry
๏ Extend
reach
towards
the
largest
possible
audience
๏ Make
API/service
consumable
by
the
largest
number
of
user
agents
๏ Make
data
and
services
evolvable
๏ Extend
the
system
at
runUme
๏ Alter
resources
without
impacUng
clients,
Direct
client
behavior
dynamically
๏ Make
systems
scalable,
reliable,
and
high
performing
๏ Simple,
Cacheable,
Atomic
13
18. SOA
&
REST
ReconciliaUon
๏ When
to
create
services
๏ Create
a
service
when
sharing
a
business
capability
๏ When
to
create
APIs
๏ Sharing
a
service
outside
a
domain
of
control
๏ TargeUng
the
widest
possible
reach
and
consumpUon
๏ Offering
the
service
across
naUve
web
infrastructure
๏ Maximizing
asymmetric
evoluUon
between
service
clients,
interface,
and
implementaUon.
18
20. SOA
&
REST
ReconciliaUon
๏ How
to
approach
service
and
API
governance
๏ How
services
and
APIs
impact
applicaUon
governance
20
21. 21
๏ Service
deals
with
implementaUon
๏ API
deals
with
subscripUon
(consumer)
๏ Two
very
disUnct
life
cycles
!
๏ You
don t
need
the
service
to
create
the
API...
Services
and
APIs
23. References
๏ SOA
and
API
Convergence
Strategy
and
Tac7cs
๏ Promo7ng
service
reuse
within
your
enterprise
and
maximizing
SOA
success
๏ REST
Easy:
API
Design,
Evolu7on,
and
Connec7on
๏ WSO2
and
API
Management
A
Technical
Evalua7on
Guide
23
