►
From YouTube: Keynote: Expanding the 80/20 Rule for Creating Service Mesh Value- Idit Levine, Solo.io
Description
Keynote: Expanding the 80/20 Rule for Creating Service Mesh Value- Idit Levine, Solo.io
While service mesh usage continues to grow, far too many companies are only seeing value from mTLS and observability. 80% of their value comes from 20% of the capabilities. As we connect and secure the world’s modern applications, we must strive to bring value to a broader set of use-cases. This means not only improving the performance and simplifying operations, but also exposing more of the value of service mesh to application teams, security teams, and ultimately to the forefront of the business.
In her talk, Idit Levine, CEO of Solo.io, will discuss innovative use cases that can be enabled by extending a service mesh. She will explore how the flexibility of mesh architectures can be used to enable more flexible, more secure, and more powerful usage patterns for companies.
A
A
We
have
we're
running
some
of
the
biggest
seo
deployment
in
the
world,
including
hundreds
of
customers
all
over
the
world.
We
recently
raised
another
135
million
dollars
in
a
billion
dollar
valuation.
We
make
us
a
unicorn
more
important
than
this.
We
are
really
really
strongly
participate
in
the
istio
community,
so
some
of
the
people
working
in
solos
people
at
christian
poster
wrote
the
last
seo
stone
action
book,
orlean,
san
and
and
raj,
who
are
two
of
the
tlc
members
from
the
five
who
exist
in
the
ecosystem
of
sto.
A
A
A
What
we
have
for
them
is
that
basically,
the
application
team
interesting
in
graphql
and
they're
coming
to
them
and
ask
them
to
basically
forward
all
the
traffic
to
this
graphql
server
and
in
the
graphql
server.
The
application
team
is
basically
need
to
do
quite
a
lot
of
stuff
in
order
to
make
it
make
it
happen,
they
need
to
create
the
schema
and
resolvers
they
need
to
build
it.
They
need
to
make
sure
that
security
apply
and
so
on
and
so
on.
A
There
is
quite
a
lot
of
burden
here
and
also
everything
right
now
is
with
extra
hope.
So
we
kind
of
like
we're
thinking.
What
can
we
do
in
order
to
actually
save
that
for
a
customer
and
what
we
did?
We
basically
do
graphql
and
build
it
into
envoy
right.
So,
basically,
right
now
we
teach
envoy
how
to
be
a
graphql
server.
So
now
the
only
thing
that
users
need
to
give
us
is
basically
a
schema
and
a
resolver.
A
There
is
a
lot
of
built-in,
but
you
can
also
write
your
own
wasium
resolver
and
then
everything
else
is
declarative
right.
You
basically
can
nvhs
will
get
a
request
of
graphql
and
know
how
to
do
this,
including
even
stitching,
so
it's
pretty
unique.
So
that's
what
is
gateway
pretty
simple
concept
in
glow
mesh?
We
basically
are
sto
distro.
A
We
first
of
all
upstream
first
right,
we
are
working
a
lot
with
the
community
if
there
is
anything
that
we
need
to
put
upstream,
we
are
putting
it
upstream.
Besides
that
we
have
a
special
build
like
fips
and
arms
and
anything
else.
You
need
we're
giving
you
n
minus
four.
If
you,
you
know
because
at
least
our
customers
are
not
upgrading
every
three
months
and
we
make
sure
that
if
there
is
any
cve,
we
basically
both
forward
them
to
all
of
that.
A
Okay,
so
that's
great,
but
no
one
running
one
cluster.
So
now
the
question
is:
what
do
you
sue?
Our
customer
is
running
between
five
cluster
200
clusters.
We
even
have
the
biggest
customers
who's,
basically
running
on
60
data
center,
with
thousands
of
instances
of
sd
all
over
the
world.
So
the
question:
what
are
you
going
to
do
come
to
each
of
your
stool
and
kind
of
like
configure
it?
No,
you
need
to
build
something,
so
we
kind
of
like
build
it
for
you.
A
We
can
do
also
route
bain's
local
locality
and
basically
make
sure
that
if
the
user
is
not
available
on
the
same
cluster,
it
will
fall
over
to
the
cluster
next
to
the
region
x,
to
the
data
center
next
and
so
on
that
plus
the
gateway
and
the
developer
portal
give
you
everything
you
need
in
order
to
basically
run
your
application
in
blue
mesh.
There
is
one
more
feature
that
is
extremely
important,
which
is
you
know,
kind
of
like
come
to
the
basic
of
what
we
doing
service
mesh?
Why
are
we
excited
about
service
mesh?
A
Why
are
we
excited
about
kubernetes?
All
together
I
mean
there's
one
aim
to
it
and
that
aim
is
basically
to
run
your
infrastructure
and
care
part
of
it
and
delegate
it
to
your
application
room
team.
That's
basically
all
the
reason
that
we're
doing
the
thing
that
we're
doing
so
that's
exactly
right.
We
basically
create
the
concept
of
workspace
that
is
giving
you
exactly
exactly
that
ability.
This
is
the
admin
view
right.
So,
basically,
now
as
an
admin,
I
can
see
my
cluster.
A
I
understand
that
and
my
sto
and
everything
that
I
need
and
also
the
workspace,
but
if
I'm
the
application
owner,
I
don't
need
to
know
anything
about
that.
I'm
only
going
to
view
the
c
my
view
on
my
workspace
with
observability
to
my
workspace
and
the
ability
to
basically
also
import
and
export
policy
and
destination.
A
A
Think
about
it
in
that
demo,
which
I
cannot
show
you,
because
I
don't
have
enough
time.
You
basically
have
two
clusters
on
those
cluster
you
have
in
one
of
them.
You
have
celium
in
the
other
one.
You
basically
have
a
colleague
you
have
a
both
of
them
registered
to
the
management
plan
and
basically,
in
order
to
create
defense
in
depth.
A
You
know
in
the
last
conference
me
and
you
talk
about
how
you
can
actually
supercharge
your
service
mesh
and
leveraging
technology.
Like
ebpf,
we
basically
talked
in
sdo
con
about
the
same
concept
about
sideless.
Basically,
we
do
bpf
versus
sidecar
in
service
mesh.
We
wrote
a
blog
that
explaining
this
and
even
internally
after
working
for
two
years
with
evpf,
was
extremely
important
to
us
to
give
the
community
the
tooling
that
we
built
bumblebee,
which
is
basically
a
docker
for
ebpf.
A
That
allows
you
to
run
it
to
build
it,
to
run
it
to
deploy
and
share.
So
because
we
are
so
excited
about
ebpf.
It's
really
important
to
us
that
our
platform
will
have
better
included
but
swappable.
So
we
will
drive
any
cni
that
you
want,
but
we're
also
going
to
ship
you
celium
and
we're
going
to
do
exactly
what
we're
doing
with
estea,
but
right
now
with
cilium.
So
basically
we
will
glue
them
together,
we'll
make
sure
that
they
work
seamlessly
together
and
we
will
make
it
extremely
extremely
easy
for
you,
the
customer.
A
So
again,
it's
better
included
by
swappable.
You
don't
have
to
use
silio,
but
if
you
do
we'll
give
you
support
and
make
sure
that
we
are
patching
it.
So,
basically
we'll
do
exactly
what
we're
doing
with
sto
right
if
you're
interesting
it
it's
coming
for
free
with
our
product
right,
if
you're
not
interested
in
our
product,
which
is
totally
fine,
we
will
give
you
support
enterprise
support
on
celium.
We
are
very
into
education
and
therefore,
what
we're
going
to
you
know.
We
have
a
big
platform
of
workshop
and
certificate
program
for
sdl
and
envoy.