►
Description
Regardless of which cloud your applications run in, it needs to communicate to other applications within the same cloud or across public and private clouds. Web APIs have always been the lingua-franca of communication between applications. However, nuances of how APIs are published and managed can mean the difference between a highly agile software development organization, and just a pile of services that cannot communicate to each other. Ed Anuff from Apigee will discuss how to use use API Management to develop APIs that span public and private clouds.
Ed Anuff
Apigee
A
A
We
need
to
get
to
the
clouds,
plural,
and
so
you've
heard
that
all
all
afternoon
and
all
evening
multi-cloud
strategies
and
how
Cloud
Foundry
is
going
to
help
you
get
there.
There's
a
lot
of
good
reasons,
for
this
might
be
trying
to
turn
your
data
center
into
a
private
cloud,
creating
the
cloud
born
Enterprise
all
of
this
good
stuff.
A
A
Some
might
recognize
this.
The
Tower
of
Babel
also
an
ambitious
plan
to
get
to
the
clouds.
This
project
failed
due
to
polyglot
requirements.
I
was
a
monolithic
architecture
and
fell
apart
when
people
couldn't
agree
what
languages
to
use
some
people
blame,
divine
retribution,
I
blame
it
on
Hacker
News.
Some
people
felt
you
should
go
to
lists.
Other
people
were
talking
about
server-side
Swift
and
you
know
they
ended
up.
Throwing
in
the
towel.
I
think
we've
all
worked
on
IT
projects
like
this,
but
the
point
was
that
you
know
building
a
project
like
this.
A
You
break
it
into
teams,
teams
choose
their
own
communication,
styles,
their
own
ways
of
working
and
so
on.
There
has
to
be
a
way
to
to
bring
that
all
together.
So
what
does
this
have
to
do
with
api's?
Well,
your
teams
are
building
apps
and
apps
talk
to
each
other
via
api's
and
left
your
own
devices.
A
These
are
actually
the
challenges
that
happen
when
you
try
to
make
your
api's
consistent
work
between
apps
and
really
when
you
look
at
the
multi
cloud
problem,
it
really
is
at
its
heart
an
API
problem.
So
what's
the
solution
to
this?
Well,
some
of
you
probably
have
heard
of
API
management.
It's
a
category
I
know
many
of
you
are
running
different
types
of
of
API
management.
Software
in
my
zest.
To
get
up
here,
I
forgot
to
introduce
myself
at
Anna
from
Apogee.
We
do
make
API
management
software.
A
That's
why
I'm
talking
to
you
about
this
today,
but
API
management
does
seek
to
to
solve
these
types
of
things
in
one
way
or
another.
You
will
solve
these.
You
will
need
a
way
to
either
have
common
security
authentication
between
all
of
your
workloads,
all
of
your
apps
that
are
exposing
api's.
You
can't
have
ten
different
authentication
schemes.
You
will
need
a
way
to
to
document.
A
Within
cloud
foundry
there's
now
a
capability
called
route
services
and
there's
a
number
of
good
sessions
that
are
on
the
conference
agenda
that
I
encourage
you
to
attend
to
talk
about
what
routes
out
services
are
and
why
they're
relevant
to
api's.
But
in
a
nutshell,
what
this
is
about
is
allowing
you
to
plug
into
the
Cloud
Foundry.
Go
router,
intercept
your
HTTP
traffic
in
this
case,
specifically
your
API
traffic
and
then
doing
all
of
these
key
requirements
for
being
able
to
go
and
authenticate.
A
It
defeats
the
whole
purpose
of
doing
them,
so
with
that
in
mind,
your
goal
is:
don't
let
your
infrastructure
projects
turn
out
like
the
Tower
of
Babel.
The
original
failed
infrastructure
project
figure
out
how
to
do
your
API
is
right.
If
you
use
this
opportunity
at
the
conference
to
learn
about
route
services,
learn
about
how
API
management
can
work
within
Cloud
Foundry,
every
one
of
your
teams
can
do.
Api
is
right
and
you
will
be
able
to
avoid
this
fate.
Thank
you.