►
From YouTube: Jakarta Tech Talk - Unleashing the Power of Jakarta Data
Description
Jakarta Tech Talk - Unleashing the Power of Jakarta Data: Exploring API-driven Data Access for Relational and NoSQL Databases.
Join us for an enlightening presentation on Eclipse JNoSQL 1.0.0, a robust framework that streamlines the integration of Java and NoSQL databases. In this session, we will delve into the latest advancements of Eclipse JNoSQL and discuss the future roadmap for the Jakarta NoSQL specification.
We will showcase the exciting new features and enhancements introduced in version 1.0.0 through a series of live code demonstrations. Discover how Eclipse JNoSQL empowers developers to seamlessly work with various NoSQL databases, including MongoDB, Couchbase, Redis, Neo4J, Cassandra, and more!
During the presentation, we will highlight the key benefits of using Eclipse JNoSQL, such as simplified data modeling, flexible querying capabilities, and seamless integration with Java frameworks. You will learn how to leverage JNoSQL's robust APIs and abstractions to optimize your NoSQL database operations and improve application performance.
Furthermore, we will discuss the significance of the Jakarta NoSQL specification and its role in standardizing NoSQL development within the Java ecosystem. Gain insights into the future direction of Jakarta NoSQL and its compatibility with Eclipse JNoSQL.
Whether you are a Java developer looking to explore NoSQL databases or an experienced JNoSQL user interested in the latest advancements, this presentation will provide valuable insights and practical knowledge. Join us to learn how Eclipse JNoSQL 1.0.0 can simplify your Java and NoSQL integration and pave the way for future developments in the Jakarta NoSQL specification.
A
Hello,
everyone
welcome
to
another
Jakarta
Tech
talk,
my
name
is
Serena
and
joining
us
today
is
utavius
Santana,
who
will
be
presenting
on
the
topic
of
unleashing
the
power
of
Jakarta
data,
exploring
API,
driven
data
access
for
relation
relational
and
no
SQL
databases.
If
you
have
any
questions
for
Octavia
as
we
move
through,
today's
presentation
feel
free
to
ask
them
in
the
chat
or
click
on
the
ask
a
questions
tab
without
any
further
delay.
Otavio
over
to
you.
B
B
B
B
As
you
can
see
here,
every
single
no
single
database
has
a
specific
structure.
For
example,
let
me
show
to
you:
the
key
value
looks
like
exactly
a
map
in
Java.
I
do
have
a
key
and
then
I
will
return
a
value.
Okay,
then
I
have
the
column,
family
or
white
column
where
it
looks
like
the
key
value.
The
exception
is
instead
of
I,
do
have
a
huge
block
like
key
value.
B
I
put
my
information
in
small
piece
that
we
call
column
and
that's
why,
by
the
way
it's
column
family,
we
do
have
a
huge
collection
of
columns.
There
then
documents
where
the
structure
looks
like
a
Json
or
XML
file
and
finally
graph
where
the
main
idea
is
exactly
to
to
do
recommendations
for
you.
So
the
structure
looks
like
a
graph
where
I
do
have
several
relationships
with
relational
database.
I
have
just
three
options.
What
you
want,
one
too
many
and
many
too
many
in
a
single
Direction
with
the
graph
database.
B
B
B
This
application,
this
framework
is
based
on
two
specifications
in
Jakarta
data,
Angel,
Cardinal
SQL,
where
I
will
explain
a
little
bit
both
and
that's
the
structure
inside
the
framework.
So
I
do
have
my
anti,
where
I'm
going
to
use
my
annotations
based
on
that
annotation,
it
will
happen
a
mapping
process.
B
B
So
we
do
have
common
annotations
to
multiple
apis
able
to
do
extensions,
especially
because
nosql
has
a
lot
of
particular
behaviors
that
matter
to
us
and
we
build
several
single
apis.
However,
with
graph
we
decided
to
reuse
Apache
chinkapop
instead
of
have
a
single
one
or
instead
of
create
another
one.
B
The
Jakarta
data
I
will
explain
a
little
bit,
but
by
the
way
who
is
familiar
with
Jakarta
data,
the
idea
is
to
have
async
Repository
and
base.
Oh
okay,
nice.
It
based
on
this
repository
I,
can
integrate
with
several
database
engine.
For
example,
I
do
have
my
business
layer
as
any
kind
of
architecture.
Application
structure
based
on
that
I
have
my
data
access
layer
where
I
don't
care
where
this
data
comes
from,
because
I
will
do
my
have
my
interface
and
this
interface
will
integrate
with
whatever
I
want.
B
So,
if
I
want
you
to
agree
with
SQL
relational
database,
it's
fine.
If
you
want
to
take
it
with
no
Sig
database,
it's
fine
as
well!
And
finally,
if
I,
don't
care
or
I
I
cannot
integrate
with
both
can
use
if
I
wish
web
service
as
well.
So
it's
fine
to
you
to
use
and
for
your
application.
We
have
no
idea,
and
that
is
exactly
the
motivation
behind
Eclipse,
yellow
sequel.
B
B
It's
easy
to
switch
between
those
six
database.
Yes,
it
is
easy
because
of
that,
but
let's
face
it,
we
hardly
ever
do
we
switch
between
no
six
database
on
production
right?
We
hardly
ever
do
a
migration
but
think
about
the
cognitive
loads.
So
if
I'm
using
orange
DB
inside
to
move
on
to
around
DB
I,
don't
need
to
learn
anything
else.
I
can
user
around
DB
right
now
because
I
know
the
syntax.
I
know
the
I
know
the
Imports
I
know
everything
that
I
need
to
do.
B
B
B
If
not,
I
will
move
ahead
so
right
now,
I
will
move
to
my
application
here
where
I
will
run.
Let
me
show
my
Docker
compose.
Let
me
presentation
mode
so
hopefully,
right
now
we
are
able
to
see
better
my
application,
my
so
what's
my
goal.
What
I
want
to
achieve
here
I
will
create
a
single
application,
less
simplest
as
possible
with
Java
SE
and
then
based
on
that
I
will
integrate
with
multiple
apis.
So
I
do
have
my
mongodb
around
DB
and
couchbase.
B
It's
a
common
configuration
here
and
based
on
that
I
will
run
my
single
application.
Okay,
to
make
it
possible.
I
will
include
in
my
imports
a
couple
dependents.
So
it's
running
on
Maven,
so
it's
Maven,
but
of
course
on
top
you
can
I
use
Gradle,
yes,
go
for
it.
The
eclipse
genocycle
has
three
minimal
requirements.
B
B
B
I
will
create
my
Pokemon
I
have
option
here.
So
if
I
want
to
create
an
immutable,
NT
I
can
use
records.
It
is
fine,
but
remember
if
you
go
through
this
way,
you're
not
able
to
change
the
state.
It
does
not
belong
to
Java
itself,
but
it
just
belongs
to
the
Java
specification.
Oh
sorry,
it
does
not
belong
to
Jakarta,
nosiko
or
eclipse
genoc
IDE,
but
to
the
Java
specification
itself.
Okay,
so
just
to
show
that
I
can
I
will
use
records.
B
B
Finally,
I
do
have
my
Pokemon
I
will
come
here
to
my
application,
where
I
have
my
feature,
that
I
will
create
some
Pokemons,
so
I
will
come
here
again
to
my
Pokemon
and
I
will
create
base
on
Faker,
so
public
static,
Pokemon
off
almost
for
Pilots.
Thank
you
for
that
Baker
and
then
what
I'm
gonna
do
I'll
take
fake
Faker,
Pokemon
thing
that
I
can
do
is
to
oops,
so
you
I
can
take
here
and
return
as
far.
B
B
So
I
did
a
random
uid
and
then
a
Pokemon
name,
and
then
my
Pokemon
location
done
so
right
now,
I
do
have
my
Pokemon
ready
to
use
so
I
came
here.
I
will
return
to
my
app
I
will
show
to
you
my
application
running.
My
container
here
is
running
right
now,
I'm
able
to
show
something
so
it's
running
for
a
while
right
now
so
three
hours
ago,
yes,
as
usual,
any
Live
code,
you
need
to
try
in
practice
every
day.
B
B
B
B
B
B
B
B
B
So
I
will
start
with
the
among
DB1
here
so
I
have
my
green
plates.
The
template
is
my
interface,
that
does
the
communication,
and
what
I
will
do
here
is
I
will
do
with
document
information,
so
the
template
is
the
one,
the
initial
one
and
then
I
do
have
a
couple
of
specializations
so
template
to
the
basic
operational
six
database
and
then
I
move
to
each
nosql
type.
Has
one
single
specialization
as
template,
so
document
templates,
column,
templates,
craft
template
and
key
value
template
today.
B
I
will
cover
only,
of
course,
the
document
template,
hey
Octavio,
but
how
about
I
have
particular
behavior
that
I
want
to
use.
For
example,
for
me,
it
makes
sense
to
use
a
let
me
see
particular
behaviors
of
around
DB
particular
behavior
of
couch
base,
or
particular
behavior
of
monkey
B.
So,
of
course,
you
do
have
the
option
to
create
specializations
or
use
those
specializations
on
this
case
templates
the
mod
generic
document
template
to
to
document
operations
and
more
specializations
on
Hmong
DB
template
that
is
implements
that
is
specialization
from
document
table,
H,
okay.
B
B
B
B
B
B
B
B
B
B
Rule
number
one
foreign:
are
you
my
IDE,
okay
I
found
you
so
right
now.
What
I'm
gonna
do
next
is
of
course,
I
need
to
show
one
more
so
I
come
to
files
micro
profile
and
then
I
will
do
something
with
couch
based
documentation,
configuration
and,
of
course,
return.
Here
is
a
cute
this
database.
So,
as
you
can
see
here,
I
create
my
faker,
then
I
did
the
injection,
then
I
search
to
return.
Everything
for
me
so
select,
Pokemons
and
so
on.
B
B
Hopefully
it
will
work
and,
as
you
can
see,
the
structure,
those
structure
is
a
little
bit
different
as
you
can
see,
but
the
concept
is
exactly
the
same.
So
I'm
searching
the
Pokemon
where
it
it
provides
an
ID
on
location
in
the
name
in
terms
of
apis.
What
I'm
doing
I'm
communicating
to
the
API.
This
API
is
translating
to
anal
6
database.
B
We
do
have
the
communication
layer
that
will
receive
some
database
structure
and
then
we
move
this
information
to
the
database
itself.
What
we're
doing
here
is
exactly
the
same
idea,
so
we
are
taking
the
other
six
database,
the
mapping
that
is
the
same.
We
are
switching
the
provider
and
basically,
switching
I
can
use
any
database
that
I
wish
to
use
pretty
pretty
simple.
B
But
hopefully
you
got
an
idea,
so
everything
that
I
will
show
among
DB
I
can
do
on
three
database.
That
session
will
be
the
communication
internally,
so
with
around
DB,
it
will
execute
around
query
language
that
I
showed
to
you
with
couchbase
is
Nico.
That
is
specific
language
for
couch
based.
That's
pretty
much
looks
pretty
similar
to
relational
database.
Sql
and
modb
has
the
Hmong
to
be
query.
So
it's
much
closer
to
Json
future.
B
If
it's
like
this,
but
what
matters
is
I,
don't
need
to
go
deep
on
that,
so
I
do
have
my
Pokemons
I
do
have
my
templates,
What
Can,
I,
Do,
I,
Can,
Do
I
can
run
queries
here.
So
I
did
the
select
and
I
have
a
couple
options.
For
example,
I
usually
prefer
to
use
the
template
with
fluent
API
and
what
does
mean
with
fluent
API.
The
idea
of
fluent
API
is
to
make
easier
and
safe
to
do
queries
inside
my
application.
B
For
example,
here
I
do
have
my
select
and
I.
Don't
need
to
memorize
the
next
step
because
the
API
itself
you
show
for
me
it
each
one
is
my
next
step.
So,
as
you
can
see
here,
I
have
my
where
I
have
my
limit
and
Skip
so
give
it
the
point
that
I
want
to
run
a
query
where
I
wanna
I
want
to
have
my
where
location
or
the
name
is
equals
Pikachu.
So
I'll
do
where
here,
where
oops,
not
you
my
location
equals.
B
B
B
B
So
that
is
that's
the
the
idea,
so
what
I'm
doing
here
is
doing
the
the
query
by
name,
of
course,
what
you
can
do
is
also
to
delete
exploring
the
fluent
API.
So
you
can
do
the
delete
Pokemon
class
and
then
the
Q,
the
query,
or
what
else
you
can
do
is
keeping
that
we
want
to
return
by
ID
so
then
play
it,
find
Buy
the
class.
B
B
You
can
also,
if
you
wish,
you
can
use
a
query
by
Design
query
by
text.
Actually,
the
document
input
itself
does
not
support
this.
However,
what
you
can
do
is
explore
the
specialization,
for
example,
and
document
template
you
can
do
have
Drano
SQL
document
template
right
and
I
can
take
it
here
and
execute
my
query.
So
I
can
have
my
query
here:
okay,
for
some
reason,
the
asset,
what
you
return
the
Pikachu,
so
let's
make
it
happy
returning
Pikachu.
So
what
did
I
do
here?
B
I
have
a
couple
of
Pikachus,
so
one
from
udella,
town,
peridian
and
Flor
Flora,
Roman
town,
so
I
have
three
Pikachu,
okay,
but
support.
You
should
be
different.
Remember
that
every
time
they're
running
I'm,
including
more
random
Pokemons,
so
the
value
is
not
the
same.
That's
why
I'm
returning
more
different
values
of
Pikachu,
for
example?
B
B
B
B
And
I
will
extend
almost
pageable
Repository,
so
yeah
yeah,
you
got
it
right,
and
this
pageable
repository
will
have
two
parameters.
The
first
one
is
my
anti-type
and
the
second
one
is
my
ID
type,
where
I
can
use
So
based
on
that
I
I
can
use
Pokemon
repository
right
now.
I,
don't
need
to
do
anything
else,
it's
ready
to
go
so
whatever
did
you
come
here?
Are
we
right
now
create
a
new
class,
so
I
will
use
the
power
of
cop
and
paste
so
app
number
two:
how
we
will
do
the
injection
of.
B
B
B
I,
don't
need
to
handle
anything
else
and
I
can
create
even
new
methods
that
I
don't
need
to
to
care
about
implementation
itself.
For
example,
I
will
create
a
list
by
the
name,
exactly
like
my
assistance
suggests.
Thank
you
for
that.
So
I'm
doing
it
find
my
name
where
using
the
name
then
I
came
here
to
my
app
I
will
use
my
repositor
here.
B
Let's
see
so
I
got
an
exception
here.
Why?
Because
I
do
have
a
couple
of
implementations,
as
you
can
see
so
I
have
with
key
value.
I
have
with
out
my
document
itself.
What
do
I
need
to
do?
I
need
to
explore
the
qualifiers,
because
I
usually
find
each
one
I
want
to
use
so
I'm
saying
that
I
want
to
use
my
document
qualifier.
B
B
B
B
B
B
If
I
want
to
use
key
value,
you
can
use
key
value
and
if
I
do
have
two
different
implementation
of
no
SQL
database,
it's
fine!
You
can
Define
the
name
of
that
using
the
database
qualifier,
okay.
So
what
did
I
show
for
you
right
now?
So
we
do
have
the
repository
where
I'm
using
single
interface
and
I
don't
need
to
do
the
implementation.
B
Just
to
remember
you,
the
template
is
the
highest
level
of
template
operation.
Then
we
have
several
implementations
so
templates.
The
basic
q
a
noticeable
database
and
then
we
have
specialization
based
on
the
types
document,
type
column,
type
graph
type
and
key
value
type.
All
templates
on
this
case
own
document,
template
I,
can
have
multiple
specialization
on
this
case.
I
do
have
a
wrongdo
temperature,
where
I
have
this
syntax
to
work
with
around
DB
if
I
wish
directly,
instead
of
you,
this
the
other
way
with
Gino
SQL,
modb
couch
base
and
so
on.
B
So
if
everyone
will
have
your
specialization,
if
it
does
make
sense,
then
we
went
through
the
Pokemon
repository.
That's
based
on
Jakarta
right,
Jakarta
data
and
I
did
the
same
thing.
So
I
did
the
same
operation.
So
I
have
my
repository
able
to
do
several
operations
and
the
only
thing
that
I
need
to
do.
Is
you
switch
the
the
provider
if
I
have
a
single
one?
I
don't
need
this,
but
once
I
have
a
couple,
what
did
I
do?
B
I
put
this
provider
and
just
remember
you-
or
we
also
have
a
specialization
here,
so
the
data
Repository
belongs
to
the
specification,
the
crew
repository
to
the
basic
operation,
the
pageable
repository
should
do
the
operation
with
pagination
and
finally,
the
specialization
under
the
low
circle
itself.
So
we
do
have
around
DB
repository
couch
bit
repository
and
mongodb
repository.
Why?
Because
if
we
are
going
to
use
around
the
B
reporter
I
can
use
a
rungo
query,
language
I
can
use
nickel
I
can
use
any
specific
behavior
that
belongs
only
to
mongodb.
B
Of
course
everything
has
a
trade
Office
of
the
engineer.
This
API
is
not
exception.
If
you
go
to
around
DB
you're
not
able
to
switch,
especially
because
there
is
no
wrong
DB
around
the
curve
language
among
DB
or
couch
base.
So
if
you
want
to
learn
in
Easy
switch
onto
page
repository
find,
if
you
want
to
use
particular
Behavior,
you
can
go
through
the
database
repository,
but
it
might
be
harder
to
switch
between
these
providers.
B
That
is
the
idea
of
Jakarta
data.
Where
I
have
my
business
layer,
my
NT
my
repository
and
then
my
implementation-
that,
as
you
can
see,
I,
don't
even
need
to
care
about
it.
I,
don't
even
children
know
about
it.
So
the
data
comes
from
SQL,
no
SQL
and
web
service.
That
is
all
for
today.
Hopefully
you
enjoy
I
guess
there
is
one
question
here.
B
B
Yes,
it's
file,
I
got
lucky
because
I
do
have
the
Json
API
and
everybody
is
using
Json
Jackson,
eyes,
Json
processor,
on
real
world.
We
usually
have
just
one
adapter.
So,
as
you
can
see
here,
I
have
Mong
DB
as
a
penis.
I
have
couch
base
as
a
penis
I
have
around
DB
as
a
penis,
the
dependency
self,
a
handle
by
Maven
or
Gradle,
but
with
when
it
does
have
any
conflict.
B
B
But,
as
I
said,
we
usually
have
one
signification
with
a
single
node
2
database
I
mean
I,
cannot
imagine
scenario
where
you
are
working
with
around
DB
monkey
being
culture
based
on
production
in
the
single
application.
Does
that
answer
the
question
Gregor,
please?
Let
me
know:
okay!
Is
there
any
any
questions.
B
A
Yes,
no
thank
you
very
much
Octavia
for
your
wonderful
presentation
and
just
a
quick
reminder
that
we
are
always
looking
to
book
some
more
Jakarta
Tech
talks
in
the
fall,
so
I'm
gonna
put
a
little
Link
in
the
chats
feel
free
to
click
on
the
chat
on
that
link,
and
it
will
be
the
forum
for
our
Tech
talks
and,
of
course,
we're
always
looking
for
your
feedback.
So
at
the
end
of
this
webinar
we
will
close
it
out.