►
From YouTube: OpenShift Coffee Break - DBaaS Series: Redis
Description
Get your espresso ready for the EMEA OpenShift Coffee Break of the new year as we start our new series about Database-as-a-Service (DBaaS) on Kubernetes at ease with Red Hat OpenShift! Today we welcome Luigi Fugaro, Solution Architect at Redis, in our first episode talking about how create cloud-native applications consuming Redis databases.
Twitch: https://red.ht/twitch
A
A
Good
morning,
good
morning,
everyone
welcome
back
to
the
openshift
coffee
break,
show
after
this
nice
music
for
our
starting
soon.
Today,
I'm
really
excited
to
restart
our
coffee
break
series
episode
with
our
fantastic
java:
hey.
How
are
you
hey
guys?
How
are
you
nice
to
meet?
You
there's
a
train?
What
is
it
that's.
A
D
A
Not
bad,
not
bad
in
this
start
of
the
new
year,
where
we
have
some
some
good
news
jafar
to
to
share.
So
basically
we
we
start
this.
This
is
the
start
of
the
new
series
about
the
database
as
a
service
series.
We
will
focus
in
a
series
inside
our
show.
Our
coffee
break
show
talking
about
how
people
can
use
a
database
database
as
a
service
on
top
of
openshift
and
we're
getting
more
and
more
in
a
cloud
service
mode.
A
We
will
talk
also
about
the
data
service
database
as
a
service
integration,
and
the
second
news
jafar,
is
that
we're
gonna
we're
gonna
go
weekly
into
a
weekly
base,
so
we
have
also
fabio
andrea
helping
us,
so
I
think
it's
great
after
our
last
year,
we
have
let's
lots
of
fun,
but
today
this
year
I
think
we
have
more
more
content.
What
do
you
think
about
it?.
E
A
Yeah,
please
folks.
This
is
opposite.
Coffee
break
the
idea
for
people
that
join
for
the
first
time.
The
idea
of
the
show
is
that
we
share
a
coffee
together,
as
we
used
to
do
no
talking
about
the
offices
about
a
little
break.
Talking
about
anything
and
the
best
idea
came
properly
from
that
coffee
break.
So
we
would
like
to
repropose
that
in
a
let's
say,
a
virtual,
but
also
more
broadened
version.
A
D
I
think
it's
the
more
natural
approach,
I
mean
you
cannot
lie,
you're
you're
live
and
then
there
is,
of
course,
all
this
kind
of
excitement,
because
your
life
is
not
recorded.
Where
it's
it's
more,
I
think
it's
the
best
way
to
do
web
in
our
presentation
and
doing
the
also
live
coding
or
whatever
it
is.
So
I.
E
F
A
A
B
A
Yeah,
the
topic
of
today
is
how
we
consume
databases
on
kubernetes
at
ease,
and
we
think
we
we
we
created
a
good
environment
where
we
have
an
openshift
cluster.
In
this
case,
we
prepared
an
environment
with
a
rosa
cluster,
which
is
a
red
dot
openshift
on
nws,
our
managed
openshift,
offering
and
redis
operator,
but
luigi
can
tell
us
more
and
more
about
it
in.
I
think
you
have
some
slides,
maybe
yeah
yeah.
B
D
D
Okay,
excellent,
so
this
is
actually
a
first
first
in
a
series
about
d
bus,
so
database
as
a
service,
and
we
are
we'll
be.
We
will
be
focusing
on
redis
enterprise
on
openshift
and
see
how
actually
kubernetes
platform
can
deliver
deep
bass
by
nature
by
the
by
design
and
as
already
mentioned
by
by
natalie,
I'm
luigi
fugarro
solution,
architect
at
redis
and
that's
today's
agenda.
So
we
will
first
focus
on.
D
D
And
what
does
it
mean
before
we
can
understand
the
debuffs?
We
need
to
properly
understand
the
traditional
way
or
provisioning
a
server
database,
a
database
server.
So
a
platform-
and
probably
you
start
by
buying
some
hardware
and
on
top
of
that,
maybe
installing
an
os
most
likely
a
linux
server
and
then,
of
course,
you
install
your
software
for
the
database
platform
of
your
of
your
choice,
your
favorite
one-
and
if
you
think
about
this,
there
is
a
lot
of
work
that,
of
course
you
can
automate.
You
can
script
it.
D
A
D
And
and
of
course,
for
the
for
the
software
for
the
database
software
platform
and
of
course,
there
is
also
more
that
you
have
to
do
so.
The
real
challenges
comes
when
you
actually
accept
your
user
to
log
into
your
system,
so
you
have
kind
of
different
users.
Depending
of
the
of
the
access
they
require,
might
be
a
system
administrator,
a
server
administrator,
a
database
administrator.
D
So
you,
you
may
encounter
separation
of
duties
between
all
these
kind
of
personas,
as,
as
I
said,
server
administrator
links,
administrator
system,
administrators
db
administrator.
So
you
need
to
probably
hire
some
specialists
to
manage
all
these
to
operate
your
infrastructure
and
your
architecture.
But
what
actually
means
managing
and
operates
a
database
server
as
a
platform?
D
D
So
you
need
to
restore
them
very
quickly
because
maybe
you're
running
in
production
workload,
and
so
you
need
to
restore
everything
as
soon
as
possible.
You
need
to
be.
You
need
to
think
about
high
availability
about
the
storage,
the
persistency,
so
there
is
really
really
a
lot
of
work.
Automating.
The
whole
thing
is
just
one
side
of
the
kind,
and
there
is
also
another
part
which
is
managing
the
whole
thing.
D
So
the
bus,
that's
the
real
benefits
of
having
a
database
as
a
service
where
all
the
challenges
are
actually
delegated
and
shifted
to
the
database
as
a
service
platform.
So
it
could
be
any
cloud
provider,
so
they
will
take
care
and
they
will
take
care
of
the
installation
of
the
security
of
the
operations
of
the
patching
backup
recovery
and
all
you
need
to
do.
A
D
Hey
just
give
me
your
my
database,
I
want
that
specific
database
platform
give
me
the
endpoint
and
the
credential,
and
I'm
done
so
the
the
real
difference,
then
between
running
your
own
database
and
actually
relying
on
adb
as
a
service.
It's
that
with
running
your
own.
You
have
great
power,
of
course,
and
of
course
comes
great
responsibility,
and
but
you
also
can
have
these
tweaking
and
tuning
all
your
settings
and
to
to
run
the
system
faster.
D
D
You
may
require
a
specific
use
case,
like
active
active
where
you
have
different
database
platform
in
cluster,
both
active
and
different,
maybe
ge
distributed
location,
so
d-bus
is
really
here
to
help
and
of
course,
redis
radius.
Enterprise
has
its
own
proposal
of
the
of
the
d-bus,
which
is
called
radius
enterprise
cloud,
which
runs
on
top
of
the
major
cloud
providers
such
as
gcp
azure.
Aws,
of
course,
can
be
provisioned
using
also
kubernetes
platform
like
the
openshift
red.openshift.
D
So
what
it's
all
about,
of
course,
one
of
the
best
solution
to
deploy
a
platform
on
kubernetes
is
through
the
2d
operator,
so
we
in
radius
enterprise.
We
have
an
operator
which
it
takes
care
of
pretty
much
everything
and
it's
it
deploys
a
stateful
set,
deploy
the
parts
deploy
the
services
and
gets
all
a
bunch
of
things
that
actually
here
is
a
high
level
overview
of
what
can
be
what
can
do
the
operator
for
us,
but
this
is
actually
treat
down
how
it
works.
D
So
we
have
this
operator
which
creates
a
couple
of
custom
resources,
definition
files
which
are
the
rec
redis
enterprise,
cluster
custom
resource
and
the
redis
enterprise
database
custom
resource
and
once
created
they
create.
Of
course,
the
operator
takes
care
of
creating
the
the
secret
for
to
access
and
to
manage
the
cluster
creates
the
set
full
set,
so
it
provision
the
states
full
sets
around
the
the
openshift
nodes,
create
the
servers,
the
service
to
access
all
these
resources
and
the
ui,
and
then
also
provision
the
secret
to
access
the
database
and
the
difference
between.
D
F
D
So
there
is
a
nice
user
interface
to
create
a
database
with
a
bunch
of
options
and
also
there
are
lots
of
metrics
that
are
exposed
via
format
use,
but
also
directly
in
the
user
interface.
You
can
see
all
these
all
these
metrics
going
back
to
the
open
shift.
Those
are
the
samples
of
radius
enterprise
database,
manifest
files.
Here
on
the
left,
we
have
like
a
small
database
where
you
actually
have
100
megabytes
of.
F
D
Live
webinar
of
these
debuffs
series
and
on
the
on
the
right
side,
we
have
the
full
specification
of
the
manifesto,
so
all
the
options
that
you
can
use
and
in
regards
to
the
deployment
you
as
you
know,
on
kubernetes
and
so
on
on
openshift
as
well,
we
have
the
so-called
namespace
project
for
openshift.
So
how
you?
Actually
you
can
create
the
radius
enterprise
cluster
within
openshift.
You
can
relay
the
entire
cluster
onto
a
single
project
with
a
single
database
or,
of
course
you
can
have
a
single
in
so
a
single
project.
D
One
cluster
with
multi-tenancy
enabled
multi-tenancy
means
you
can
have
different
databases
within
the
same
cluster.
They
are
completely
isolated
and
they
have
their
own
errorback
and
scl
things.
So
every
every
database
that's
on
endpoints
and
and
of
course,
we
also
provide
the
multi-project
and
multi-tenant
deployment.
What
we
do
not
support
it's
adding
into
a
single
project,
multiple
cluster.
This
is
not.
This
is
not
allowed
allowed,
also
for
kind
of,
because
also
of
the
gaming
convention
and
and
so
on,
and
so
without
going
too
much
in
details.
A
Before
before
that,
I
would
like
to
first
thanks
for
this
great
presentation,
because
the
help
understand
how
we
can
manage
you
know.
Databases
in
kubernetes
are
something
that
if
you
talk,
if
you
tell
to
people
hey
what
about
database
and
kubernetes
they're
gonna
say
I
don't
know
because
there's
a
complexity,
you
know
that
you
have
to
manage,
but
the
operators
is
the
really
first-class
citizen
in
kubernetes
helps
managing
events.
A
The
life
cycle,
the
reconciliation,
reconciliation
loop,
the
reconcile
loop
of
the
kubernetes
lifecycle
management,
so
you
can
deploy
your
topology
as
you
were,
are
showing
here
with
the
single
tenant
multi-tenant
active
active.
So
this
is
this
complexity
of
deploying
and
maintaining
stuff
is
managed
by
the
operator,
and
that
makes
the
thing
easier
and
negative
to
kubernetes.
So
I
think
this
is
the
big
plus,
the
second
big
plus
luigi.
I
would
like
to
mention
you
to
your
you.
A
You
show
has
a
reddish
enterprise,
but
I
want
to
mention
that
redis
enterprise
is
also
a
certified
operators
in
red
that
marketplace.
So
I'm
gonna
share
also
in
the
chat
the
link
in
the
from
of
the
reddit
catalog,
where
you
can
look
for
any
software
in
this
case
for
kubernetes
packages
as
an
operator.
A
So
the
redis
enterprise
that
luigi
was
talking
about
is
a
certified
software
for
openshift
and
when
you
click
here,
you
can
start
deploying
using
it
in
inside
your
openshift
cluster.
There's
the
documentation,
there's
the
all
the
steps,
the
component
so
there's
a
list
of
certified
software
for
for
openshift
and
redis
enterprise
is
part
of
it.
So
it's
really
cool
that
we
have
also
an
ecosystem
of
software
which
is
certified
and
packaged
as
an
operator.
In
this
case,
of
course,
you
can
use
either
enterprise
and
community
operators.
D
Yeah
text
entirely
also
what
the
redis
enterprise
operator
does.
It
also
enables
you
to
use
admission
controller
where
you
can.
Actually
it
validates
your
database
manifest
files
before
you
deploy
them.
It
validates
and
checks
everything.
If
everything
is
compliant
to
your
rules,
then
it
gets
deployed,
and
so
the
operator
manages
the
whole
thing
day.
One
operation
day,
two
operation
maintenance,
update
roll
up
the
rolling
update
everything
for
you.
A
Right,
oh
before
before
we
we
move
into
the
demo,
which
is
the
coolest
part.
No
any
any
question
from
you
fabio,
andrea
jafar.
I
see
in
the
chat.
There's
the
people,
that's
joining
hi
everyone.
There
are
also
luigi
fan.
I
think
there's
lots
of
people
for
luigi.
So
that's
great!
That's
why
we
you
we
invited
you
and
yeah
any
any
thoughts.
Folks.
B
F
A
B
D
Yeah
guidance,
details
yeah
the
the
operator
actually
watches
for
everything
that
happens
in
the
radius
enterprise
cluster,
the
radius
enterprise.
A
software
actually
has
a
certain,
an
automation
mechanism
that
watches
all
the
instances
all
the
shards
and
whenever
some
and
whenever
something
goes
wrong,
it
applies
triggers
developer
of
that
particular
instance
nodes
whatever
it
is
so
once
you,
for
example,
if
you
lose
a
master
automatically,
a
replica
would
be
promoted
as
a
master.
So
there
is
no
interruption
in
terms
of
client
connection.
The
data
there
is
no
data
loss.
D
There
is
nothing
that
that
happens
in
those
kind
of
situation
and,
of
course
there
is.
There
are
also
mechanism
that
once
a
node
actually
comes
back,
you
can
also
have
those
kind
of
fail
back
to
re-migrate,
eventually
or
all
your
data
set
to
that
specific
node.
If
that
node
has
some
particular,
I
don't
know
much
resources
in
respect
to
the
other,
and
so,
but
this
is
something
that
you,
of
course
you
can.
D
This
is
all
these
automatic
automations
are
because
of
the
radius
enterprise
with
the
radius
open
source.
It's
a
bit
different.
You
have
to
do
it
manually.
You
have
to
configure
different
components.
So
it's
a
bit
tedious
with
redis
enterprise.
Everything
is
done
with
the
with
the
operator
on
overshift,
okay,.
B
E
Yeah
so
I'll
have
another
question,
but
maybe
we
can
keep
the
answer
for
after
the
demo.
What
I'll
be
interested
in
is
to
understand
your
main
use
cases
like
for
what
use
cases
your
customers
mainly
use
regis.
If
you
have
something
that
can
explain
that
that
would
be.
You
know
what
are
the
the
strengths
of
of
radius
when
you
are,
you
know,
in
an
application
architecture,
I
would
say.
D
We
are
seeing
the
adoption
of
redis
also
for
cdc,
so
change
the
capture,
use
cases
so
to
to
receive
those
updates
from
let's
say
legacy
database
and
then
store
bring
everything
at
the
on
on
redis
and
then
eventually
redistribute
with
messaging
certification
or
with
stream
to
other
system
of
the
of
the
architecture.
Those
are
mainly
the
use
cases
where
you
you
see.
The
adoption
of
redis
reduce
enterprise,
but
can
be
really
in
terms
of
industries
any
any
industries
as
a
as
a
use
case.
D
E
E
E
D
A
So,
just
to
give
a
quick
context
we
prepared
with
luigi
we
gave
to
luigi
an
openshift
cluster.
This
is
a
managed
openshift
cluster
on
rosa
red
that
openshift
on
aws.
We
created
the
from
the
hybrid
cloud
console,
so
it
was
very
easy
to
create
this
question
and
and
prepare
the
cluster
for
the
demo.
So
this
is
a
4.9
cluster
that
means
kubernetes
122.
A
A
So
this
is
the
operator
hub,
which
is
the
our
marketplace
inside
the
cluster,
where
you
can
pick
your
favorite
software
and
and
use
and
order,
in
this
case,
with
luigi,
we
ordered
at
redis
database,
which,
if
you
look
for
redis
here,
what
what
we
we
installed
in
in
our
demo
is
the
community
operators,
which
is
the
a
radius
community
operator
just
so
yeah.
What
we
did
is
just
install
the
operator
and
then
we
were
able
we
will
be
able
to
consume
it
in
in
the
demo.
A
F
A
So
those
are
prometheus
extracted
metrics,
so
a
developer
can
look
at
the
application
and
then
look
of
all
the
set.
In
this
case,
we
we
created
some
some
some
cluster
from
the
operator.
It's
cool
that
you
have
also
this
metrics
overview,
where
you
can
check
all
all
the
all
the
settings
and
you
can
manage
alerts.
Events
with
prometheus
yeah,
yeah.
F
A
F
F
D
E
A
B
A
Here,
if
you
see,
we
created
those
radius
instances
just
using
the
operator
custom
resource,
so
those
are
clicking
on
one
of
this.
It's
just
a
it's
just
a
customer
yaml
file.
If
you
click
on
yaml
describing
hey,
I
want
to
read
this
class.
I
want
to
read
this
class
with
one
replica
in
this
case.
I
want
to
start
with
from
this
container
image.
I
want
this
settings
similarly
to
what
luigi
showed
for
about
redis
enterprise,
which
has
more
settings
right,
more
control
in
this
community.
C
A
A
A
Okay,
yeah,
so
luigi
prepared
an
application.
I'm
gonna
share
in
the
chat
the
source
code
of
this
application,
so
you
can
at
which
you
can
also
share
in
the
screen,
your
application
just
to
to
show
to
the
people
what
we
which
application
we're
going
to
use
for
the
demo.
I
put
the
link
in
the
chat
and
you
can
show
the
chat
in
yeah
you
should
see.
A
A
A
F
F
A
Oh
okay,
because
we
are
not
using
the
fully
qualified,
maybe
luigi,
we
can
use
just
the
route,
the
openshift
route,
which
is
that
if
you
go
down,
is
the
url
exposed
outside
and
also
if
you,
if
you
yeah,
if
you
share
in
the
chat
in
the
private
chat,
I
can
share
to
the
people.
So
the
people
can
see
that
the
application
is
up
and
running
in
our
live
demo
and
they
can
check
it.
F
A
C
F
E
E
A
Oh,
that's
fine.
I
think.
Let
me
check
also
over
here.
Maybe
it's
just
a
copy
and
paste
stuff.
Oh
yes,
I
copy
and
paste
stuff
because
I
was
able
to
do
from
my
terminal.
Let
me
copy
to
you
in
in
the
private
chat:
it's
yeah.
It
was
a
copy
and
past
issue.
If
you
go
to
the
private
chat,
I
have
the
right
one.
F
A
A
A
A
A
A
A
A
D
So,
basically,
what
we
did
is
actually
we
deploy
this
with
the
source
to
image
so
connect
it
directly
to
the
github
repo
and
then
the
open
shift
did
the
magic
and
then
we
just
drag
and
drop
the
the
arrow
to
the
redis
standalone
instance
and
then
the
application.
Now
it's
bound
to
that
specific
database
and
point,
and
so,
as
you
can
see
from
there.
Finally,
the
core
commands
we
can
actually
enter
the
data
into
into
redis.
E
D
Yeah,
let
me
show
you
actually,
I'm
relying
on
the
spring
data
radius,
which
actually
has
inside
the
two
redis
client
drivers,
jetties,
let's
use,
and
so
the
old
things
actually
happens
at
that
level.
So
I
need
actually,
I
had
to
specify
my
movie
repository,
like
any
other
spring
data
repository.
I
don't
know
if
you're
familiar
with
with
spring
and
then
this
actually
it's
cream
embedded
into
the
the
controller
which
has
all
the
get
mappings
and
posts
and
boots
and
whatever
to
do
all
the
things
and
that's
it.
D
That's
the
only
thing
that
you
have
to
do,
and
one
thing
maybe
to
to
notice
is
the
redis
configuration
where
you
can
actually
tweaking
and
tuning
your
database
and
point
where
you
can
actually
apply
defaults
and
everything's,
and
then
you
can
specify
which
connection
factory
to
use
and
so
which
driver
to
use
eventually
how
to
serialize
the
values
of
the
of
the
of
the
object
that
you
want
to
store
in
the
red
is
right.
Now,
I'm
using
jackson
to
json
as
a
json,
serializer
and
so
really
depends,
and
then
you
have.
D
We
might
also
look
at
the
the
models
which
are
actually
possible,
just
annotated
with
redis
hash.
So
in
this
case
it's
just
a
list
of
attributes
and
values,
and
then
I
also
use
the
at
id
annotation
so
because
red
is
actually
a
nosql
database
and
specifically
it's
a
key
value
store.
So
we
have
we
need
to
specify,
which
is
the
key
in
this
in
these
poshes
to
be
used.
D
So,
okay,
nice,
nothing
really,
especially
very
very
easy,
and
also
we
have
we
just
released
redis
om
if
you're
familiar
with
the
or
rm
object,
relational
mapping
framework.
We
have
one
for
for
radius,
which
is
drops,
of
course,
the
relational
thing,
and
so
we
have
an
op-edge
mapping
just
for
radius
and
we
have
released
it
for
spring.net,
node.js
and
python.
So
it
will
easy
all
your
your
coding
and
just
relying
on
annotation,
for
example,
for
the
from
spring,
so
very,
very
easy.
B
A
There
are
support
from
the
framework
like
springboot
and
quercus.
This
is
the
lens
client,
so
in
the
same
way
that
we
just
showed
on
how
to
add
to
a
spring
application,
the
ready
support
this
is
the
only.
This
is
how
you
can
have
the
redis
connector
to
a
parkour
space
application,
so
fabulous
sharing
the
chat
already.
A
And
I
also
wanted
to
to
share
in
the
chat,
so
we
we
showed
with
luigi
there's
this
redis
application,
which
is
in
this
case,
is
a
springboot
application
connected
to
the
redis
database.
If
you
want
to
use
the
service
binding
operator,
which
is
the
one
that
operation
web
console,
allow
you
connecting
application,
avoiding
the
complexity
of
managing
manually
mapping,
environment,
variable
secrets,
there's
a
library
that
you
can
use,
and
it's
this
one,
the
spread
in
this
case
it's
the
spring
cloud
bindings
and
for
quarkus.
A
If
you
want
to
use
it
for
quarkx,
actually
there's
another
library
that
you
can
use.
That
seby
was
kindly
sharing
with
me,
which
is
this
other
one,
I'm
putting
in
the
chat,
which
is
the
service
binding
for
kubernetes.
So
when
you
use
the
these
libraries,
you
can
allow
the
connection
automatically
between
the
the
two
and
it.
I
think
this
make
easier
the
life
of
the
developer
on
kubernetes
without
having
to
struggle
much
on
how
to
manage
connection,
how
to
connect
to
database.
A
D
And
okay,
just
skipping
the
details
about
every
single
deployment,
single
name,
space,
single
multi-instance,
etc.
We
did
the
demos.
Few
view
recap
just
regarding
the
d-pass,
what
you
should
focus
when
choosing
80
bus
platform.
So
again,
high
availability,
resilience,
scalability
performance
flexibility.
This
is,
I
think,
very
important
to
to
choose
between
the
on-premise
or
clouds.
D
That
means
we
already
registered
our
dbas
solution
within
openshift
and
automatically
openshift
discovers
all
the
debuffs
and
points,
and
you
just
select
your
database
of
choice
and
there
you
go.
You
have
your
dbas
point
directly
into
the
the
pop
topology
and
here
again
drag
and
drop,
but
for
real
without
any
manual
coding
or
settings,
and
you
you
just
drag
it
the
row,
the
arrow
and
then
it
gets
bound
to
the
database
to
the
endpoints
wow.
D
A
Yeah
thanks
for
mentioning
it,
I
have
had
also
a
quick
chat
with
the
engineering
and
the
product
manager,
so
the
red
data
business
service
had
on
john
will
be
available
february
and
ready
support.
Will
we
will
have
read
support
by
april,
as
far
as
I
understood
so
that's
very
cool
because,
as
luigi
was
showing
here
in
the
slide,
basically,
you
connect
your
application
in
your
openshift
cluster
to
a
sas
service.
So
the
redis
database
in
this
case,
which
is
not
in
this
cluster,
but
it's
on
redis
cloud.
A
A
Super
super
cool.
Let
me
check
if
we
have
any
question
about
this,
I
also
share
in
the
chat
the
link
to
red
dot
openshift
database
access.
This
is
the
new
service
that
allow
openshift
user
to
connect
to
any
database
as
a
service
available
for
supported
in
in
this.
In
this
feature,
so
you
can
add
your
operation
cluster
connect
to
any
database
as
a
service,
as
the
redis
cloud,
one
which
will
be
available
should
be
available
in
by
april.
A
So
looking
forward
to
it,
we
don't
have
an
additional
question
in
the
chat,
but
thanks
everyone
for
joining
and
making
interactions.
So
we
we
have
some
few
minutes
left.
I
was
wondering
if
you
andrea
fabio
jafar,
do
you
have
any
additional
question?
Also
about
this?
This
thing
with
the
lightest
finger
that
we
we've
seen
that
ruiji
discusses
about.
C
D
It's
it's
an
architecture
that
you
can
build
with
the
redis
enterprise,
where
you
have
one
redis
enterprise
cluster,
on
one
side
which
can
be
inside
openshift,
using,
for
example,
virtual
machines
or
maybe
on
the
cloud,
and
then
you
have
another
separate
cluster
active
again
and
which
may
be
on
premise
on
whatever
infrastructure
you
have
and
all
those
two
clusters
connect
together
and
sync
the
data
together.
So
it
can
be,
of
course,
a
distributed.
Geographic
geographically,
for
example,
in
different
cities
on
different
regions
and
all
the
thing
happens.
Real
time
and
radius.
D
Enterprise
has
a
technologies
which
is
called
conflict
data,
replication
type,
which
actually
merges
and
resolves
all
the
conflicts
of
writing
the
same
set
on
different
cluster
together
at
the
same
time.
So
it
prevents
any
any
conflicts
and
merge
correctly
all
the
data.
So
you
can
actually
really
have
two
separate
clusters
active,
active
together
and
without
any
problem
and.
C
C
D
Yeah,
well,
the
the
all
the
sharded
instances
of
the
the
of
radius
enterprise
has
to
be
in
the
same
cluster,
of
course,
because
that
the
workload
has
to
be
distributed
in
that
specific
cluster.
But
the
data
can
be,
of
course
it
gets
replicated
to
the
other
cluster
back
and
forth.
So
there
is
no
priority
which
one
where
you
write
all
right,
so
it
depends
also
on
your
location
depends
on
the
networking.
D
Maybe
you
are
in
america,
it's
better
that
you
use
the
american
cluster
rather
than
the
european
cluster,
for,
of
course,
latency
issues
and
so
on.
So
but
everything
gets
synced
and
replicated
together
without
any
conflict,
but
the
data
volume,
the
data
set,
is
actually
managed
by
one
single
cluster.
E
So
so,
actually
let
me
rephrase
maybe
the
the
question
andrea
and
let
me
know
if
that's
what
you
you
meant
so,
for
instance,
when
we
speak
about
central
architecture
and
edge
deployments.
Usually
we
try
to
minimize
the
footprint
on
the
edge
workloads
yeah.
So
andrea
did
you
mean,
for
example,
you
are
going
to
have
a
full-fledged
highly
available
radius
cluster
on
the
central,
but
on
the
edge
you
only
have
one
replica
or
something
like
that.
Is
that
what
you
meant.
A
All
right
folks,
we
arrived
at
the
end
of
this,
show
I'm
really
happy.
We
have
the
show.
We
started
this
database
as
a
series
database
as
as
a
service
series,
and
we
started
with
ouija,
because
we
have
the
great
conversation,
great
slides,
great
democrat,
talk
and
great
question
thanks,
also
andrea.
For
this
twist
it
was
really
interesting.
I
would
like
to
end
our
show
just
with
some
quick
reminder
today.
Please
check
our
calendar
at
openshift
tv
to
see
what
are
the
other
session
that
we
have
today
today.
A
For
instance,
we
we
should
have
the
level
up
hour
and
hasken
and
openshift
admin,
so
you
can
stay
on
openshift,
tv
and
and
follow
us
also
in
this
show,
and
also
we
we.
I
would
like
to
remind
the
next
appointment.
We
will
keep
bi-weekly
for
january.
Then
we
will
move
weekly
by
february.
So
next
appointment
for
us
is
february
26th,
another
database
as
a
service
episode,
probably,
and
and
also
I
would
like
to
leave
you
some
some
reference
from
luigi.
A
I'm
gonna
share
his
twitter
on
our
on
the
chat.
So
if
you
would
like
to
follow
luigi
and
check
news
from
what
he's
doing
here
at
reddy's,
that
is
the
twitter
handle
and
and
and
now
yes,
I
would
like
to
thank
luigi
for
this
joining
us
today.
It
was
really
great
to
start
this
new
year
series,
all
together
with
luigi
fabio,
andrea
jafar.
Thank
you,
everyone
for
joining.
Thank
you.
Everyone
for
attending
and
yes,
see
you
next
time.
Ciao
have.