►
From YouTube: CNCF End User Tech Radar, November 2020 - Cheryl Hung, Jackie Fong, Mya Pitzeruse, Smaïne Kahlouch
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
CNCF End User Tech Radar, November 2020 - Cheryl Hung, CNCF; Jackie Fong, Ticketmaster; Mya Pitzeruse, Indeed; Smaïne Kahlouch, Dailymotion
The CNCF End User Community present the next edition of the CNCF End User Tech Radar (http://radar.cncf.io/), the quarterly report that shows what end users really use and recommend. Cheryl Hung, CNCF VP Ecosystem, will lead a panel discussion with the Radar team covering what they expected going in and what they found most interesting or surprising.
https://sched.co/etSI
A
A
Basically,
what
I
do
at
cncf
is:
I
work
with
end
users
to
get
them
engaged
and
active
in
the
ecosystem
so
that
they
can
successfully
adopt
technologies
like
kubernetes
and
prometheus.
You
can
find
me
at
voiceshow
on
twitter,
and
these
are
some
of
the
companies
that
I
work
with.
So
this
ranges
from
startups
to
large
enterprises
and
all
fantastic
companies
that
are
using
cloud
native
and
I'm
very
honored
to
be
joined
by
three
of
them
here
today
to
talk
about
the
cncf
end-user
technology
raid
gun,
so
I
would
like
them
to
each
introduce
themselves.
B
Hi
everyone
I'm
jackie
fong.
I
work
at
mass
ticketmaster
for
the
last
three
years
as
their
engineering
manager
leading
their
kubernetes
platform
team
and
cicd
team
observability
and
most
recently
developer
experience
and
we
developed
the
platform
for
our
developers
to
consume,
and
recently
we
migrated
our
self-managed
kubernetes
to
eks
at
the
beginning
of
2020.
B
C
I'm
smain
I'm
a
devops
team
leader
at
dailymotion,
which
is
a
video
distribution
platform,
basically
pretty
famous
in
france
and
europe.
In
this
attribution,
I'm
leading
a
team
which
is
in
charge
of
the
cloud
native
platform.
This
this
platform
is
a
hybrid
platform,
mostly
on
premises,
and
we
have
some
stuff
on
on
cloud
and
we
are
responsible
of
the
whole
developer
experience
from
the
laptop
or
the
ci
cd
to
the
how
they
ship
their
the
application
to
the
production.
D
A
So
just
a
reminder,
the
tech
radar
is
a
way
of
assessing
upcoming
solutions
and
different
technologies.
So
the
idea
is
to
pick
which
tools
you
would
recommend
to
place
and
adopt,
in
other
words,
they're
mature
and
they're
stable
they've
been
used
by
many
different
teams.
Many
different
use
cases
or
you
could
put
it
in
trial,
which
is
to
say
that
you
know
it's
there's
some
success,
but
may
not
be
applicable
in
all
cases
or
assess,
meaning
it's
up
and
coming
or
maybe
there
are
other
solutions
for
different
use
cases.
A
C
Maybe
I
would
start
by
saying
that
I
was
wondering
how
was
the
adoption
in
the
cncf
end-user
community
in
this
particular
area,
because
this
ncf
community
is
pretty
mature
on
the
humanities
platform
and
maintaining
and
the
evolution
of
the
cuban
this
platform.
But
I
wanted
to
know
how
databases
fit
in
this
in
this
cloud
native
domain.
D
I
know
on
the
indeed
side
of
the
world
as
we
started
to
shift
more
and
more
of
our
workloads
to
the
cloud.
We
were
really
interested
in
how
people
were
running
their
databases,
whether
they
were
choosing
to
go,
manage
services
or
running
in
cluster
and
what
kind
of
some
of
the
technology
decisions
that
went
into
that
were
as
well
as
how
they
were
handling
some
of
their
scale
out.
B
Yeah
I'm
pretty
similar.
I
would
love
to
pick
the
community
spring.
We've
been
migrating,
our
on-prem
presence
to
the
cloud
on
the
database
front.
We
have
legacy
systems
running
on
oracle
and
just
looking
forward
to
get
some
insight
from
the
computer
community
and
some
experiences
to
migrate
out
of
either
oracle
or
on
to
orgo
on
the
cloud.
So
super
excited
for
this
topic.
A
A
D
B
Yeah,
I
expect
oracle,
like
I
mentioned
earlier
earlier,
to
be
up
there
as
well
and
for
most
of
the
companies
that
has
entered
information
in
there.
They
most
of
them
said
on
on
hold
or
or
or
recommending
it
to
to
be
on
hold
phased
out.
So
that
was
surprising,
but
otherwise
most
of
those
are
pretty
in
line
with
what
we've
been
using.
C
And
I
was
expecting
much
more
experiments
on
new
cloud
native
databases.
This
is
something
that
we
will
see
later
on,
but
I
want
I
wanted
to
see
because
we
worked
on
the
pocs
at
delhi
motion
to
identify
our
next
database
cognitive
database,
and
I
was
expecting
that
many
more
companies
will
do
the
same
experience.
A
A
D
A
Definitely
yeah
a
lot
of
well-known
names
up
at
the
top,
so
when
we
came
to
choosing
which
ones
ended
up
in
adopt
trial
and
assess,
I
think
these
are
just
kind
of
bucketed
like
this.
I
know
there
was
a
little
bit
of
discussion
about
some
of
these
items.
Were
there?
Are
there
any
here
that
you
use,
or
you
thought,
were
you
know
personally,
you
would
put
in
a
different
place.
C
D
A
B
Yeah
I
mean
way
more
than
mysql.
As
you
can
see
here,
we've
been,
we
migrated
off,
not
a
ticketmaster.
My
previous
place,
I
believe,
20
years
ago
we
migrated
off
of
postgres
onto
mysql
and
since
then
I've
been
working
with
mysql
almost
every
place
I
work
for,
but
recently
at
ticketmaster
postgres
came
back.
I
mean
at
least
from
a
vendor
supported
service.
They
provided
and
postgres
sql
was
the
backend.
B
A
B
That
was
a
long
time
ago,
our
main
database,
I
work
for
isp.
That
was
when
you
know
when
we
have
bought
ups
and
dsl,
I'm
aging
myself
here
and
and
basically
it
was
our
main
registration
application
and
it
was
really
heavy
at
the
time
people
were
signing
up,
left
and
right
and
supporting
postgres
sql
was
just
too
heavy
for
us
and
we're
looking
for
an
open
source
database
that
we
can
migrate
to
it.
B
Was
it
wasn't
an
easy
effort
when
I
left
they
were
still
finalizing
the
migration
and
mysql
at
that
time
worked
for
us,
it
was
super
light
and
the
operation
cost
for
mysql
is
so
much
lower
than
post
quest,
sql
and
finding
expertise.
At
that
time.
We
call
them.
You
know
dbas
right,
finding
expertise
for
mysql
at
that
time
was
so
much
easier
than
postgres
dbas.
D
A
Yeah,
in
fact,
I
think
we're
talking
a
little
bit
about
how
the
different,
how
difficult
it
is
to
move
between
databases.
So
I
think
actually
we
should
go
into
that
yeah.
So
I
asked
you
to
sort
of
come
up
with
some
thoughts
about
what
themes
or
patterns.
Did
you
see
not
just
from
the
data
but
from
your
own
experience
so
maya?
Why
don't
you
talk
about
this?
First,
one.
D
I
remember
running
math
to
try
to
figure
out
what
kind
of
like
right
workload
capacity.
We
needed
to
stay
on
top
of
our
rights
for
the
day
and
there
was
just
a
lot
there
to
take
into
consideration
and
we
ended
up
like
not
choosing
to
adopt
any
new
technologies,
but
even
in
our
move
to
the
cloud
we're
still
kind
of
considering
like
keeping
the
things
that
we're
familiar
with,
we
have
a
lot
of
operational
excellence
around
things
like
my
sql,
as
well
as
all
of
our
applications
are
programmed
against
that.
B
B
B
You
know
based
on
some
of
those
responses
and
newer
technology,
it's
sort
of
attraction
right
to
work
for
a
company
and
and
one
not
like
maya
going
to
a
startup.
It's
a
you
have
to
choose,
you
don't
want
to
choose
legacy
systems
and
technologies,
and
and
that's
why
the
newer
technologies
should
should
be
there.
I
mean
it
shows
on
our
radar
too.
So.
A
B
C
C
I
would
say
for
a
developer
to
to
build
his
application
architecture,
and
one
of
the
the
pieces
we
want
to
provide
is
to
provide
an
easy
way
to
to
boost
traffic
database
system
database
software,
and
we
are
looking
at
the
cloud
native
alternatives
in
the
in
the
market
and
we
did
pocs
last
year
in
order
to
to
choose
the
one
that
fit
our
knees,
and
we
are
pretty
happy
because
some
of
our
internal
tools
are
currently
running
in
production.
On
that
solution.
C
Yes,
well,
we
did.
That
shows
because
we
put
because
we
did
a
lot
of
performance
tests,
tests
and
reliability
tests.
We
did
cause
testing
using
the
the
tool
named
the
cause
mesh.
We
we
pushed
a
lot
the
the
solution
to
be
sure
that
it
handles
our
traffic
big
traffic,
because
we
we
we
have
the
we
have
the
target
to
to
have
a
lot
of
traffic
in
this
platform
and
and
we
made
everything
to
to
be
a
production
ready.
So
we
have
backups,
regular
backup
schedule
backups.
C
The
thai
db
operator
is
pretty
amazing
because
it
it
allows
you
to
define
really
easily
how
you
want
to
declare
your
your
your
database
and
every
and
all
the
observability
features
are
really
amazing
in
this.
In
this
solution
I
was,
I
was
pretty
surprised
by
the
maturity
of
this
solution,
because
it's
not
known
really
known,
but
when
we
did
our
tests
and
compared
to
the
other
solution,
this
is
the
one
we
shot.
A
B
Yeah,
I
mean
one
of
our
use
cases.
Our
database
is
the
biggest
one
is
on-prem
and
one
of
our
initiatives
for
our
developers
is
migrate,
their
workloads
to
the
cloud
in
the
east
region,
it's
great.
The
cloud
ac
is
pretty
close
to
our
on-prem
data
center
there.
But
on
the
west
side,
it's
it's
it's.
You
know
it's
too
far
and
we
constantly
hitting
some
latency
issues
and
that's
where
our
use
case
is
kind
of
a
little
bit
different
between
our
east
and
our
west
regions,
and
so
that's
what
we're
still
looking
into.
B
D
And
so
we
did
a
lot
of
things
like
that
when
we
were
diving
in.
I
think
when
we
were
doing
that
evaluation.
We
were
on
like
ec2
instances
and
not
necessarily
running
in
kubernetes,
but
it
was
something
that
was
like.
We,
we
kind
of
again
kind
of
take
to
heart
when
we
look
at
some
of
this
stuff
and
like
really
try
to
take
our
our
use
cases
in
this
consideration.
D
We
also
had
like
another
ephemeral
testing
type
of
effort
in
place
where
people
wanted
to
be
able
to
spin
up
kind
of
like
feature
branches
for
you
know,
service
x
and
then
have
a
database,
that's
kind
of
fresh
and
brought
up
and
then
torn
down.
When
that
feature,
branch
is
deployed
and
using
like
a
managed
service
for
something
like
that,
can
be
really
heavy
and
really
difficult
to
kind
of
get
built
into
that
workflow.
And
that's
where
we
started.
B
A
B
Well,
I
mean
it's
vague
right
when
we,
when
I
said
rds,
which
database
are
we
talking
about
mysql,
aurora,
right
or
even
oracle,
goes
there
as
well,
so
we
took
that
out
and
because
you
I
mean
some
of
the
users,
you
know
they
they
answer
they
adopt
rds,
but
within
rds
there
are,
you
know,
five
or
six
that
that
they
can
choose
from.
So
we
took
that
out.
B
A
B
Yeah-
and
I
reason
why
this
subject
was,
you
know,
while
filling
out
the
radar,
I
get
a
chance
to
talk
to
our
database
team
and
they're
new
to
kubernetes
and
we've
been
trying
to
work
with
them
to
migrate
their
services
onto
the
cloud.
I'm
most
the
time
on
to
kubernetes
as
well,
and
some
of
those
engineers
are
oracle
dbas
and
we
try
to
talk
to
them
about
migrating
venture
into
new
technology
and
don't
don't
settle
for
the
first
one.
A
D
One
of
the
big
things
I
think
in
kind
of
this
space,
of
like
keeping
an
open
mind
right
like
a
lot
of
pieces
of
technology,
are
coming
out
that
are
better
suited
for
certain
use
cases
and
kind
of
keeping
that
in
mind.
So
we
have
a
pretty
high
right,
high
right
throughput
when
it
comes
to
things
like
processing,
candidate
applications
or
our
job
aggregation
funnel,
and
so
we
needed
to
make
sure
that
whatever
database
technology
we
chose
could
handle
the
right
throughput.
D
D
C
Say
that
about
performances
and
reliability,
there
are
other
specs
aspects
to
take
into
consideration.
I
would
say
all
the
life
cycle
tools
around
the
software
solution,
the
database
software
solution-
I
mean
how
do
you
do
backups?
How
do
you
dig
further
when
you
have
an
issue?
Observability
is
really
important
and
how
you
can
get
the
more
information
from
your
system.
C
A
B
Yeah
I
mean
maya
and
zamin,
you
know
nailed
it.
We
as
we
migrate
from
on-prem
and
supporting
legacy
systems.
We
need
basically
keep
an
open
mind.
What
on
what's
out
there
venture
into
the
unknown
right
a
lot
of
times
my
team,
the
engines
I
have
every
spring.
We
I
see
them
picking
the
tasks
that
they're
comfortable
with.
I
keep
basically
telling
them.
B
A
B
Reach
out
to
your
network
or
join
this
community
here
and
pick
the
brains,
a
lot
of
brain
power,
a
lot
of
open
source
contributors
here,
trying
on
new
things
and
learn
from
each
other,
because
I
learned
a
lot
just
talking
to
you
guys
here
and,
and
so
don't
don't
be
afraid
to
reach
out
for
help.
That's
the
biggest
piece
that
I
can
say
here.
C
B
D
B
Go
ahead!
Sorry
matt
now
I
was
gonna
say
a
lot
gave
me
a
chance
to
reach
out
to
teams
that
I
have
not
talked
to
for
a
while,
especially
you
know,
and
this
time
and
most
of
my
team
work
from
home
anyways.
So
I
reach
out
to
the
database
team
and
pick
their
brain
for
a
while
to
help
me
build
this
radar.
D
Having
been
like
so
engrossed
on
our
persistence
platform
side
of
the
world,
I
was
pretty
familiar
with
kind
of
the
indeed
side
filling
in
that
information.
Wasn't
too
bad
for
me,
the
things
about
the
radar
process
that
I
thought
were
really
interesting
was
it
was
kind
of
difficult
at
times
to
figure
out
like
well.
Should
this
go
into
adopt,
or
should
this
go
into
trial?
D
A
Just
a
reminder,
so
you
can
go
to
radar.cncf.io
and
read
about
this
in
more
detail
and
take
a
closer
look
at
the
projects,
and
if
you
want
to
get
involved,
then
we
want
to
find
out.
What
do
you
want
to
hear?
You
can
go
to
this
link
cncf.io
tech
radar
that
just
redirects
to
a
github
github
issue,
where
you
can
vote
on
things
that
you
want
to
see
for
the
next
version
of
this
radar?
A
If
you
have
thoughts
about
how
this
could
be
better,
then
please
send
your
feedback
to
info
at
cncf.io
or
just
to
me,
and
that
is
it.
I
want
to
say
thank
you
once
again
to
all
three
of
our
radar
team
today
for
putting
the
work
and
the
time
into
this,
so
really
appreciate
it
and
really
appreciate
your
time
today.
Thank
you
so
much.