►
Description
The topic of this Async Import meeting was an update on the Async architecture.
A
A
A
A
It
looks
really
good
that
the
basically
was
the
performance
improvements,
if
he's
touring
the
operations
of
a
synchronous,
API
or
KPI
in
a
radius
and
not
inversion
to
database,
to
get
like
20%
all
the
improvements.
If
you
are
talking
about
the
bulk
operations,
when
you
a
chance
for
like
a
lot
of
objects
with
one
request
or
if
you
took
an
all
like
single
request,
its
pipe
like
six,
almost
six
percent
of
performance
improvement
for
one
operation,
so
for
singular
request,
which
I
really
think
it's
really
good
put
numbers
here,
so
we
can
go
for
it.
A
I
just
made
it
here,
small
review,
but
I
guess
more
and
you
know
what
to
do
to
try
to
make
it
like
more
isolated,
like
a
service
that
we
can
just
edit,
like
several
extension
with
minimum
dependencies
as
possible,
but
yeah.
If
you
have
any
questions,
just
drop
in
a
chat
or
drop
it
on
them
to
me,
but
I
hope
you
can
do
it
the
next
day,
sweets.
No.
A
On
post
low,
we
have
finally
all
chests
available
for
that
for
all
repository
they
all
up
and
running
all
works.
It's
really
good
useful.
We
can
now
run
the
test
for
the
pull
request,
pets
and
other
good
news
and
related
to
art
architecture.
Just
wanna
show
you
some
changes,
a
challenge
implement
past
weeks.
A
We
have
two
currently
now
two
modules:
it's
simple
service
animal
service,
API.
What
we
dealed
well
discussing
with
all
except
the
final
structure
would
looks
like
this,
so
switch
as
we
go
into
service
insulation
direction.
We
will
try
to
make
the
whole
model
also
in
this
direction.
So
we
have
the
input
service
and
if
a
service
API
like
a
core
modules,
and
then
we
have
on
top
the
source
modules,
so
you
can
solve
by
default.
Visual
supports
sv
like
a
source
like
a
default
source.
A
On
top,
we
can
easily
then
add
and
another
source
types
like
XML
JSON
and
whatever
you
want
so
idea
that
the
source
tab
will
be
implemented
like
a
separate
module
and
its
end,
as
we
have.
The
all
endpoint
form
for
each
source,
who
will
develop,
will
also
have
an
API
for
what
you've
had.
This
will
provide
the
service
context,
potent
and
endpoints
itself,
and
also
the
several
model
will
will
be
for
import,
which
is
so
true
in
here
to
service
catalog
products
or
economic
categories.
A
So
when
we
have
each
import
object
in
a
separate
module
and
on
top,
if
you
want
to
implement
to
create
a
new
import
object,
you
just
make
it
in
you
and
your
model
on
it
foliage
and
by
using
the
configuration
and
XML
files
make.
It
works
with
a
import
service
module
like
core
module
and
what
a
time
to
do
last.
These
are
basically
challenges
had
to
refactor
the
modules
that
we
have.
A
So
we
are
trying
to
split
to
move
out
there
over
the
SS
e
related
interfaces
models,
implementations
to
put
this
V
on
all
the
related
for
you.
The
center
will
do
a
simple
start,
so
the
catalog
products
starting
points
yeah,
and
also
what
I
made
last
days
I
provided.
So,
but
basically
we
had
a
problem
that,
because
we
are
using
the
format
here
which
may
be
different
from
time
to
time.
A
So
you
can
imagine
that
ESB
has
a
touch
attributes,
for
example,
and
XML
has
some
root
node
only
attribute,
or
maybe
some
another
one,
but
currently
that's
not
a
use
case,
but
in
any
case
any
format
will
have
the
own
base.
Settings
always
have
to
be
processed.
This
means
that's
to
prevent
this.
Well,
maybe
I
deserve
to
have
their
own
service
contract
and
basically
owned
DTO.
A
This
means,
if
you
want
to
add
a
new
file
type
like
XML.
We
have,
we
have
to
complicate
a
lot
of
code.
Maybe
another
table
can
write
it
again,
but
it's
really
a
lot
of
files
just
to
make
like
a
new
type
available
for
the
import
and
what
I'm
trying
to
do
I
try
to
provide
the
unique
interface
we
change
the
same
setters
and
getters,
but
format
will
be
provided
here
like
an
array.
A
So
in
this
case
that's
not
an
interface,
so
we
still
receiving
that
this
interface
on
details,
but
then
we
conversion
it
to
the
source
format
it
has.
An
error
inside
which
has
basically
may
have
a
different
set
of
the
keys
inside
will
be
transferred
to
process
source,
for
example,
to
start
source.
This
means
we
don't
need
to
dublicate
a
lot
of
code
and
we
only
need
to
provide.
A
We
still
need
need
to
provide
the
own
end
point
the
again
end
points
and
the
own
service
contract
that
will
execute
it,
because
we
still
have
to
have
the
type
related
interfaces,
but
then
we
can
wear
them
to
the
like
unique
one
and
it
will
be
processed
by
all
processors.
I
will
try
to
complete
it
next
taste.
This
one
and
also
the
splitted
I,
will
make
a
pull
request
and
then
I
will
basically
ask
you
Alex
to
have
a
look
on
it.
If
you'll
find
the
time.
A
The
most
never
funds
into
developers,
okay,
so
yeah
Alex
from
corner
I
know
you
will
work
on
a
test
for
the
source.
Applause
yeah,
that's
pop
in
two
weeks.
Maybe
you
you
can
show
us
something
in
any
case
after
you
will
make
a
full
request
in
a
pull
request.
You
can
see
the
chest
if
there
were
successful
sore
all
mojo.
That
is
good.
If
not,
you
have
to
align
it,
but
any
case.
If
you
will
have
a
questions
about
general,
like
pool
requests
and
testing
workflows.