Comparative
analysis
of
the
efficiency
of
Data
P
e
r
s
i
s
t
e
n
c
e
F
r
a
m
e
w
o
r
k
s
.
C
a
s
e
s
t
u
d
y
H
i
b
e
r
n
a
t
e
5.4
and
MyBatis
3.4
A
b
s
t
r
a
c
t
.
-
T
h
e
o
b
j
e
c
t
i
v
e
o
f
t
h
e
s
t
u
d
y
w
a
s
t
o
d
e
t
e
r
m
i
n
e
w
h
e
t
h
e
r
H
i
b
e
r
n
a
t
e
5
.
4
o
r
M
y
B
a
t
i
s
3
.
4
i
s
t
h
e
m
o
s
t
efficient
in
terms
of
time,
RAM,
and
CPU
usage.
Two
REST
microservices
were
implemented
to
perform
CRUD
o
p
e
r
a
t
i
o
n
s
;
w
h
i
c
h
w
e
r
e
a
c
c
e
s
s
e
d
b
y
R
E
S
T
s
e
r
v
i
c
e
s
d
e
v
e
l
o
p
e
d
w
i
t
h
H
i
b
e
r
n
a
t
e
a
n
d
M
y
B
a
t
i
s
i
n
v
o
k
e
d
f
r
o
m
a
client.
Our
results
were
that
Hibernate
was
the
most
efficient
with
respect
to
processing
time
at
509.1%
and
4
7
.
7
%
f
o
r
s
e
l
e
c
t
a
n
d
d
e
l
e
t
e
q
u
e
r
i
e
s
,
w
h
i
l
e
M
y
b
a
t
i
s
w
a
s
a
t
1
2
.
7
%
a
n
d
1
4
.
2
%
f
o
r
u
p
d
a
t
e
a
n
d
i
n
s
e
r
t
q
u
e
r
i
e
s
,
correspondingly.
Regarding
the
use
of
RAM
and
CPU,
MyBatis
was
determined
to
be
the
most
efficient
at
55.2%
and
20%
respectively.
Keywords:
Data
persistence
framework,
comparative
analysis,
Hibernate,
MyBatis.
I
S
S
N
-
E
:
2
5
4
2
-
3
4
0
1
,
I
S
S
N
-
P
:
1
3
1
6
-
4
8
2
1
U
n
i
v
e
r
s
i
d
a
d
,
C
i
e
n
c
i
a
y
T
e
c
n
o
l
o
g
Ã
a
,
V
o
l
.
2
6
,
N
ú
m
.
1
1
7
,
(
p
p
.
2
4
-
3
2
)
Medoza-Palomino
et al.
Comparative analysis of the efficiency of Data Persistence Frameworks. Case study Hibernate 5.4 and MyBatis 3.4
Yolvis
Luis
Mendoza-Palomino
https://orcid.org/0000-0002-6948-5558
y
o
l
v
i
s
.
m
e
n
d
o
z
a
.
2
7
@
u
n
s
c
h
.
e
d
u
.
p
e
Qualifacts
Lima,
Perú
Resumen.
-
El
objetivo
del
estudio
fue
determinar
si
Hibernate
5.4
o
MyBatis
3.4
es
el
más
eficiente
en
referencia
al
uso
del
tiempo,
la
RAM
y
la
CPU.
Se
implementó
dos
microservicios
REST
para
realizar
operaciones
CRUD;
los
cuales
fueron
accedidos
por
servicios
REST
desarrollados
con
Hibernate
y
MyBatis
invocados
desde
un
cliente.
Nuestros
resultados
fueron
que
Hibernate
fue
el
más
eficiente
respecto
al
tiempo
de
procesamiento
en
un
509.1%
y
47.7%
para
consultas
de
selección
y
eliminación,
mientras
que
Mybatis
en
un
12.7%
y
14.2%
para
consultas
de
actualización
e
inserción,
correspondientemente.
Con
respecto
al
uso
de
la
RAM
y
la
CPU
se
determinó
que
MyBatis
fue
el
más
eficiente
en
un
55.2%
y
20%
respectivamente.
Palabras
clave:
Framework
de
persistencia
de
datos,
análisis
comparativo,
Hibernate,
MyBatis.
Análisis
comparativo
de
la
eficiencia
de
Frameworks
de
persistencia
de
datos,
caso
de
estudio
Hibernate
5.4
y
MyBatis
3.4
24
R
e
c
i
b
i
d
o
(
2
9
/
0
7
/
2
0
2
2
)
,
A
c
e
p
t
a
d
o
(
0
1
/
1
0
/
2
0
2
2
)
Manuel
Avelino
Lagos-Barzola
https://orcid.org/0000-0001-8078-755X
m
a
n
u
e
l
.
l
a
g
o
s
@
u
n
s
c
h
.
e
d
u
.
p
e
Universidad
Nacional
de
San
Cristóbal
de
Huamanga
Ayacucho,
Perú
E
f
r
a
Ã
n
E
l
Ã
a
s
P
o
r
r
a
s
F
l
o
r
e
s
h
t
t
p
s
:
/
/
o
r
c
i
d
.
o
r
g
/
0
0
0
0
-
0
0
0
2
-
5
5
6
0
-
0
3
0
8
efrain.porras@unsch.edu.pe
U
n
i
v
e
r
s
i
d
a
d
N
a
c
i
o
n
a
l
d
e
S
a
n
C
r
i
s
t
ó
b
a
l
d
e
H
u
a
m
a
n
g
a
A
y
a
c
u
c
h
o
,
P
e
r
ú
https://doi.org/10.47460/uct.v26i117.657
I. INTRODUCTION
G
i
v
e
n
t
h
e
w
i
d
e
v
a
r
i
e
t
y
o
f
d
a
t
a
p
e
r
s
i
s
t
e
n
c
e
f
r
a
m
e
w
o
r
k
s
,
u
s
u
a
l
l
y
s
o
f
t
w
a
r
e
d
e
v
e
l
o
p
e
r
s
f
a
c
e
d
t
h
e
d
i
l
e
m
m
a
o
f
w
h
i
c
h
f
r
a
m
e
w
o
r
k
t
o
u
s
e
i
n
o
r
d
e
r
t
o
a
c
h
i
e
v
e
t
h
e
i
r
o
b
j
e
c
t
i
v
e
s
i
n
t
e
r
m
s
o
f
s
o
f
t
w
a
r
e
i
m
p
l
e
m
e
n
t
a
t
i
o
n
,
t
h
e
s
h
o
r
t
e
s
t
t
i
m
e
,
a
n
d
t
h
e
h
i
g
h
e
s
t
q
u
a
l
i
t
y
.
T
h
e
s
t
u
d
y
i
n
[
1
]
h
i
g
h
l
i
g
h
t
s
a
n
d
d
e
s
c
r
i
b
e
s
t
h
a
t
t
h
e
o
b
j
e
c
t
-
r
e
l
a
t
i
o
n
a
l
m
a
p
p
i
n
g
(ORM)
solution
is
available
in
many
popular
platforms,
that
offer
useful
tools
allowing
developers
to
be
concerned
about
other
pending
issues.
The
work
in
[2]
indicates
that
among
of
the
most
relevant
aspects
when
choosing
a
framework
are
speed
and
efficiency,
which
may
have
many
issues
due
to
the
diversity
of
metrics
to
measure
the
performance
of
a
f
r
a
m
e
w
o
r
k
.
H
o
w
e
v
e
r
,
t
h
e
r
e
a
r
e
o
t
h
e
r
a
s
p
e
c
t
s
t
h
a
t
c
o
u
l
d
h
e
l
p
t
o
d
e
c
i
d
e
,
s
u
c
h
a
s
t
h
e
r
e
s
p
o
n
s
e
s
p
e
e
d
,
t
h
e
i
n
t
e
g
r
a
t
i
o
n
w
i
t
h
t
h
e
d
a
t
a
b
a
s
e
,
t
h
e
u
s
e
o
f
t
h
e
C
P
U
,
a
n
d
t
h
e
u
s
e
o
f
R
A
M
.
The
study
[3],
concerned
about
data
processing
time,
reported
that
the
Hibernate
framework
slightly
i
n
c
r
e
a
s
e
s
t
h
e
p
r
o
c
e
s
s
i
n
g
t
i
m
e
s
w
h
e
n
c
o
m
p
a
r
e
d
t
o
t
h
e
M
y
B
a
t
i
s
f
r
a
m
e
w
o
r
k
,
i
n
a
n
e
x
p
e
r
i
m
e
n
t
a
t
i
o
n
q
u
e
r
y
automatically
generated
and
variation
of
caching
algorithms.
Similarly,
the
work
in
[4]
compared
Hibernate
against
MyBatis,
concluding
that
Hibernate
outperforms
MyBatis
in
terms
of
available
documentation,
quality,
robustness,
and
easy
learning
curve,
which
makes
it
ideal
for
developing
software
projects.
B
e
c
a
u
s
e
t
h
e
H
i
b
e
r
n
a
t
e
a
n
d
M
y
B
a
t
i
s
f
r
a
m
e
w
o
r
k
s
a
r
e
w
i
d
e
l
y
u
s
e
d
b
y
s
o
f
t
w
a
r
e
d
e
v
e
l
o
p
e
r
s
i
n
J
a
v
a
l
a
n
g
u
a
g
e
programming;
it
is
desirable
to
carry
out
an
evaluation
of
the
efficiency
of
both
frameworks
aiming
to
establish
w
h
i
c
h
c
o
u
l
d
b
e
s
e
l
e
c
t
e
d
a
s
a
f
r
a
m
e
w
o
r
k
f
o
r
a
s
o
f
t
w
a
r
e
d
e
v
e
l
o
p
m
e
n
t
p
r
o
j
e
c
t
.
A
l
t
h
o
u
g
h
p
r
e
v
i
o
u
s
s
t
u
d
i
e
s
t
r
i
e
d
to
establish
which
is
the
best
one,
there
is
a
lack
of
a
deep
study
in
terms
of
time,
RAM,
and
CPU
usage.
In
this
w
o
r
k
,
w
e
p
r
o
v
i
d
e
a
s
t
u
d
y
t
o
d
e
t
e
r
m
i
n
e
w
h
e
t
h
e
r
t
h
e
H
i
b
e
r
n
a
t
e
5
.
4
a
n
d
t
h
e
M
y
B
a
t
i
s
3
.
4
f
r
a
m
e
w
o
r
k
s
i
s
t
h
e
b
e
s
t
one
for
software
development.
II. DEVELOPMENT
A.
Object-relational
mapping
The
study
[5]
established
that
object-relational
mapping
(ORM)
is
a
technique
that
allows
converting
system
data
used
in
an
object-oriented
programming
language,
into
data
used
by
a
relational
database.
Thereby,
ORM
creates
a
virtual
object-oriented
database
over
a
relational
one.
Thus,
allowing
the
use
of
object-oriented
features
such
as
inheritance
and
polymorphism.
The
work
[6]
indicated
that
ORM
refers
to
the
automatic
persistence
of
objects
from
a
Java
application
to
tables
in
a
relational
database
and
that
the
mapping
between
the
objects
and
the
database
is
described
in
metadata,
which
is
used
to
reverse
effects.
Despite
this
advantage,
a
considerable
aspect
to
take
into
account
about
the
use
of
this
technique
is
the
compromise
of
the
performance
of
applications.
Another
study
from
a
developer
perspective
[7],
concluded
that
ORM
encompasses
solutions
for
mapping
business
objects
to
relational
data,
delegating
to
the
persistence
layer
the
details
of
its
persistence.
However,
ORM
is
not
fully
automatic,
and
that
automation
is
indescribable.
B.
Data
persistence
Data
persistence
can
be
understood
as
the
maintenance
of
the
state
of
the
object
as
well
as
its
class,
not
reducing
it
to
any
particular
program
[8].
In
a
more
specific
sense,
data
persistence
is
the
ability
of
a
computer
to
retain
information
even
after
shutting
down
or
closing
the
program
that
uses
that
information
[8],[9].
25
Medoza-Palomino
et al.
Comparative analysis of the efficiency of Data Persistence Frameworks. Case study Hibernate 5.4 and MyBatis 3.4
I
S
S
N
-
E
:
2
5
4
2
-
3
4
0
1
,
I
S
S
N
-
P
:
1
3
1
6
-
4
8
2
1
Universidad,
Ciencia
y
TecnologÃa,
Vol.
26,
Núm.
117,
(pp.
24-32)
C
.
F
r
a
m
e
w
o
r
k
The
term
framework
is
used
in
many
contexts
[11],
such
as
applications
in
medicine,
computer
vision,
games,
a
n
d
a
m
o
n
g
o
t
h
e
r
s
,
i
n
w
h
i
c
h
i
t
i
s
u
s
e
d
t
o
d
e
s
c
r
i
b
e
a
s
o
f
t
w
a
r
e
s
t
r
u
c
t
u
r
e
c
o
n
s
i
s
t
i
n
g
o
f
a
d
a
p
t
a
b
l
e
a
n
d
interchangeable
components
for
developing
applications.
In
other
words,
a
framework
can
be
thought
of
as
s
o
m
e
t
h
i
n
g
i
n
c
o
m
p
l
e
t
e
,
b
u
t
c
o
n
f
i
g
u
r
a
b
l
e
g
e
n
e
r
i
c
a
p
p
l
i
c
a
t
i
o
n
b
y
m
e
a
n
s
o
f
a
d
d
i
n
g
c
o
m
p
l
e
m
e
n
t
s
.
D.Hibernate
Hibernate
is
a
framework
that
provides
a
complete
solution
to
the
problem
of
data
persistence
in
Java.
By
i
n
t
e
r
a
c
t
i
n
g
b
e
t
w
e
e
n
t
h
e
a
p
p
l
i
c
a
t
i
o
n
a
n
d
t
h
e
r
e
l
a
t
i
o
n
a
l
d
a
t
a
b
a
s
e
,
H
i
b
e
r
n
a
t
e
a
l
l
o
w
s
d
e
v
e
l
o
p
e
r
s
t
o
f
o
c
u
s
o
n
t
h
e
business
problem.
Hibernate
also
enables
us
to
follow
a
lot
of
design
rules
and
specific
patterns
when
creating
persistence
classes
and
business
logic.
Moreover,
Hibernate
furnishes
high
integration
with
most
new
and
e
x
i
s
t
i
n
g
a
p
p
l
i
c
a
t
i
o
n
s
w
i
t
h
o
u
t
t
h
e
n
e
e
d
t
o
m
a
k
e
m
a
j
o
r
c
h
a
n
g
e
s
t
o
o
t
h
e
r
p
a
r
t
s
o
f
t
h
e
a
p
p
l
i
c
a
t
i
o
n
[
6
]
.
F
i
n
a
l
l
y
,
t
h
e
f
r
a
m
e
w
o
r
k
i
s
a
n
o
p
e
n
-
s
o
u
r
c
e
D
a
t
a
P
e
r
s
i
s
t
e
n
c
e
F
r
a
m
e
w
o
r
k
,
e
a
s
i
l
y
c
o
m
b
i
n
e
d
w
i
t
h
H
Q
L
a
n
d
S
Q
L
s
o
f
t
w
a
r
e
[
1
2
]
.
E
.
M
y
B
a
t
i
s
M
y
b
a
t
i
s
i
s
a
n
o
t
h
e
r
p
e
r
s
i
s
t
e
n
c
e
f
r
a
m
e
w
o
r
k
t
h
a
t
s
u
p
p
o
r
t
s
S
Q
L
,
s
t
o
r
e
d
p
r
o
c
e
d
u
r
e
s
,
a
n
d
,
a
d
v
a
n
c
e
d
m
a
p
p
i
n
g
s
.
MyBatis
does
not
require
JDBC
code,
manual
parameter
setting,
and
retrieval
of
results.
MyBatis
can
be
c
o
n
f
i
g
u
r
e
d
w
i
t
h
X
M
L
,
a
n
d
a
n
n
o
t
a
t
i
o
n
s
,
a
n
d
a
l
l
o
w
s
m
a
p
s
a
n
d
P
O
J
O
s
(
P
l
a
i
n
O
l
d
J
a
v
a
O
b
j
e
c
t
s
)
t
o
b
e
m
a
p
p
e
d
t
o
database
records
[13],[14].
F.
Efficiency
Efficiency
is
defined
as
the
characteristic
that
would
allow
evaluation
of
the
relationship
between
the
level
of
performance
of
software
and
the
number
of
resources
used.
The
aspects
to
be
evaluated
would
be
the
time
behavior
related
to
adequate
response
and
processing
times,
that
is
to
say,
the
performance
when
executing
its
function
under
specific
conditions
and,
on
the
other
hand,
the
resource
behavior,
related
to
the
capacity
of
the
software
to
use
suitable
amounts
and
types
of
resources,
also
operating
under
specific
conditions
[15].
G.
Aspect-Oriented
Programming
The
Aspect
Oriented
Programming
(AOP)
is
a
methodology
that
provides
separation
of
crosscutting
concerns
by
introducing
an
Aspect,
a
new
unit
of
modularization.
Each
aspect
focuses
on
a
particular
crosscutting
function.
Main
classes
are
no
longer
plagued
with
crosscutting
concerns.
The
aspect
weaver
assembles
the
final
system
by
combining
main
classes
and
crosscutting
aspects
through
a
process
called
weaving.
Therefore,
with
the
use
of
the
methodology,
applications
that
are
easy
to
design,
implement
and
maintain
would
be
created.
III. METHODOLOGY
A.
About
the
data
used
In
this
work,
we
use
the
Employee
data
table
of
the
Oracle
HR
scheme.
It
consists
of
10,000
records
for
tests.
Four
basic
queries:
selection,
insertion,
update,
and
elimination,
are
performed.
26
Medoza-Palomino
et al.
Comparative analysis of the efficiency of Data Persistence Frameworks. Case study Hibernate 5.4 and MyBatis 3.4
I
S
S
N
-
E
:
2
5
4
2
-
3
4
0
1
,
I
S
S
N
-
P
:
1
3
1
6
-
4
8
2
1
Universidad,
Ciencia
y
TecnologÃa,
Vol.
26,
Núm.
117,
(pp.
24-32)
T
h
e
r
e
s
t
-
c
l
i
e
n
t
:
I
m
p
l
e
m
e
n
t
s
a
R
E
S
T
c
l
i
e
n
t
a
n
d
t
h
r
o
u
g
h
t
h
r
e
a
d
s
,
w
e
s
e
n
d
a
h
u
n
d
r
e
d
r
e
q
u
e
s
t
s
simultaneously;
fifty
of
which
are
directed
towards
a
REST
service
of
hr-rest-MyBatis
and
the
other
fifty
towards
a
REST
of
hr-rest-hibernate,
in
this
way
we
subject
our
applications
to
a
stressful
situation
since
each
REST
service
will
have
to
process
fifty
requests
simultaneously.
The
hr-rest-mybatis:
microservice
implemented
with
MyBatis.
This
microservice
exposes
four
REST
services.
B
.
E
m
p
l
o
y
e
e
s
t
a
b
l
e
D
D
L
CREATE
TABLE
"HR"."EMPLOYEES"
(
"
E
M
P
L
O
Y
E
E
_
I
D
"
N
U
M
B
E
R
(
6
,
0
)
,
"FIRST_NAME"
VARCHAR2(20
BYTE),
"