►
From YouTube: The Apache Cassandra® Corner podcast w/ Otavio Santana
Description
For this episode, Aaron catches up with Otavio Santana, one of our guests from the first season. They discussed Otavio's new book "Persistence Best Practices for Java Applications" which was just released on Aug 25th. Listen in as Aaron and Otavio discuss how Cassandra fits into the landscape of Java application persistence, the role that cloud native tech plays, as well as practices for building good DTOs in Java.
A
A
A
B
A
A
A
A
B
A
A
B
I
explain
a
little
bit
more
about
what.
Unfortunately,
we
don't
cover
enough:
the
persistence
layer
inside
the
application,
I
use
Java,
but
you
can
apply
these
ideas
through
any
language
itself
for
sure
sure,
I'll
explain
the
refactoring
the
migrations,
especially
because
we
do
have
a
lot
of
amount
of
books
around
stuff
that
design
partners
and
application
side
refactoring
and
things
like
that
and
on
a
database
site.
First,
the
refactory
is
also
trivial,
like
we
do
with
application
with
the
code
right
right,
you
might
need
to
do
a
migrations.
You
feel
like
that.
B
We
do
have
a
huge
challenge,
because
when
we
do
our
first
modeling
in
our
application,
it's
usually
time
that
you
don't
know
enough
about
it
right
so
how
to
handle
with
this
kind
of
thing
and
the
impact
of
design
that
are
you
gonna
use.
For
example,
if
you
go
to
use
repository,
that
is
one
impact.
If
you're
gonna
use
data
access
objects,
there
is
another
impact,
so
unstructured
module.
That
is
trade-off
among
off
of
the
solutions
and,
furthermore,
I
will
cover
especially
the
the
type
of
java
Frameworks,
covering
no
secret
database
and
basis.
B
A
Right
right,
you
know,
you
know
you
bring
up
an
interesting
point
there.
You
know
when
you
you
mentioned
that
there
are
a
lot
of
books
out
there
about
like
application,
building
and
application
design
patterns,
but
really
it's
that
it's
that
data
layer
where
there's
there's
kind
of
a
gap.
You
know
where
you
just
don't
see
the
same
amount
of
information
out
there,
as
as
you
do
on
on
the
application
side.
You
know
that's
and
that's
something
I've
I've
noticed
too,
and
you
know
the
over.
A
B
A
B
Because
nobody
explained
to
us
the
impact
that
on
production
right
right
and
nobody
wants
to
tell
the
federal
case
and
I
came
up
with
this
book.
Saying:
hey
guys,
I
failed
that
stuff,
you
don't
need
to
go
through
this
way.
I
failed.
This
step
I
mentioned
some
ideas
around
Legacy
modernization
strategy
to
explore
more
CDC.
But
yes,
hopefully
it
will
help
more
and
complete
the
gap
of
the
documentation
and
guys
on
the
database
side.
A
A
B
Mean
I
get
emotional
with
Cassandra,
but
be
honest
when
you
talk
about
high
performance,
scalable
application,
especially
with
vertical
needs,
I,
don't
feel
anything
else
than
Cassandra
I
mean
the
maturity
of
the
bank
is
also.
There
is
a
huge
documentation
using
Cassandra
right
now.
Cassandra
was
one
of
the
first
database
that
put
the
documentations
modelings
in
types
inside
the
documentation
itself.
A
A
B
Some
some
trade-offs
around
secondary
index,
I
mean
and
so
on,
and
the
point
here
is
Cassandra
is
Cassandra.
Has
a
huge
maturity?
Has
a
huge
Community
has
a
huge
user
case?
Has
several
samples
around
the
configuration
it's
much
easier
to
choose,
calling
with
Cassandra
for
example?
Then
some
providers,
like
even
SQL
database
I,
mean
I,
can
use
few
nodes
and
automatically
they
will
do
the
handshake
and
do
the
load
balance
with
codes.
Loadback,
yeah.
A
B
B
How
to
use
the
use
defined
type
because
there
are
tricks
that,
oh
sure,
people
still
believed?
Okay,
it's
like
a
one-on-one
relationship.
No,
don't
do
that!
Don't
try
to
do
relationship
in
the
application
layer,
don't
try
to
create
links
because
a
huge
mistake,
Explore
More,
the
query
driven
away
I
mean
I,
want
to
retrieve
that
information
modeling
through
this
way,
and
you
have
a
huge
amount
of
this
kind
of
thing.
On
Cassandra
I
mean
you
have
a
lot
of
books
around
Cassandra
as
well.
Yeah.
A
Yeah
and
that's
a
good
point
you
bring
up
too
about
you,
know:
Cassandra's
maturity,
level
where
it's
I
mean
it's
been
a
thing
now
for
I
mean
it's
been
around
for
like
15
years,
I,
I.
Think
if
you
you
look
at
everything
going
all
the
way
back
to
you
know
like
like
2008
or
so,
but
yeah
I
mean
you
know
this.
This
is
something
that
we've
seen
recently
too
in
one
of
the
one
of
the
user
surveys
that
that
Patrick
McFadden
just
did.
A
B
A
B
Idea
is
not
to
replace
anything
else
in
the
book.
That's
why
I
usually
enjoy
to
put
reference.
Okay,
read
this
read
this
the
documentation,
that
is
amazing.
It
become
every
day
even
better
and
better
explore
that
and
I
include
more
about
okay.
This
is
the
unity
how
to
use
how
I
did
and
become
more
accessible
and
easy
to
use,
understand,
and
things
like
that.
A
Yeah
yeah,
so
you
know
one
thing
that
you
know
your
your
book
talks
about
quite
a
bit
too
is
the
the
dtos,
the
the
data
transfer
objects.
Can
you
explain?
You
know
a
little
bit
about
like
you
know
how
these
relate
to
you
know
like
Cloud
native
services,
and
you
know
kind
of
their
kind
of
their
role
in
the
architecture.
B
Yes,
yes,
there,
it
is
more
around
more
than
an
architecture.
Right
I
mean
you
usually
go
to
hexagonal
model
or
even
try
to
isolate
the
entry
through
the
database
modeling,
and
because
of
that,
we
also
try
to
isolate
while
go
through
the
UI
or
the
rest.
Api
right
and
data
transfer
object
can
help
you,
so
you
can
explicitly
say
that
all
is
coming
out
through
your
domain.
B
B
B
Can
I
do
I
can
change
the
modeling
if
without
change
my
entity,
if
I
do,
for
example,
the
hexagonal
model
or
explaining
about
UI
I
can
do
versions.
So
the
version
number
one
has
one
kind
of
information.
The
the
version
number
two
has
another
kind
of
information,
so
with
video
I
can
isolate
the
UI
identity
and
data
modeling.
A
B
B
It
when
you
do
have
dto
you're
able
to
refactor
the
NT,
if
not
impact
the
view,
and
you
can
also
change
the
view
if
without
impacted
the
empty.
So
it's
a
win-win
situation.
I
enjoy
a
lot,
especially
when
my
API
is
consumed
by
a
lot
of
people.
I
mean
several
teams,
it's
so
easy
to
say:
okay,
I'm
gonna
break
this
point
in
the
National
boy
right.
A
B
B
What
is
the
impact
if
I
decide
to
use
oriented
objects?
Programming
instead
of
using
data?
Oriented
programming,
I
mean
when
everybody's
talking
about
this
right,
but
that
is
the
impact.
If
you
do
this
way,
there
are
consequences
to
be
closer
to
the
business,
with
the
D
or
close
to
the
database.
How
can
I
deal
with
that?
B
A
little
better?
The
flavors
of
no
secret
database
understand
better
the
impact
of
mapping
through
reflection
and
so
on.
So
hopefully
you
will
enjoy
the
book
and
hopefully
I
help
you
to
listen
better,
the
universe,
the
huge
universe
that
is
inside
the
physicist
layer
and
try
something
else.
The
relational
database
like
Cassandra,
if
I
got
those
points
for
you,
I'm
super
happy
to
to
help
you
with
this
book.
A
A
A
So,
hey
everyone
Octavio
this
is
this-
has
been
really
great.
It's
always
awesome
having
you
on
the
show
and
getting
to
talk
to
you
folks,
out
out
there
listening
Octavio's
new
book
is
called
persistence,
best
practices
for
Java
applications
and
it
is
available
as
of
today
out
on
out
on
Amazon,
so
hey
otavio.
Thank
you
so
much
for
coming
on
again.