►
From YouTube: Fueling Digital Transformation with Cloud Native Applications Mark Brewer Lightbend OpenShift Common
Description
OpenShift Commons Briefing
OpenShift Commons Operator Hour
Lightbend provides cloud native application platforms that are deployed on OpenShift. Lightbend is the originator of open source application frameworks Akka, Play & Lagom, the Scala programming language, streaming data pipelines framework Cloudflow, and the next generation serverless project Cloudstate.
Lightbend's Mark Brewer and Hugh McKee provide some real-world examples of enterprises embracing digital transformation and making the move to cloud native, with Lightbend and Red Hat providing the essential technical foundation to deliver incredible business outcomes.
November 11 2020
(Lightbend)
A
A
B
Hi
everyone,
my
name's
hugh
again
and
I'm
a
developer
advocate
for
lightbend
on
the
akka
platform,
so
my
role
is
pretty
enviable.
I've
been
a
developer
for
many
decades,
but
now
I
get
to
talk
to
people
about
aka
technology
about
light
bend
technology.
I
speak
at
conferences
around
the
world.
Do
lots
of
videos
do
lots
of
events
like
this,
and
and
also
I
get
to
write
a
lot
of
cool
demos
with
my
favorite
thing
is
adding
some
eye
candy.
So
that's
going
to
be
showing
you
later
on
in
in
this
session.
A
B
C
Good,
like,
like
michael
said,
my
name
is
mark
brewer,
I'm
the
ceo
of
lifebend
been
in
this
open
source
industry
for
quite
a
while,
actually
20
years
now,
for
I
think,
21
years,
my
first
company
in
the
open
source
space
was
covalent
and
covalent
was
the
company
behind
the
apache
web
server,
and
the
tomcat
servlet
container
actually
had
an
opportunity
to
work
with
red
hat
back
then
as
well,
but
I've
also
from
there.
I
should
say
I
went
to
spring
source.
C
So
I
was
part
of
the
spring
team
that
took
spring
framework
and
the
tomcat
product
and
brought
it
to
market,
and
then,
of
course,
that
company
got
acquired
by
vmware
back
in
2009
and
then
a
few
years
later
became
a
spin
out
of
vmware.
It
was
pivotal,
and
so
anyway
I
stayed
with
spring
source
until
I
I'm
sorry
with
vmware.
Until
I
came
here
in
2012.
C
A
Okay
and
light
bend
bending
of
light
is
there?
Is
there
a
any
symbolism
in
the
company
name,
or
did
you
decide
to
just
pick
a
name
that
was
easy
to
pronounce
and
and
people
wouldn't
misspell
it
or
how
did
they
come
up
with
the
name
like
then
we
have
a
lot
of
our
partners.
Have
you
know
insect
names
and
some
of
them
have
farm
animal
names,
and
so
why
light
bent.
C
Yeah
well,
actually,
we
weren't
light
bend
when
we
were
founded.
We
were
type
safe
and
type
safe,
the
name
to
type
safety,
which
is
one
of
the
things
that
scala
the
language
that
we're
the
vendor
behind
provides
type
safety,
and
so
the
name
had
a
lot
of
meaning.
Initially,
when
the
company
was
all
about
scala
and
early
on
with
the
the
product,
we
focused
on
scholar
developers
only
just
a
side
note
today
and
actually
for
the
last
seven
years.
C
Java
has
been
our
primary
language
that
our
customers
utilize,
but
anyway,
the
company
was
type
safe
for
its
first
five
years
of
existence,
we
changed
the
name
in
2016,
went
through
a
long
exercise
of
trying
to
come
up
with
a
trademarkable
name
and
a
name
that
wasn't
restrictive,
like
type
safe
was
type
safe
was
all
about.
You
know,
scala
and
the
company
provides
the
full
platform.
As
I
said,
it's
it's
targeted
at
the
java
audience
more
than
it
is
even
the
scala
audience.
C
A
I've
been
here
for
19
years
at
red
hat,
and
I
completely
get
it
about
the
the
spelling.
I
mean
red
hat
red
hat's,
two
words:
it's
capital,
r,
capital,
h
and
people
make
it
be.
One
word
with
you
know,
lowercase
h,
so
I
I
completely
get
a
matter
of
fact.
We
we
actually
went
through
a
huge
logo,
rebranding
exercise
about
two.
B
A
C
When
we
accomplish
that
with
light
bend,
the
other
other
thing
that
we
were
trying
to
accomplish
was
find
a
name.
That
was
not
only
easy
to
remember
an
easy
spell,
but
didn't
limit
us.
It
wasn't
tied
to
just
one
piece
of
technology
like
safe
was
so
I'm
pleased
with
the
name,
but
it
doesn't
have
any
other
specific
meaning.
Obviously,
light
bend
is
light.
Bending
is
a
real
thing.
It's
it's
difficult
to
do.
It
takes
a
pretty
big
mass
to
actually
bend
light,
but
it
can't
happen
mostly.
A
C
We've
had
a
long-standing
relationship
with
red
hat
and
even
prior
to
that,
with
ibm,
we've
worked
with
ibm
on
a
number
of
fronts,
in
fact:
they're,
actually
an
investor
in
our
company.
So
our
relationship
with
red
hat
extends
through
a
number
of
of
relationships
or
areas
in
the
relationship
specifically
around
openshift.
So
we
have
you
can
find
our
our
technology
on
the
open,
open
shift.
C
Commons
find
this
on
the
marketplace
as
well.
The
red
hat
marketplace
we
just
last
year.
I
guess
it's
this
year,
not
last
year,
sorry
won
the
light.
Bender,
I'm
sorry
red
hat's,
north
american
partner
award
and
we've
certainly
found
many
customers
that
are
using
openshift
with
our
technology.
In
fact,
I'm
going
to
be
talking
about
that
here
a
little
bit
later,
but
we
have
quite
a
few
customers.
Who've
been
leveraging
the
openshift
technology,
along
with
light
ben's
platform.
A
So
I'd
like
to
put
in
a
gratuitous
plug
for
for
light
bend.
You
know
you
folks
have
been
a
a
member
in
good
standing
of
the
openshift
commons
community
for
quite
some
time.
It's
not
trivial.
You
know
you
mentioned
that
you
folks,
you
know,
have
an
application
that
works
with
openshift
and
you're
in
the
red
hat
marketplace,
operated
by
ibm.
I
just
wanted
to
make
sure
that
people
understood
that.
That's
that's,
not
a
trivial
statement,
that's
not
a
that's!
Not
a
logo
swap
and
putting
it
on
a
website
saying
I'm
affiliated
with
some
program.
A
You
folks
have
been
working
our
technical
teams
for
quite
some
time
to
build
and
test
your
your
containers
and
and
most
recently,
your
your
red
hat
operator.
So
you
folks
have
a
red
hat
certified
operator
for
openshift
and
that
enables
companies
then
to
be
listed
with
a
commercial
offering
in
the
the
red
hat
marketplace,
operated
by
ibm
so
yeah.
A
I
just
wanted
to
point
that
out
that
you
know
that
the
at
the
end
of
the
day,
the
story
for
customers
is
people
who
want
to
run
light
bend
on
any
of
the
red
hat
platforms,
including
openshift,
and
know
that
you
know,
for
the
the
best
day.
Two
supportability
is
assured
because
of
the
engineering
integration
that
we've
done
together
between
our
companies.
So
I
thought
I'd
try
to
throw
that
out.
There.
A
Well,
it's
all
about
it's
all
about
doing
it
for
the
end
customer,
so
nobody
likes
surprises.
They
want
to
try
and
run
something
in
a
production
environment,
especially
now
when
we
have
all
you
know,
everything's,
multi-cloud
and
distributed
everywhere.
So
it's
all
about
you
know
enhancing
the
customer's
value.
That's
that's.
My
team's
chart
anyways
right.
Okay,
so
talk
a
little
bit
more
about
light,
bend
like
what
it
is.
What
it
does
I
know
yeah,
so
it
was
bringing
it
to
akka.
A
C
Yeah
before
we
jump
into
the
product
I'll
give
you
a
quick
history,
so
the
company,
as
I
mentioned,
is
started
in
2011.
The
the
objective
of
the
founders-
that's
martin,
odersky
and
jonas
bonaire-
was
to
help
companies
build
distributed
based
systems
and
bring
it
to
a
broader
audience.
A
broader
audience
than
previously
could
have
built
these
kind
of
complex
systems.
Thinking
back
to
you
know,
2011.
C
C
It's
simply
application
modernization
I'll
talk
about
one
customer
where
it
was
all
about
that
they
had
a
very
old
legacy
system
that
was
getting
harder
and
harder
to
maintain,
and
they
just
were
looking
for
a
way
to
bring
it
to
newer
technology,
but
make
it
easier
for
developers
to
continue
to
maintain
that
application
and
then,
finally,
e-commerce.
We
see
a
lot
of
a
lot
of
new
e-commerce
platforms
built
using
the
light
bin
technology.
C
C
If
you
will
or
personas
one
is
focused
on
delivering
what
you
need
to
build
reactive
micro
services
and
get
them
into
production,
that's
the
aqua
platform
at
its
core
and
then
aqua
data
pipelines
brings
in
streaming
technologies
both
our
own
streaming
technology
akka
streams,
as
well
as
some
third-party
spark
and
flink
and
others
that
are
widely
adopted
in
the
market.
But
in
in
the
akka
data
pipelines,
product
or
persona,
you
can
build
streamlets
that
become
core
or
integrated
into
the
application.
Creating
and,
like
I
said,
we'll
talk
about
a
couple
of
use
cases
there.
C
C
Next
efficiency
efficiency
is
obviously
important.
You
want
to
find
ways
to
utilize
your
cloud
infrastructure,
whether
it's
running
on
kubernetes
or
not.
You
want
to
make
sure
that
it's
taking
advantage
or
or
only
utilizing
what
it
needs
and
in
a
kubernetes
open
shift
world
highly
efficient,
be
able
to
run
these
things
in
a
very
small
footprint
with
with
you
know,
scale
when
you
need
it
or
availability
when
you
need
it.
C
First,
one
bright
house.
This
is
bright
house
by
the
way,
is
a
spin
out
from
I'll
think
of
it
because
we're
talking
here,
but
they
they
became
a
public
company
a
couple
years
ago,
spun
out
of
one
of
the
large
insurance
metlife
there
we
go,
I
knew
I'd
get
it
and
the
the
problem
they
were
trying
to
solve
was
to
reduce,
not
just
risk
but
reduce
the
amount
of
time
to
process
mass
amounts
of
data
to
come
up
with
answers
on
risks.
C
You
know
whether
or
not
this
this
was
an
insurance
policy
that
had
a
high
risk
or
a
lower
risk.
They
were
able
to
accomplish
that
and
reduce
it
from
70
minutes
or
more
down
to
less
than
10
seconds
now.
This
doesn't
just
mean
that
they
can
get
an
answer
faster,
but
it
also
means
that
they
can
run
these
models
much
more
frequently,
so
they
can
evaluate
risk
at
a
much
more
rapid
and
frequent
basis,
yeah.
C
So
with
usaa,
another
red
hat
openshift
customer
that
was
looking
to
improve
the
time
it
took
to
send
out
messages
through
all
their
different
channels.
If
you
don't
know,
usaa
is
a
insurance
provider
for
military
families,
and
I
think
they
have
10
million
members
or
more
and
one
of
the
things
that
they
they
were
struggling
with
was
being
able
to
interact
with
their
their
member
base
in
a
in
a
way
in
which,
where
you
could
get
information
when
it
was
relevant
to
them.
C
So
if
they
got
in
a
car
accident,
they
want
to
place
a
claim
or
let
their
insurance
pro
insurance
agent
know
take
a
picture
of
the
accident
and
send
it
directly
back
to
the
to
the
persons
that
would
authorize
a
claim.
Well
that
used
to
take
days
now,
you
can
do
it
in
real
time.
They
replace
their
entire
undercore
communication
system
that
allows
them
to
communicate
with
their
their
members
via
email
via
sms,
via
actually
phone
and
and
the
like.
C
A
C
Is
it
is
norwegian
and
we're
actually
working
with
a
number
of
cruise
line,
companies
that
use
our
technology
all
for
the
same
type
of
application,
where
it's
about
personalizing
the
experience
of
somebody
who
goes
on
on
a
cruise,
and
that
starts
from
the
time
you
book
the
cruise,
whether
you
do
it
on
the
web
or
over
the
phone
or
via
their
app.
They
actually
have
an
app
where
you
can
book
your
your
cruise.
But,
more
importantly,
it's
the
experience
once
you're
on
the
cruise
booking
your
reservations,
whether
it's
for
dinner
or
for
an
excursion.
C
If
you're
going
to
go
out
on
a
snorkeling
trip-
and
you
realize
the
weather
is
bad,
you
need
to
change
that
that
excursion
to
something
else.
Well,
this
this
experience,
this
personalized
experience
happens
on
the
ship
for
everybody
and
in
the
in
the
past.
Before
they
had
this.
You
know
you
just
have
to
book
all
of
your
your
reservations
in
advance,
and
you
know
days
trying
to
get
on
the
phone
to
change
something
if
the
weather
looked
like
it
was
going
to
be
bad.
Now,
it
all
happens.
C
A
Mark
how
do
how
does
that
work?
I'm
not
I'm
not
quite
sure
I
get
it.
I
I
get
it
that
you
know
you
don't
have
to
book
everything
in
advance,
but
how
does
how
specifically
does
light
bend
and
and
your
in
your
products
akka
actually
improve
that
the
user
experience
of
people
on
a
cruise
ship?
I'm
not
I'm,
not
picking
it
up.
C
So
they
built
a
they
built,
an
app
that
you
experience
via
the
phone
or
a
tablet
if
you've
got
an
ipad
or
something
and
that
application
allows
you
to
keep
track
of
not
only
all
the
things
you've
booked,
but
anything
else.
That's
available
that
you
might
want
to
try
out
all
the
way
down
to
your
dinner
reservations.
C
You
can
even
find
out,
if
there's
a
long
line
at
a
particular
restaurant
on
the
ship,
but
you
don't
want
to
go
there
for
dinner
or
lunch
because
the
wine's
too
long,
so
it's
all
via
an
application,
and
you
can
also
set
up
alerts
so
that,
for
your
dinner
reservations,
if
you
want
to
be
notified
that
there's
going
to
be
a
a
long
line,
then
it'll
alert
you.
So
you
don't
even
bother
going
to
that
particular
restaurant.
A
C
Yeah
I've
got
a
couple
more
use
cases.
I
thought
I
would
share
and
then
we'll
turn
it
over
to
hugh
and
have
him
give
give
the
demo
the
product
rogers
rogers
telecommunication,
their
canadian
telecast
telecommunication
company.
This
was
all
about
reducing
costs,
but
also
delivering
a
much
better
experience
on
their
ecommerce
site.
So
if
you
go
to
rogers.com
that
site
and
and
the
app
where
you
can
buy
a
phone,
you
can
order
services,
whether
you
want
to
change
your
cell
phone
coverage
or
you
want
to
add
a
new
new
family
member
or
change.
C
C
So
they
were
able
to
accomplish
this
by
by
using
the
light
bend
technology
using
akka.
In
our
frameworks,
the
the
reduced
footprint
has
saved
them
nearly
40
percent
per
year
in
their
bill
for
for
infrastructure,
so
the
amount
of
footprint
that
they
they
were
running
their
old
system
on
versus
what
they're
running
it
on
now
has
shrunk
by
40.
C
C
They
were
looking
to
replace
a
very
old
cobalt-based
system,
and
some
of
us
have
been
around
long
enough
to
remember
programming
in
cobalt,
it's
hard
to
find
cobol
programmers,
it's
hard
to
maintain
co-op-based
systems.
So
this
is
a
swift
payment
system.
Anybody
who's
been
in
the
banking
industry
knows
what
this
is
and
is
experienced
with
swift
payment
systems.
C
They
decided
they
needed
to
replace
it
and
replace
it
with
something
that
not
only
was
more
modern
and
could
be
maintained,
but
would
allow
them
to
add
functionality
in
a
in
a
more
rapid
fashion.
You
know
the
old
koba
bay
system,
I'm
sure
it
hasn't
changed
much
over
the
years,
so
they've
they're
not
done
with
this
they're
in
process.
C
A
B
I
I
wanna,
you
know
some
kind
of
a
kubernetes
environment,
so
this
first
app
is
on
behind
the
scenes
I'm
actually
running
in
an
amazon
environment,
but
behind
the
scenes,
there's
two
aka
microservices
and
they're
both
running
a
number
of
pods
in
a
cluster,
so
in
another
second
demo,
app
I'll
kind
of
show
you
the
anatomy
of
this
thing,
but
here
I
just
wanted
to
show
you
kind
of
a
little
bit
more
realistic
type
of
an
application.
So
the
user
interface
of
this
demo
app
is,
is
a
map.
It's
like
a
google
map.
B
The
concept
is
that
this
is
simulating
an
iot
type
of
an
application,
so
these
markers
that
are
distributed
around
the
world
on
the
map
are
showing
locations
of
these
simulated
iot
devices
that
I've
created
using
this
demo
app
and
the
real
goal
of
this
app
is
to
create
some
load.
We're
trying
to
push
the
parameters
of
how
hard
can
we
push
akka?
B
How
hard
can
we
push
in
openshift,
kubernetes,
environment
help
and
probably
the
biggest
one,
is
how
hard
can
we
push
the
back-end
databases
that
this
thing
interacts
with,
so
just
to
show
you
you
can
navigate
around
this
thing,
just
like
you
do
with
google
maps
and
I'm
going
to
zoom
into
the
area
around
london.
As
I
get
closer,
you
start
to
see
where
there's
these
highlighted
regions
and
what's
happening
here
is
this
is
showing
where
these
hypothetical
iot
devices
have
been
placed.
B
A
B
Yes,
exactly
yeah
great
question,
so
what's
what
this
demo
app
is
doing?
Is
that
one
service
is
I'm
using
that
to
simulate
the
outside
world,
like
iot
devices
that
are
sending
in
telemetry
messages
into
another
services?
So
this
is
what's
happening
here.
There's
the
second
service
is
receiving
these
telemetry
messages.
Saying
things
like
hey,
create
a
device
at
this
location
on
the
map
is
the
device.
Happy
is
the
device
sad.
You
know
that
kind
of
a
state
change
or
deleted
device.
So
it's
you
know
it's
a.
B
But
on
the
backend
system,
there's
akka
is
a
the
actor
model
on
the
jvm
and
actors
are
kind
of
glorified
objects.
So
if
you're
a
developer
of
any
kind
or
if
you
heard
about
you,
know
software
development
commonly
hear
about
object-oriented
programming,
well,
actors
are
kind
of
very
much
like
objects.
You
they're
written
in
the
same
way
that
objects
are
written,
but
they
have
a
kind
of
a
unique
characteristic
and
the
unique
characteristic
is
the
only
way
you
interact
with
an
actor.
B
Is
you
send
it
a
message,
an
asynchronous
message
versus
how
you
would
interact
with
say,
a
normal
object,
written
in
python
or
or
java,
or
something
like
that
so
in
this
system,
what
I'm
zooming
in,
but
in
as
you
can
see,
as
I'm
mousing
around
here,
moving
their
mouse.
It's
kind
of
it's
pulling
data
from
the
back
end,
but
there's
a
thousand
twenty
four
devices
so
in
this
region
that
I'm
over
right
now.
B
So
on
the
back
end
of
the
system,
there's
a
thousand
twenty
four
actors
that
are
alive
that
know
the
state
each
individual
device.
Now
in
this
map
on
the
bottom
right,
you
know
it's
showing
that
there's
like
223
000
devices
that
have
been
created.
So
what
that
means
is
there's
223
000
live
actors,
kind
of
hot
in
memory.
A
Where
do
the
red
hat
the
operators
that
you
folks
built
for
openshift,
where,
where
do
those
operators
live?
So
if
they're,
you
think
of
theirs
like
in
like
an
ai,
you
know
artificial,
intelligent
daemon.
If
you
will
that's
that
allows,
you
know,
apps
to
you,
know,
self-heal
and
helps
with
configuration,
management
and
so
forth.
Where
do
the
operators
fit
into
this
whole
into
this
whole
whole
scheme
here.
C
B
So
one
of
the
things
that
I
can
do
with
this
app
is
like
I
said
it's
kind
of
a
test
bed
for
demonstrating
the
technology.
There's
a
lot
of
source
code
for
developers
to
look
at,
and
things
like
that.
It's
kind
of
fun
to
play
with
interactively
here
is:
I
can
kind
of
do
things
at
scale.
So,
for
example,
I'm
going
to
create
a
bunch
of
devices
and
I
can
do
through
this
ui.
I
can
create
some
devices
and
it's
not
like
one
device
at
a
time.
B
B
It
cascaded
that
into
4
000
grpc
messages
over
the
network
to
the
second
service
that
second
service
got
those
4
000
requests,
as
if
4
000
devices
suddenly
came
online
over
the
course
of
about
four
seconds.
Did
a
bunch
of
database
work
did
a
bunch
of
actor
stuff
and
then
brought
a
bunch
of
information
to
the
database,
and
we
saw
it
happen
in
real
time.
B
So
there's
a
there's
a
lot
going
on
behind
the
scenes
that
made
all
that
work,
but
it
runs
pretty
fast.
You
know
that
was
4
000
pretty
quickly.
I
can
do
my
little
bit
I'll.
Do
it
once
more
just
for
fun
and
create
4
000.
I
can
zoom
in
to
kind
of
watch
them
happen
a
little
bit
more
granular
scale,
so
you
can
see
the
devices
start
to
show
up
and
there
you
know
it's
done
right.
B
So
there's
you
know,
there's
now
another
4
000
devices,
so
I
can
zoom
out
more
and
generate
more
traffic,
but
I
want
to
go
to
the
second
demo
all
right.
So
this
is
another
demo.
That's
running
in
openshift
code
running
containers
on
my
laptop
the
first
one
was
running.
You
know
real
cloud
environment
and
amazon
in
kubernetes,
but
this
one
is
structurally
behind
the
scenes
exactly
what
this
that
other
application
was
doing,
and
it's
a
way
to
kind
of
show
a
cluster
and
akka
cluster
in
action.
B
A
A
A
B
A
Okay,
so
in
the
in
the
case
that
mark
brewer
was
was
showing
there
with
the,
I
think
it
was
the
norwegian
cruise
lines
customer
story,
this
infrastructure
that
we're
looking
at
right
here
would
be
the
infrastructure
of
the
norwegian
cruise
lines
organization
and
all
the
little
blue
dots.
All
the
you
know,
iot,
you
know
devices
would
be
all
of
their
stuff
that
they
use
to
run
their
business.
B
If
this
was
a
shopping,
cart
app,
if
we,
if
somebody
use
akka
to
build
the
classic
shopping,
cart
app,
every
one
of
these
blue
circles
would
be
somebody
actively
interacting
with
a
shopping.
Cart.
Your
shopping
cart.
My
shopping
cart.
Somebody
else's
shopping
cart.
These
little
blue
circles
represent
real
actors
running
in
the
system
in
this
demo.
Again,
it's
like
I
got
100
or
so
of
these
little
blue
circles
running
right
now,
in
the
map
app,
I
had
225
000
of
them.
A
B
So
the
idea,
though,
is
that
the
we're
making
it
easy
for
developers
to
write
the
business
logic
for
handling
you
know
the
manipulations
of
the
devices
or
the
shopping
cart
or
whatever
the
application
has
to
do
in
a
very
distributed
environment.
So,
on
the
perimeter
of
this
circle,
I'm
showing
a
bunch
of
of
you
know,
100
or
so
the
count
is
down
at
the
bottom
here.
This
entity
count.
It
says
102.
it'll
change,
because
these
things
are
coming
and
going
because
the
system
is
actually
you
know
percolating
along
here.
A
B
Yes-
and
that's
exactly
what's
going
on
here-
that
you
know
in
this
case
I've
got
the
number
of
shards
is
fixed.
You
know
the
actual
number
you
know
in
this
case,
there's
15
in
the
map
app,
but
there
was
like
about
a
thousand
shards
and
you
know
the
scale
of
hundreds
of
thousands
of
actors,
but
the
charger.
Basically,
their
work
is
really
just
to
distribute.
B
You
know
work
across
the
cluster,
because
the
big
circles
here
represent
pods
running
in
kubernetes
in,
like
in
my
open
shift
environment,
on
my
laptop
or
in
a
real
kubernetes
environment,
running,
say
somewhere
in
a
cloud
or
an
on-premise
open
shift
environment.
So
right
now,
I'm
running
a
cluster
of
three
pods
and
those
pods
of
course
contain
a
container
and
those
containers
are
running
a
java
virtual.
B
B
Just
so
I
tag
it
so
I'm
going
to
force
this
pod
to
stop
this
pod
19
and
do
that
just
by
clicking
this
up
here,
so
it
should
shut
down
in
a
moment,
and
what
we
should
see
is
this
entity
that
I've
tagged
as
long
as
as
well
as
a
shard
will
jump
to
one
of
these
other
pods
there.
It
goes
beautiful,
so
it
right
away.
This
is
where
it
recovers.
It's
like
for
me
as
a
developer.
Writing
the
code
that
does
handles
the
entity
logic.
B
B
It's
like
yep,
expected
that
we
know
pods
come
and
go,
that's
just
a
fact
of
life,
and
it
just
deals
with
it
so
and
then
the
meantime,
the
beauty
of
running
into
kubernetes
environment
is
that
for
a
moment
we
were
down
to
two
pods,
but
I
told
kubernetes.
I
want
three
pods
in
this
environment,
so
kubernetes
saw
that
there
was
a
pod
down
and
it
started
one
up
and
it
came
back
so
the
the
kubernetes
is
like
the
perfect,
perfect
environment
for
akka
clusters.
B
Akka
plus,
has
been
around
for
a
while
kind
of
predates
kubernetes.
I
used
docker
clusters
when
I
used
to
work
at
hp,
and
I
t-
and
we
had
you
know
just
like
virtual
machines
and
we
really
really
need
wanted
something
like
this.
You
know
a
beautiful
orchestration
environment,
it's
just
akka
was
waiting
for
something
like
kubernetes.
B
B
So
we
should
see
is
the
these
on
the
top
right
here.
These
are
nodes
or
pods
running
in
another
cluster,
and
all
they're
doing
is
generating
traffic.
That's
flowing
into
this
service.
You
know
it's
generating
http
requests
that
are
flowing
in
and
I'll
show
you
so
these
four
more
spun
up
and
now
the
density
of
the
entities
is
increasing.
So
I'm
you
know
kind
of
trying
to
simulate
increasing
the
load
on
the
system.
So
now
the
stress
say
on
each
of
the
pods
running
in
this
cluster,
each
of
the
three
pods
has
gone
up.
B
So
of
course,
with
kubernetes.
You
can
set
that
up
to
auto
scale,
but
you
can
also
manually
scale.
So
that's
what
I'm
going
to
do.
I'm
going
to
go
back
over
to
the
open
shift
console
and
I'm
going
to
scale
up
my
akka
cluster
here.
So
what
we
should
see
is
two
more
pods
will
show
up
which
contain
two
more
containers
which
are
running
two
more
jvms.
B
Those
containers
will
spin
up.
Those
jvms
will
light
up,
akka
the
they
reach
out
and
say:
hey.
I
want
to
join
the
cluster,
here's
what
one
just
came
in
and
then
the
second
one
should
come
in.
What
you
see
also
is
that
the
shards
are
some
of
the
shards
are
automatically
getting
redistributed
to
these
new
pots.
So
now
we
have
some
extra
processing
capacity
thanks
to
kubernetes
and
akka
sees
this
and-
and
this
is
part
of
the
sharding
strategy,
it
goes.
I
got
more
capacity.
Let
me
move
stuff
over
there.
B
B
Yes,
the
zero
code
that
I
wrote
that
makes
that
happen
as
a
developer.
You
know
I
developed
this
little
demo
application.
I
developed
the
the
map
application.
I
don't
run
any
of
that
code.
That
does
all
this
rocket
science,
redistribution
and
stuff
like
that,
that's
handled
by
akka-
and
I
I
just
have
to
follow
kind
of
a
very
simple
prescriptive
approach
for
setting
up
the
way
my
application
works,
and
I
get
this
kind
of
out
of
the
box.
A
B
C
You
think
about
it
fortnight.
The
game
runs
on
akka
and
when
there
are
all
these
active
players
at
the
same
time,
it
needs
to
scale
to
some
pretty
big
numbers.
I
don't
think
we
ever
got
a
final
number
from
how
many
nodes,
but
it's
in
the
thousands-
and
you
know
when
it
when
people
aren't
playing
it,
just
shrinks
down.
So
it's
elastic
and
therefore
their
cost
of
running
the
system
is
only
high
when
they
have
a
lot
of
people
using
it.
B
Oh
yeah,
sorry
yeah,
we
we've
got
is
a
commercial
offering
monitoring
that
provides
instrumentation.
You
know
it's
very
specific
to
aka
the
jvm
and
so
on
that
can
be
integrated
in
with
some
of
the
you
know,
the
more
common
tools
you
know
the
application
monitoring
tools
so
yeah
it
does
that,
but
I
mean
as
far
as
things
like
when
a
node
say,
fails
or
node
spins
up,
and
we
want
to
redistribute
work
across
it
and
the
decisions
to
do
that.
That's
all
pocket
itself.
You
know
the
open
source
socket
of
the
box.
B
B
So
it's
as
a
developer.
It's
really
easy.
All
I
have
to
do.
Is
I
write
the
code
that
kind
of
receives
the
incoming
say,
http
request,
maybe
some
json
or
whatever
it
is.
I
create
an
object
which
represents
a
message
that
I
want
to
send
off
to
an
entity
actor
and
I
identify
the
entity.
You
know
by
some
id
that
I
want
to
send
this
message
to
and
all
the
routing
to
either
local
or
remote
off
to
another.
You
know
node
across
the
network,
is
handled
by
itself.
It's
all
this.
B
B
When
I
turn
them
all
on,
you
can
see
all
this
flow
coming
in
from
the
the
load
balancer-
and
it's
just
you
know
it's
kind
of
a
spaghetti
bowl,
but
it's
showing
all
the
distribution
of
all
these
incoming
messages.
Around
20
messages
per
second
are
coming
into
this
little
demo,
app
that
are
just
getting
distributed
all
across
the
cluster,
and
it
doesn't
matter
where
the
http
request
comes
in
we'll
always
route
it
to
the
correct
entity.
B
Actor,
no
matter
where
that
thing
is
and
and
that
allows
us
to
do
something
with
state,
because
a
very
common
pattern
for
people
to
develop
applications
is
is
called
a
stateless
type
of
an
application,
and
the
reason
they
do
stateless
is
that
it's
hard
to
do
stateful
in
a
distributed
environment.
But
this
is
exactly
what
akka
excels
at,
because
it
has
this
very
powerful
mechanism
for
distributing
messages
across
a
distributed
environment,
which
means
that
we
can
have
stateful
actors,
which
means
with
stateful
actors.
B
Excellent
excellent
yeah,
the
the
this
visual
is
is
this
visualization
has
been
fun
and
again.
This
is
all
these
are
things
that
we
make
available.
Yes,
just
stuff,
I
wrote
for
developers
to
take
play
with,
maybe
show
their
team.
You
know,
get
excited
about
akka
and
see
how
akka
works
and,
like
I
said,
have
a
little
bit
eye
candy.
I
love
doing
this
eye.
Candy
stuff.
A
That
was
actually
great
for
me
because
when,
when
you
were
talking
about
the
norwegian
cruise
lines
and
the
cruise
ship,
I
was
you
know
I
I
was
kind
of
struggling
to
figure
out
okay,
so
how
exactly
does
akka
fit
in
there
and
tie
all
this
together?
But
now
I
get
it.
You
know
when
you're
running
these
large
complex
businesses
that
are
mobile
and
moving
around
the
world.
I
couldn't
imagine
trying
to
manage
a
business
like
that
without
something
like
what
that
you
folks
provide
it.
Just
you
couldn't
do
it.
C
Well,
there's
even
a
more
challenging
aspect
to
norwegian
or
any
cruise
line
use
case,
that
is
that
they
aren't
always
connected
to
the
internet
right
they
may
be
out
at
sea
and
they
may
not
have
good
coverage.
You
know
the
satellite
coverage
isn't
good
or
they're
too
far
from
shore
to
get
the
wireless
connections
there.
So
the
ship
itself
is
a
data
center
and
that
data
center
has
akka
running
and
has
pods
of
aqua
running.
But
when
it's
close
enough
to
it
has
internet
connectivity,
it
expands
to
the
internet.
C
In
other
words,
it
uses
amazon,
I
think,
is
their
their
provider,
but
regardless
it,
it
literally
behaves
just
like
that
that
that
visual
graphic
that
you
were
seeing
there
from
hugh,
where
all
of
a
sudden
there's
another
pod
available.
Now
I've
got
the
internet.
So
I
can
start
using
it
to
process
these
things,
but
when
the
ship
is
out
too
far
away
from
the
internet
or
too
far
away
from
the
shore
or
satellite
coverage,
it
still
works.
Everything
works.
A
You
know
I
was
we
were
talking
about.
You
know
I
mentioned
people
are
still
using
open
vms.
I
I
used
to
work
for
digital.
I
used
to
help
software
vendors
port,
their
apps
to
alpha
alpha
nt,
digital
unix
openvms,
and
there
were
there
were
tools
out
there
made
by
computer
associates
and
bmc
and
others
that
were
kind
of
doing
something
and
correct
me
from
wrong
kind
of
like
what
akka
is
doing
now
in
a
distributed.
B
A
lot
of
your
old
habits,
adopt
these
new
habits
and
you
get
really
where
you're
really
really
using
the
cloud
right
I
mean
you're
scaling
you're
resilient
you're.
You
know
if,
if
you,
if
your
kubernetes
auto
scales,
you
it's
it's
it's
elegance,
you
know
auto
scaling
where
you,
you
know
your
actors
are
redistributed
and
all
this
kind
of
stuff,
it's
just
massively
cloud
native
compared
to
what
most
people
seem
to
be
doing
kind
of
bringing
forward.
Oh
yeah
we're
going
to
just
build
our
stateless
micro
services
on
kubernetes
and
it's
all
good
right.
B
It's
like
well,
no
you're,
not
really
taking
advantage
of
all
the
really
awesome
things
you
get
with
things
like
bringing
openshift
giving.
You
know,
bringing
the
cloud
down
premise
to
usa,
for
example,
and
allowing
them
to
really
take
advantage
of
the
the
power
that
they're
getting
not
doing
the
old
things
anymore.
You
know
but
doing
the
new
things.
A
C
Yeah
great
question:
I
don't
have
a
crystal
ball,
but
I
will
say
that
there
is
a
number
of
movements
that
we're
both
a
part
of
and
watching
very
carefully,
specifically
around
abstraction,
making
it
easier
to
build
these
complicated
systems.
If
you
think
about
all
the
configurability
and
what
frameworks
provide
you
or
provide
a
developer,
it
gives
you
a
lot
of
power,
but
it
also
takes
a
lot
of
work
for
the
developer
and
even
for
the
ops
folks
when
they
put
those
things
into
production.
C
We
see
a
world
where,
in
24
months,
maybe
much
sooner
where
companies
are
going
to
look
at
serverless,
look
at
ways
of
abstracting
that
complexity
and
therefore
losing
some
of
the
configurability,
but
giving
it
up
in
exchange
for
rapid
development
and
and
honestly,
something
that
I
don't
have
to
worry
about.
That
literally
has
been
operated
by
by
the
cloud
providers.
The
service
itself
just
runs.
I
just
write
the
business
logic
and
deploy
it
and
it
all
the
rest
of
it's
handled
for
me.
So
we're
we're.
C
We've
launched
a
project
called
cloud
state
and
we're
going
to
be
launching
a
service
called
akka
serverless,
and
that's
all
about
abstracting
that
complexity
and
making
it
much
easier
to
build
these
complex
distributed
systems.
I
think
that's,
that's
not
just
light
bin.
That's
driving
towards
that.
You
see
other
vendors
as
well,
including
ibm,
red
hat,
providing
technologies
to
make
it
easier
to
build
cloud
native
based
systems
and
not
put
a
lot
of
the
work
on
the
developer.
C
C
B
B
So
now
we
have
this
new
abstraction
than
kubernetes
and
then
serverless
takes
it
to
the
next
level
of
distraction
where
I
don't
even
care
about
things
like
pods
anymore,
and
I
have
no
idea
about
machines.
What
all
I'm
doing
is
saying
I
will
spend
up
to
this
much.
You
know
things
like
that.
You
know
I
might.
I
will
pay
for
this
much
compute
power
and
iot
operations
and
how
you
do
it.
I
don't
care.
I
just
want
my
have
to
run.
I
want
to
scale
when
things
break.
I
don't
want
to
even
hear
about
it.
B
A
Yep
well
we're
coming
up
on
the
top
of
the
hour.
We
have
a
couple
minutes
left
here
if
you're.
If,
if
I,
if,
if
I
called
your
your
director
or
vp
of
marketing,
would
that
person
be
saying?
Oh,
my
gosh,
I
can't
believe
you
were
on
there
for
an
hour
mark
brewer,
and
why
didn't
you
talk
about
the
phone?
C
Yeah,
so
to
to
engage
with
light
bend
is
pretty
simple.
We
we
obviously
provide
a
lot
of
open
source
technology
that
people
take
advantage
of,
but
when
it
comes
to
engaging
with
the
company,
it's
all
about
helping
you
with
your
project,
making
sure
you're
successful
at
building
those
applications
and
they
meet
your
business
requirements.
A
And
you
know
just
just
another
another
plug
you
know:
lightbend
is
available
in
the
red
hat
marketplace
right,
so
people
can
go
to
marketplace.redhead.com,
find
the
light
band
offering
that's
there
and
certainly
if
anyone
needs
to
get
in
touch
with
mark
and
or
hugh,
you
have
mark's
email
right
there
on
the
screen
we're
at
the
top
of
the
hour.
I
am
michael
waite,
and
this
has
been
another
exciting
edition
of
the
openshift
commons
briefings
with
our
operator
partners
from
lightbend
thanks
everybody
and
we'll
see
you
next
week.