►
From YouTube: Sponsored Keynote: Building a Bigger Tent: Cloud Native, Cultural Change and... - Bob Quillin
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Sponsored Keynote: Building a Bigger Tent: Cloud Native, Cultural Change and Complexity - Bob Quillin, VP Developer Relations, Oracle Cloud
The Cloud Native ecosystem continues to expand dramatically but many enterprises and traditional development teams are being left behind. The top two issues facing our industry are cultural change for developers and complexity – thus we need to find ways to build a bigger cloud native tent that is more inclusive of modern and traditional applications, cloud and on-premises users. This keynote focuses on the challenges and opportunities to create a more inclusive, sustainable cloud native community.
https://sched.co/MRz1
A
Hello
coupe
con
hi,
I'm,
I'm,
Bob,
Quillin
I'm,
the
vice
president
of
developer
relations
for
Oracle
cloud,
and
today
I'm
going
to
focus
my
time
on
ways.
We
can
all
build
a
better
bigger
cloud,
Native
community,
especially
for
enterprise
developers,
we're
living
in
what
is
arguably
now
a
golden
age
for
developers.
Devops
has
changed
how
we
develop
and
deploy
open-source
has
democratized
what
platforms
we
use
and
the
cloud
has
supercharged
where
we
run
those
applications
but,
as
we
all
know,
as
you
reach
for
that
golden
idol,
it's
never
that
easy
right.
A
So
their
boulders
ahead.
Many
many
challenges
and
those
challenges
are
becoming
more
and
more
people
oriented
challenges.
If
you
take
a
look
at
these
surveys,
it's
a
CN
CF
survey,
cultural
change,
complexity,
training-
these
are
all
people.
Oriented
issues
are
dominating
the
charts.
Now,
we've
gotten
really
really
good
at
solving
the
technical
issues,
security,
monitoring,
storage,
those
have
been
knocked
down
as
a
community.
The
technical
issues
seem
to
be
something
we
could
solve.
We
could
pat
ourselves
on
the
shoulder
for
that,
but
people
issues
are
really
thorny,
replacing
ingrained
practices.
A
This
is
a
gitlab
survey,
resistance
to
change
communication.
These
are
issues
that
are
people
oriented
issues
that
are
really
really
hard
to
change.
So
why
is
that?
So?
Enterprise
teams,
in
particular,
are
feeling
left
behind.
Cultural
change
is
a
long,
slow,
painful
march.
It's
a
slog
and
as
it
goes,
this
March
we're
piling
more
and
more
complexity
and
more
more
tools.
On
top
of
that
and
to
solve
that
problem,
many
folks
are
actually
choosing
a
single
cloud
strategy
which
locks
you
in.
A
Let
mr.
choice
limits
your
agility.
It
really
is
the
exact
opposite
of
an
open
approach.
So
we
need
to
do
is
build
a
bigger,
better
cloud
native
tent
one
that
is
more
open.
It
really
drives
us
to
a
multi
cloud
future,
one
that
is
more
sustainable,
which
helps
enterprise
teams,
leapfrog
complexity
would
manage
services
and
one
that's
more
inclusive
across
modern
and
traditional
applications
Enterprise
to
cloud
a
certain
open
labs
and
enterprises
going
through
that
process.
Now
and
I've
got
a
nice
video
to
show
shows
where
they
are
in
this
process
and
their
journey.
B
We
were
spending
a
lot
of
time,
basically,
maintenance
tasks.
So
at
some
point
we
decide
to
find
a
new
technology
of
something
that
was
acting
asked
to
let's
focus
on
the
maintenance
and
focus
more
on
the
developers
needed
I
started
to
work
with
kubernetes
and
to
migrate
the
WebLogic
infrastructure
to
magnificent
other
containers.
We
were
able
to
deploy
the
similar
logic
cluster
in
two
minutes
before
it
was
taking
us
at
least
half
a
day
thanks
to
this
new
tool.
That
is
what
logic
deploying
tooling.
B
We
are
basically
able
just
to
write
a
simple
clip,
config
file
and
the
script,
and
we
have
a
new
domain
in
few
seconds.
This
is
amazing
because
before
was
not
real
easy
thanks
to
kubernetes
and
some
advantages
that
too
many
things
like
the
fact
that
our
logic
in
deployment
is
more
portable.
Now
we
are
busy
investigating
our
OCI
that
have
helped
us
to
me
great
automatically
our
service
from
on-premise
to
cloud
in
case
of
disaster.
I
noticed
that
my
advice,
my
suggestion,
were:
listen
from
the
product
manager
of
what
logic
on
kubernetes.
A
That's
a
great
use
case
there
on
how
we've
gone
from
a
half-day
down
to
two
minutes
in
terms
of
deployment
time.
There's
some
pretty
strong
evidence
of
success.
If
we
look
at
some
other
use
cases
and
I'll
close
out
with
a
few
more
use
cases,
the
held
on
project
is
helping.
Java
teams
move
to
micro
service
framework
that
sits
on
top
of
cloud
native
technology
and
helps
you
move
to
kubernetes.
You
can
extend
that
to
more
broader
platforms.
A
The
FN
project
is
an
open
serverless
framework
and
growl
vm
is
a
virtual
machine
that
helps
teams
start
with
proofs
start
up
memory
and
performance
issues
perfect
for
the
cloud
also
technologies,
open
source
technology
also
helpful,
helping
database
teams
move
to
the
cloud
that
we
just
announced.
The
Oracle
cloud
service
broker
for
kubernetes,
which,
when
it
connected
to
the
autonomous
database
services,
helps
app
database
application
teams,
improve
performance,
lower
costs
and
actually
modernize
their
architecture
as
they
move
applications
from
the
database
world
out
to
the
cloud
itself.
A
So
to
close
out
really
we
did
build
a
bigger,
better
cloud
native
tent
one
that
is
more
open
and
drives
us
to
a
multi
cloud
future,
one,
that's
more
sustainable
with
managed
services
and
one
this
more
inclusive
across
modern
and
traditional
enterprise
and
cloud.
So
thank
you
all
I
invite
you
all
to
come
down
to
the
oracle.
Oracle,
booth,
learn
about
oracle
cloud
and
cloud
native,
we'll
see
you
all
around.
Thank
you.