►
Description
Keynote: Knative, the future looks bright!- Naina Singh, Red Hat
Find out why the OpenShift Serverless team at Red Hat stands behind their vision of how Knative will continue to positively impact businesses, and help drive Knative forward as the premiere container-based serverless solution. The future looks bright!
A
So
once
upon
a
time
there
were
no
containers
and
applications
were
precariously
bundled
by
developers,
with
lots
of
hope,
as
wars
and
ers
were
executed
directly
on
virtual
machines
or
bare
metal
servers
right.
Everything
changed
when
docker
introduced
the
application
deployment
through
self-sufficient
and
portable
containers,
and
then
the
helmsman
with
the
name
of
kubernetes
emerged
and
the
cloud
world
was
never
the
same.
A
I'm
lena
singh,
I'm
very
excited
to
be
here
and
very
proud
for
red
hat,
to
have
the
opportunity
to
be
a
diamond
sponsor
at
this
very
first
native
con
event
and
for
the
next
few
minutes.
I
will
take
you
on
a
journey
to
show
you,
the
serverless
evolution
and
the
future
of
k
native
the
rising
name
in
the
world
of
application
deployment.
A
A
Serverless,
contrary
to
its
name,
we
have
learned
that
relies
very
much
on
servers.
What
it
actually
does
is
let
you
worry
less
about
the
servers
and
it's
easy
and
practical
good
for
all
sorts
of
applications.
Be
it
a
microservice
api
or
your
one-off
business
need
serverless
journey
could
be
charted
in
two
phases
and
serverless
1.0
phase
one.
A
And
the
next
pit
stop
in
this
journey
is
when
we
realize
that
the
same
serverless
traits
and
benefits
could
be
applied
to
containers,
and
this
leads
us
into
the
phase
which
we
can
call
1.5
and
one
solution
started:
delivering
serverless
experience
on
kubernetes
with
an
abstraction
layer.
That's
sitting
on
top
of
it.
Also
known
as
k
native
and
red
hat
is
one
of
the
founding
members
of
k
native
and
still
one
of
the
top
contributors
by
opening
up
serverless
to
containers.
A
A
And
now
we
are
entering
phase
two,
where
container
full
functions
for
code
to
cloud
capabilities,
integration
and
state
come
into
play.
Phase
two
of
serverless
will
focus
on
serverless
handling
the
complex
orchestration
and
integration
patterns
with
some
case
with
some
state
management
phase.
Two
is
also
focusing
on
advanced
messaging
capabilities
with
the
breadth
of
enterprise-ready
event.
Sources
for
developing
event-driven
applications
with
2.0
serverless
will
essentially
become
a
feature
of
your
platform
and
because,
in
practice,
most
organizations
would
be
running.
A
I'm
going
to
take
a
pause
before
I
show
you
the
future
as
to
how
combining
serverless
capabilities
with
other
open
source
technologies.
We
can
unleash
even
more
so
combining
the
serverless
capabilities
with
the
cloud
native
performance
of
quarkx
integration,
with
events
across
your
hybrid
cloud
through
camel
k,
doing
stateful
orchestration
with
cogito
and
securing
and
managing
your
serverless
and
non-serverless
api
and
the
reliable
event
bus
with
kafka.
We
can
create
solutions
for
almost
any
use
cases
and
now
back
to
the
future.