►
From YouTube: Getting Started with Jakarta NoSQL and MongoDB | Jakarta Tech Talk | September 15, 2021
Description
This presentation will provide an overview of the Jakarta NoSQL specification, introduce the four NoSQL database types, and demonstrate a Jakarta NoSQL application that interacts with a MongoDB database.
A
Hello,
everyone
and
welcome
to
another
jakarta
tech
talk
joining
us
today.
We
have
michael
redlich
discussing
getting
started
with
jakarta,
nosql
and
mongodb.
Michael
is
a
senior
research
technician
at
exxon,
mobile
research
and
engineering.
He
has
enjoyed
numerous
assignments
with
the
company,
including
automotive
testing,
analytical
sciences,
practicing
infrared
spectro
spectroscopy
in
chemical
mechanics
and
developing
scientific
I.t
applications.
A
B
Okay,
great,
thank
you
hayley
for
the
introduction.
Thank
you
for
reading.
You
know
my
background
at
excel
mobile.
It's
it's
been
a
32
year,
almost
32
years
with
the
company
so
and
I'm
looking
forward
to
retiring
within
the
next,
oh
two
to
three
years,
so
so
yeah
welcome
today.
B
Thanks
for
for
coming
out,
I
I
must
let
you
know
that
if
I
look
sweaty,
I
am
it's
because
our
site
experienced
significant
fluid
in
our
central
plant
and,
as
a
result,
our
ac
has
been
down
so
but
anyway
yeah
those
were
you
know
it's
very
warm
on
here.
So
so
this
is
me.
B
B
I've
been
running
the
garden
state,
job
user
group
for
the
past
20
and
a
half
years,
although
for
almost
the
last
year,
it's
it
was
under
it's
under
this
name
now,
but
it
was
under
the
acg
ajava
group
before
that
and
we
went
nonprofit
about
a
year
ago,
I'm
also
on
the
leadership
council
of
the
jakarta
ee
ambassadors.
So
I
spent
a
lot
of
my
free
time
in
in
the
java
space.
B
So
the
objectives
for
this
for
this
morning
is
you
know
what
is
jakarta
nosql
you
may
have
heard
references
to
eclipse
j,
no
sql.
B
We
want
to
cover
some
j
or
some
no
sql
database
types
discuss
the
nosql
layers
and
the
best
part,
of
course,
which
you
know
is
everybody,
looks
forward
to
is
the
demo
and
we'll
see
if
something
can
break,
because
you
know
things
always
go
on
when
you
do
these
things
live
and
then
discuss
some,
no
sequel
resources
and
how
to
get
involved
as
well.
B
Okay,
so
jakarta,
no
sequel,
okay!
This
is
one
of
the
specifications
under
the
jakarta
ee.
It
is
at
the
moment
not
under
the
profiles
and,
like
you
know,
the
platf.
The
web
profile
or
the
corp
profile,
otavio
santana,
is
the
spec
lead
and
this
specification
looks
to
streamline
all
you
know:
the
integration
of
java
applications
with
nosql
databases,
and
there
are
many
of
them
out
there
and
when
I
first
started
studying.
B
B
I
have
made
a
you
know
a
handful
of
contributions
so
far
and
I
look
forward
to
doing
many
more
and
just
so
you
know
all
the
specifications.
You
know
any
java
group
if
you
happen
to
belong
to
one
or
lead
one
and
if
you're
interested
in
adopting
any
of
the
specs,
you
can
go
ahead
and
do
so.
I
forget
what
the
url
is,
but
you
can
try
to
look
that
up
and
you
can
follow
the
process
how
to
do
that.
B
So
eclipse
jnosql
is
the
compatible
implementation
of
this,
and
there
is,
you
know
for
all
database
types.
There
is
one
defined
api
and
we'll
talk
about
those
database
types
in
a
minute
and
there's
a
consistent
use
of
annotations
to
map
java
object
and
you'll
see
some
some
references
to
annotations
from
the
relational
database
world.
So
I'm
going
to
do
some
comparisons
to
that
as
well.
B
B
So
the
key
value
you
know
the
cartoon
there
I
apologize
for
that
there
is
a
line
going
from
apollo
to
sun
and
so
on.
So
the
key
value
is
the
simplest
of
all
the
nosql
databases.
The
client
is
allowed
to
get
a
value
for
a
specific
key,
assign
a
value
and
delete
the
key.
So
there's
a
lot
of
flexibility.
There
value
itself
can
be
any
type
it
could
be.
B
You
know
the
binary,
large
object
or
blob
or
anything,
and
it's
the
responsibility
of
the
application
to
know
what
is
being
stored
and
because
this
is
very
simple.
The
performance,
of
course,
is
you
know
quite
scalable
and
and
quite
easy
to
be
to
be
scaled
use,
cases,
storing
session
data,
maintaining
schema-less
user
profiles
and
storing
user
preferences.
B
B
Comparing
a
key
value,
nosql
type
to
a
relational
database,
as
you
can
see
on
this
table
here,
so
a
table
would
be
referred
to
as
a
bucket
and
a
row
would
be,
you
know,
would
be
considered
a
key
value
pair
in
in
that
nosql.
B
B
The
main
advantage
over
a
relational
database
would
be
a
faster
search
and
access,
and
actually
data,
aggregation
and
use.
Cases
for
this
will
include
content
management
systems,
blogging
platforms
and
applications
that
will
require
heavy
write
requests
such
as
log
aggregators,
for
example.
B
You
may
want
to
avoid
using
no
sql
type
if
there
are
a
lot
of
complex
queries.
So
an
example,
databases
include
cassandra
and
apache.
B
And
similarly,
here
here's
the
the
the
differences
between
the
two
here
versus
you
know:
relational
versus
column,
family
and
there's.
No
there's
no
relationship
like
in
the
other
ones
as
well.
So
okay
document
database
is
similar
to
key
value,
but
the
value
itself
is
structured
and
they're
all
familiar
with
json
and
technically
mongodb
itself
uses
binary
basis.
I
guess
it
serializes
that,
and
so
it's
very
easy
to
use
in
that
regard.
B
But
if
you've
ever
worked
with
mongodb
and
try
to
do
some
kind
of
querying,
it
could
be,
it
could
be
pretty
pretty
intense.
It
could
be.
You
know
a
lot
of
the
the
curl
braces
and
what
not
to
try
to
you
know
get
everything
right.
You
know
the
first
time
can
be
very
challenging.
B
So
again
too,
you
may
want
to
avoid
the
document
type.
If
there
are
complex,
you
know,
query
and
use
cases
would
be
e-commerce
applications
and
content
management
systems
as
well.
B
B
And
last
but
not
least,
is
the
graft
database
type.
You
can
see
some
relationships
going
there.
You
know
he
says
apollo
or
no
fsa
is
loves,
apollo
and
then
there's
a
connection
between
apollo
and
aries.
That
are
brothers,
and
you
know
so
on.
It's
apologize
for
the
graphics
being
as
clear
as
it
should,
but
you
know
think
of
graph.
You
know
graph
theory
right,
so
you
see
in
there
is,
you
know,
vertex
and
edge.
B
If
you
remember
your
computer
science
on
that,
you
know
in
graph
theory,
you
know
you
refer
to
a
lot
of
these
things
as
vertices
and
edges,
so
you
can
see
that
there,
a
graph
by
the
way
is,
is
built
on
top
of
the
what's
known
as
the
entity
attribute
value
model,
you
can
encode
in
a
space
efficient
manner,
entities
where
the
number
of
attributes
that
can
be
used
to
describe
them
is
potentially
vast,
but
the
number
that
will
actually
apply
to
a
given
entity
is
relatively
modest.
B
It's
a
flexible
way
to
describe
how
data
relates
to
other
data
and
use
cases
would
use
as
fraud,
detection
graph
based
search
and
social
networks,
and
example.
Databases
in
this
family
are
neo4j,
morocco,
db
and
oriented
db.
B
Okay,
next,
we
have
the
two
different
layers
and
the
first
one
is
communication,
and
this
was
formerly
known
as
diana
when
when
the
spec
was
first
developed.
B
So
if
you
see
some
old
blog
posts
from
a
couple
years
ago,
you
know
you'll
see
references
to
this
and
the
mapping
layer,
we're
referred
to
as
artemis.
B
And
you
can
see
a
diagram
where
everything
is
related
together.
You
can
see
that
all
the
d-
I'm
sorry
all
the
nosql
database
families
at
the
bottom
and
how
they
connect
all
together.
B
So
the
communication
letter
layer
is
a
set
of
apis
that
obviously
defines
communications
with
all
the
no
equal
databases.
There
are
model.
There
are
models
representing
all
four
types,
so
you
see
when
you
use
one
of
them,
there's
all
the
classes
will
begin
with
the
the
name
of
the
notes,
equal
type,
and
you
can
think
of
this
synonymously
in
the
relational
database
world,
like
jdbc
apis.
B
The
mapping
layer,
obviously
similar
to,
like
you,
know,
hibernate
and
whatnot,
you
can
map
your
java
objects
to
those
databases,
and
this
specification
incorporates
the
context
and
dependency
injection
and
jakarta
bean
validation
specs.
B
It
is
annotation
driven
and
if
you
worked
with
jpa
in
the
past,
you
can
obviously
compare
you'll,
see
annotations
that
are
similar
to
to
those
jpa
annotations
as
well.
B
So
we
will
see
that
that
will
be
clear
in
the
example
that
I
have
here
so
going
back
to
what
I
said
before
about
each
of
those
nosql
types,
the
if
you
can't
see
it,
the
x-axis
is
complexity
and
y-axis
of
scalability,
so
you
can
see
where
each
of
those
fall.
You
know
the
key
value,
obviously
less
complex
and
more
highly
scalable,
and
so
on.
B
So,
as
I
mentioned
earlier,
it's
amazing
how
many
nosql
databases
are
out
there.
I
don't
know
if
any
of
you
have
heard
of
any
of
these,
but
and
I'm
sure
there's
a
lot
more
than
that
as
well.
These
these
are
ones
that
are
supported
by
the
jakarta
nosql
specification,
so
you'll
obviously
see
the
ones
here.
We've
got
the
hazelcast
couchdb
apache
tinkerpop
is
a
graph
nosql
type,
and
I
believe
there
is
there's
no
specific
classes
for
the
graph,
no
sequel
database
type,
because
because
the
specification
leverages
apache
tinker
pop.
B
Okay,
so
I
am
a
craft
beer
enthusiast
and
those
of
you
who
know
me
well,
I
you
know
I
try
to
visit
craft
breweries
when
I
visit
different
cities,
and
you
know
that
that
kind
of
thing
so
and
so
of
course,
why
not
have
an
application
that
deals
with
here
and
I
have
a
mongodb,
obviously
a
database,
it's
known
as
beertv,
and
here
is
the
beer
collection.
B
So
basically
it's
very
simple.
It's
nothing!
You
know
I
mean
this
could
be
a
lot
more
involved
or
you
know
much
bigger,
but
just
to
try
to
keep
things
simple.
I
just
have
the
abv
of
the
beer,
the
name
then
the
brewer
id,
because
I
I
have
a
separate
collection
for
that
and
the
the
beer
type.
B
B
So
there's
a
lot
of
good
ones.
Here
I
even
included
budweiser
yeah,
you
know,
but
that's
okay
and
then
in
the
brewer
collection,
I'm
just
storing
the
name
of
the
brewer
like
southern
tier
and
the
city
and
state
in
which
they
in
which
they
operate.
Okay
and
there's
21
of
them
there.
So
we're
going
to
go
refer
back
to
this
as
we
run
the
the
application.
B
So
the
first
thing
you
want
to
do
is
we're
going
to
do
the
mapping.
B
You
know
for
the
the
two
collections,
so
we
have
one
corresponding
for
beer
and
obviously
we're
corresponding
for
for
brewer,
and
basically
it's
a
pojo
with
some
additional
builder
stuff
here
so
you'll
see
we
use
the
the
annotation
here
column,
entity
and
id
these
look
very
familiar
to
those
of
you.
Who've
looked,
you
know,
used
jpa,
so
we
we
wrapped
the
class
with
an
entity
annotation
and
then,
of
course,
we,
the
primary
key,
we'll
wrap
that
with
an
id
annotation
and
then
same
thing
with
the
columns.
B
So
you
know
keep
it
simple
here.
You
know
just
just
storing
the
name.
Oh
there's
also
appear
type,
we
add
in
there
and
it's
a
separate
enum
right
here.
So
we
can
refer
to
that
right,
so
you
can
see
them
all
there.
I
think.
B
And
so
that's
embedded
in
there
and
then
so
here
this
is
using
the
column,
but
I'm
referring
to
brewer
id
in
this
case.
Why
don't
I
do
it
in
the
other
ones?
Well,
because
these
match
exactly
id
name
and
type.
B
So
id
the
name
and
oh,
that's
the
brewery,
so
the
id
name
and
the
type
okay
brewer
id
you
notice
is
brewer
underscore
id,
and
if
you
would
like
to
use
the
more
traditional
brewer
uppercase
id
without
the
underscore
you
can
do
that
and
all
you
have
to
do
is
in
your
annotation
refer
to
the
proper
one,
that's
in
the
database
itself,
so
you
obviously
could
use
you
know
brewer
underscore
id
here,
but
I
wanted
to
show
you
know
how
you
can
map
the
two.
B
Even
if
they're
they're
slightly
different,
we
got
a
just
a
basic
default
constructor,
which
you
know
we
never
use
right,
but
it's
there
anyway.
You
know
for
completeness
and
then
they,
the
primary
constructor,
you
know,
passes
all
this
stuff
in
here
and
then
getters
and
setters,
and
we
need
to
focus
on
that
because
we
all
know
what
they
look
like
got
a
two
string.
B
Now,
of
course,
you
know,
I
could
do
all
this
in
in
java
16
and
use
a
record,
but
so
we
haven't
gotten
there
yet
then,
thanks
to
atomio,
you
know
I'd
like
to
be
able
to
use
the
builder
in
the
application
itself,
and
this
is
all
the
you
know
the
machinery
in
order
to
do
that.
B
So
basically,
you
have
a
static
class
and
then
all
your
corresponding
types
and
then
you
know
as
a
beer
builder,
you
know
for
the
id,
the
name,
the
type
and
so
on,
right
and
then
a
build
method
that
returns
the
actual
structure
that
it
builds
in
there.
Okay,
so
we'll
see
how
that's
how
that's
used.
I
think
this
is
really
cool,
and
this
was
no.
B
This
may
have
been
obvious
to,
or
maybe
a
lot
of
you
knew
this
in
the
past,
but
I
just
was
something
that
that
I
learned
the
first
time
in
a
number
of
months
ago
and
the
same
thing
is
here:
we
don't
have
to
go
through
this
in
any
gory
detail,
but
again
this
all
corresponds
to
the
brewer
collection,
and
then
you
know
the
same.
B
You
know
the
same
getter
and
setter
methods
or
actually
getter
methods-
I'm
sorry,
the
same
builder
stuff,
so
all
right,
easy
enough
and
so
we'll
go
through
some
of
the
other
things
here.
First
before
we
look
at
the
main
application,
there's
a
service
that
we
use
here
right
and
it
uses
inject
and
you
notice
I'm
still
using
the
java
x,
I
may
have
been
using
an
older
version,
which
is
probably
why
I
had
some
difficulty.
I'm
gonna
I
haven't
had
the
time
to
go
back
and
experiment.
B
And
then
the
db1.database
is
brsdb,
obviously
right
and
then
we're
going
to
you
know
the
default
port
for
db
is
27017
and
then
the
provider
is,
you
know
the
or
eclipse
j
note
sequel.
You
know
it
has
diana
right.
So
that's
part
of
the
communication
and
the
mongodb
configuration
there
are
corresponding.
B
You
know,
methods
or
classes.
You
know
for
the
other
database
types
itself.
B
We
have
a
manager
producer
again.
I
don't
think
this
is
more
relevant
for
you
know
more
than
one
database,
so
you
can
see
here
our
property
name
db,
one
right
provider,
beer
db,
and
then
here
you
know
this
is
a
database
type.
Obviously
document
and
you
have
the
you
know
the
corresponding
key
value,
graph
and
column
family
of
those,
and
you
have
your
application
where
it
produces.
It
produces
a
database
right,
get
brewer,
doc
and
there's
a
beer
doc.
B
Okay
and
again
I
have
the
the
corresponding
jakarta
namespace
stuff.
I'd
like
to
import,
you
know,
is
to
use
instead
of
the
you
know,
soon
to
be
old
java,
x,
namespace.
B
Okay-
let's
see
so
now
we
have.
We
have
two
different
ways
of
doing
things
and
when
I
get
to
the
main
application
there
are,
you
can
actually
use
a
beer
repository,
an
instance
of
that
or
a
beer
service
and
then
same
thing
with
with
the
brewer.
B
B
Okay,
that
was
a
little
bit
weird
in
the
screen
there,
so
we
have
the
different,
find,
buy
or
find
methods
and
a
delete
method
here.
So
I
have
the
find
all
find
by
name
find
by
grouper
id
and
you
can
do
find
by
whatever
else
corresponds
to
the
data
in
your
database
all
right.
So
these
these
get
they
get
compiled
behind
the
scenes.
But
you
know
the
the.
B
What
I
should
say
is
the
instead
of
the
interface,
the
the
classes
themselves,
get
get
created
behind
the
scenes
and
the
same
thing
with
the
brewer
repository
all
right.
In
this
case
you
know
I'm
just
going
to
find
all
and
phone
by
name
and
of
course
you
can
just
your
listing
whatever
you
know,
whatever
you
need
here
in
your
interface.
B
And
similarly
with
the
okay,
so
similarly
with
the
service,
it's
now
you
have
to
define
your
query.
So,
as
you
saw
in
the
repository
right,
all
you
have
to
do
is
declare
them
and
they
get
created
when
it
generates
the
concrete
classes.
The
implementation,
that's
what
I
was
looking
for
earlier,
and
so
in
this
case.
B
So
we
have
an
insert
method
here:
oh
and
we're
going
to
have
it
integrated
in
this
is
a
document
template
type
and
so
we're
going
to
do
the
insert
method
of
template
and
then
pass
in
the
beer
itself
and
then
we're
going
to
do
a
find.
My
name,
you
know,
define
that
and
then
there's
document
query
class
and
then
he's
used.
This
is
the
streams,
so
there's
a
select
and
then
dot
from
dot
where
so.
This
all
looks
very
familiar
to
everybody.
Anybody
who's
used
ansi
sql
over
the
year.
B
So
this
is
really
easy.
You
know
to
use
and
then
there's
a
build
method
as
a
as
the
terminator
of
the
stream,
and
then
you
call
the
select
method
from
template
and
that's
your
query
right
there,
and
this
is
the
find
by
brewer
id
okay.
You're
gonna
select
from
beer
where
brewer
id
equals
the
brewery
being
passed
in
and
then
a
method
and
same
thing
with
the
brewer,
the
brewer
service
yeah.
B
So
we
have
the
one
defined
here:
okay
and
you'll
notice
here,
a
config
property
annotation
is
d1.
That's
referring
to
that.
So,
if
you
only
use
one
database,
you
probably
don't
need
this
at
all.
You
know
so.
B
Okay,
let's
see,
I
think,
we're
about
ready
to
show
the
main
class
here.
Yes,
okay,
there
any
questions
so
far
or
have
I
put
anybody
to
sleep
yet.
B
Okay,
oh
yeah,
this
is
I'm
not
using
the
logger
in
this
case
that
was
from
the
you
know,
the
original
application
I
started.
One
of
the
things
you
can
do
is
is
a
in
the
in
the
java
sc.
Without
using
jakarta
containers
you
can
use
an
se
container
here
and
create
so
you
create
a
new
instance
of
that
and
then
initialize
and
then
we're
going
to
take
that
container
and
use
that
to
select
our
service
all
right.
B
So
that'll
get
the
service
that
we
defined
earlier,
and
here
are
our
ways
of
instantiating
our
beer
repositories.
So
we
use
our
get
beer
repository
from
the
service
right
and
then
the
brewer
repository
and
then
in
the
service
you're,
using
the
container
variable
to
select
to
select
that.
So
that's
how
everything's
wired
up
first,
I'm
going
to
do
is
get
all
the
elements
in
the
database
itself
and
the
reason
I
do
that
is
because
I'd
like
to
dynamically
add
to
the
end
of
the
list,
all
right.
B
B
All
right,
so
we're
going
to
use
we're
going
to
create
a
brewer
and
we're
going
to
call
it
reports
brewing.
This
is
up
in
newport,
rhode,
island,
where
I've
visited
in
the
past,
I'm
going
to
insert
an
id
of
the
number
of
brewers
plus
one
okay
and
then
we're
going
to
use
the
build
method.
This
corresponds
to
the
build
method
that
I
showed
you
in
the
pojo
and
then
we're
gonna
in
the
repository.
You
know
we'll
use
the
save
method.
B
Okay
again,
this
was
all
generated.
The
implementation
was
generated
in
the
background,
there's
a
save
method
to
do
that
and
we'll
save
the
variable
storm
using
the
service.
B
I
was
just
made
aware
last
couple
of
months
in
new
jersey
in
my
own
backyard
here
about
in
stockton,
new
jersey,
I'm
out
in
clinton,
and
so
this
is
hundred
and
county
western
part
of
new
jersey
along
the
delaware
river.
I
heard
brewing.
I
have
not
been
there
yet
okay,
but
I've
had
had
you
know.
B
I've
had
a
beer
or
two
from
from
their
brewery
at
our
friend's
house,
so
I
look
forward
to
going
there
so
anyways
they're
in
stockton,
new
jersey
and
the
same
thing,
except
we're
going
to
use
the
insert
method
that
was
defined
in
this.
The
in
this
case
the
poor
service
and
was
in
here
right
there.
So
all
right
so
straight
forward,
there's
another
one
another
way
to
skin
a
cat
here
too,
as
they
as
they
say,
but
using
the
template
itself.
B
That's
why
we
have
the
list
and
then
we'll
put
that
on
the
screen
as
well
now
we'll
use
that
brewer
id
since
we
store
in
the
database.
If
you
recall
that
the
beer
itself
had
a
brewer
id
and
that's
that's
where
we'll
make
that
connection
all
right.
B
So
now
we
do
the
same
thing:
we're
going
to
use
the
repository
method
to
create
a
new
beer,
and
since
we
we're
going
to
enter
in
two
beards
from
oddbird
brewing,
the
first
one
is
an
esb
as
they
call
it
extra
stock
bitter
instead
of
extra
special
bitter,
and
this
is
beer
type
ale.
B
So
you
know
recreating
the
the
beer
itself,
the
brewer
id
that
we
just
got
from
calling
calling
the
method
and
the
abv
is
4.3,
and
then
we
use
a
build
and
then
we'll
we'll
save
method
from
the
beer
repository
and
similarly
with
their
extraordinary
machine,
which
is
an
rpa.
B
So
now
that
we
have
those
in
there-
and
we
will
run
this-
let's
find
a
regular
beer
by
name
something
we
haven't
inserted.
Just
you
know,
as
we
here
as
we'll
as
we
will
do
here,
so
let's
find
pum
king
and
this
this
is
one
of
my
favorite
beers
by
by
southern
southern
tier.
It's
actually
it
tastes
as
if
you're
you're
biting
into
a
piece
of
pumpkin
pie.
So
that's
the
best
way
to
describe
that.
I
highly
recommend
it
southern
it's
out
now:
seasonal,
of
course,
anyways.
B
B
B
So
I
think
we're
ready
to
run
this
thing.
Is
you
guys
ready
over
there?
I
really
miss
in
person.
You
know
presentations,
so
I
like
interacting
with
everybody
all
right.
So
the
first
thing
we're
going
to
do
we'll
have
to
compile
this
since
I,
since
I
updated
this
earlier.
B
B
B
Yes,
you
notice
that
it
compiled
with
jdk
11,
but
we
couldn't
run
it
with
jk
11..
So
this
needs
to
have
some
updating
done
here,
all
right,
so
when
it
originally
ran.
I
said
there
were
14
beers
in
the
database
and
21
brewers,
and
that
was
true
before
we
get
started
so
now
we're
going
to
update
this-
or
you
know
refresh
this-
there
are
16
now
and
you'll
see
the
two.
These
are
the
this
is
beer
the
esb
and
the
extraordinary
machine.
B
That's
why
it's
more
than
funny
so
so
you'll
see
id23
is
stocked
in
hot
bird
brewing.
All
right
and
22
was
newport
storm
and
of
course,
you
know
when
we
got
the
before.
That
was
a
new
one
that
we
discovered
in
new
orleans
this
past
summer
meal
brewing
so.
B
Okay,
so
it
seemed
everything
seemed
to
work
nicely
so
that
you
found
we
found
the
brewer
by
name.
So
this
is
the
output
here,
all
right.
So
again,
it's
jason
right,
oops.
B
B
Oh
and
then
we
do
the
find
the
varieties
of
beer
by
uber
id
and,
of
course,
since
we
specify
cod
bird
brewing
found
these
two
here.
So
obviously,
if
you
ran
up
with
different
ones
here,
one
of
these
days,
I'm
going
to
have
time
to
actually
make
this
a
you
know
a
rest.
You
know
application,
so
it's
that
four
letter
work
all
time
right.
Any
questions
on
this.
It's
you
know
this
is
a
good
way
to
get
started.
You
can
obviously
take
this
to.
A
There
is
one
question
in
the
questions
tab:
is
it
possible
to
do
bulk
insert
update.
B
Oh,
that's
an
excellent
question.
I
have
not
tried
update.
Can
I
if
I
can
get
if
you
can
send
me
an
email
on
that,
I
can
actually
try
to
play
with
that
and
try
to
do
an
update.
I
had
not
thought
of
that.
Let
me
come
to
write
that
down.
B
Yeah
I'd
have
to
research
that
a
little
bit
I've
been
so
focused
on
just
this.
You
know
I
never
thought
about
doing
this
so,
but
I'm
sure
there
are.
There
are
methods
to
do
that.
A
A
B
And
I
have
mentioned
that
at
the
end,
but
I
have
yes.
This
is
where
you
can
get
this
now,
though,
so,
let's
wrap
up
with
a
couple
of
couple
of
small
slides
here,
the
current
status.
It's
still
in
development,
it's
not
part
of
the
platform
profile
or
the
the
web
profile
just
yet,
and
this
is
version
1.0.0,
beta
3.
B
B
So
I'd
have
to
try
to
find
out
where
that,
where
that
stands
so
but
yeah
though,
as
part
of
jakarta
ee10,
I
you
know,
I
don't
think
this
will
be
underneath
the
you
know
in
any
one
of
those
profiles.
So
hopefully
you
know
sometime
next
year.
This
can
be
under
one
of
those
profiles
themselves.
That
would
be.
That
would
be
cool.
Actually,
I
think
this
is
really
a
useful
specification.
B
And
well
there's
some
resources.
I
have
these
slides
available.
You
can
download.
Now
I
found
some
other
thing
here
is
one
of
the.
I
think
it
was
one
of
the
other
info
queue.
Editors
wrote
something
back
in
2019
on
card
on
nosql
the
specification
itself
you
can
see
in
that
first
bullet
and
there's
a
this
is
a
youtube
video,
a
good
feature
for
tavia
and
and
possibly
somebody
else,
and
then
baildong
has
an
older
eclipse,
j-no
sequel
example.
B
If
you're
familiar
with,
I
think
his
first
name
is
eugene,
if
I'm
not
mistaken,
but
he's
got
some
great
great
blog
posts
on
how
to
do
various
things.
In
java.
B
And
if
you
want
to
get
involved,
the
best
way
is
to
contribute.
You
can
fork
the
nosql
repository
as
you
see
here
and
you
can
get
going
and
obviously
do
the
traditional.
You
know
branching
and
you
know
prs
and
whatnot.
So
that's
the
best
way
to
go
with
that
and
you
know
I
want
to
acknowledge
otano,
since
he
spent
some
time
with
me
before
I
started
doing
these
presentations
and
you
know
answering
a
lot
of
my
questions
and
oh,
how
do
you
this?
B
B
This
is
my
contact
info.
You
know
my
twitter
handle
is
a
lot
of
you
know
I
t
stuff,
but
I
do
have
my
my
political
rants
once
in
a
while,
I
limited
I
limited
to
twitter
as
opposed
to
other
social
media,
but
I've
been
a
little
bit
better
with
that,
and
you
know
so,
but
then
also
you
can
put
up
with
some
cat
stuff,
since
I
have
four
cats
at
home.
B
That's
my
my
twitter
feed,
so
my
main
website
and
I
have
a
portfolio
page
that
has
contains
a
number
of
other
presentations
that
I
do
and
then
have
a
github
repository
under
mp,
ready,
zero
one,
okay
and
and
speaking
of
beer.
Thank
you
very
much.
I
appreciate
taking
your
time
out
of
taking
the
time
out
of
your
work
day,
or
maybe,
if
you're
from
europe.
Obviously
it's
the
end
of
your
day,
so
you
can
actually
enjoy
one
of
these
before
I
can
so
so
with
that,
that's
it.
A
A
And
finally,
if
you
have
any
feedback
for
the
jakarta
tech
talk
program,
you
can
let
us
know
through
that
as
well,
and
let's
see
if
we
have
any
other
questions,
it
doesn't
look
like
that
nope
just
a
lot
of
thank
yous,
so
it
looks
like
that.
Is
it
so
I
just
want
to
say
thank
you
again
mike
for
that
presentation
and
thank
you
for
everyone
who
attended.
I
hope
you
all
enjoy
the
rest
of
your
day.