►
Description
- New arch-diagram for Async Import Service by Alex Lyzun
- Discussing some PR comments made by Volodymyr Kublitskiy
B
A
The
generally,
the
small
diagram
which
is
showing
the
status
on
which
we
plan
to
do
in
case
of
the
importance
and
API
is
which
we
want
to
develop
in
our
module.
So
if
starts
from
the
beginning,
we
have
this.
This
final
important
point,
which
has
several
use
cases.
One
of
them
is
already
as
a
full
request,
not
on
main
repository
but
I
hope
in
my
pull.
Request
will
be
done
in
this
will
also
appear
on
our
now
repository,
and
then
we
have
the
input
start
operations.
A
We
have
get
import
information,
we
have
profiling
endpoints
here
and
yeah.
That's
all
journey
I
mean
if
you
I
will
not
go
in
details,
we're
ready
to
discuss
it.
If
you
have
any
questions
concerns
you
can
just
go,
they
have
a
look
feel
free
to
propose
some
changes
if
you
want
to,
but
generally
yeah,
that's
it
of
the
new
developers
we'll
find
this
useful
for
them
cool
good.
A
This
extension,
because
before
idea,
what
that
it
looks
like
this,
so
we
have
the
file
ID
on
fosston
than
the
source,
but
you
journey
right.
We
don't
need
it
structure
such
complex
structure
here,
because
we
also
expect
that
it
will
be
executed
as
synchronously
and
the
file
ID
when
we
create
in
you
and
you
pile
like
push
a
new
file
in
the
system,
not
really
necessary
on
entry
once
on
the
create
end,
point
only
case
which
we
had
in
mind
before.
A
That
was
the
basics
before
upload
in
a
part,
but
when
you
upload
the
multiple
parts
that
may
be
like,
you
send
the
first
request
to
get
a
file
ID
and
then
next
parts
are
coming
to
the
same
file
ID,
but
I.
Think
it's
still
not
necessary
here,
because
we
again
can
send
those
parts
are
synchronously.
This
mean
we
just
push.
C
This
confused
because,
like
good
source
return
source
serves
that
interface,
which
which
also
have
source
ID
and
dislike
confused
in
those
interfaces
or
CD,
will
be
the
same
or
not,
probably,
if
we,
it
might
be
a
good
idea
to
proceed
with
initially
here,
but
maybe
just
fix
enough
name
in
collision
will
help
just
to
clearly
communicate.
What
was
the
purpose
of
those
interfaces
in
data?
Indeed,
namespace
we
have
a
source.
A
Go
to
boil,
but
also
maybe
some
somebody
else
has
an
idea
internal
to.
We
need
the
the
source
side,
your
file
ID
in
this
and
in
this
endpoint
and
at
all,
because
we
didn't
see
any
use
case
for
it
when
we
create
any
when
you
post
a
new
file
in
a
system
for
import,
so
I
would
generally
be
rather
to
eliminate
it
and
then
make
a
structure
bit
simpler.
Also
for
for
developers.
A
A
A
Then
you
need
this
to
level
structure
or
we
can
stay
with
this
end
point
on
which
you
can
see
on
my
screen,
so
we
have
only
one
level.
We
have
a
source
and
then
parameters
all
the
source
inputs
and
we
don't
need
complex,
like
we
have
it
here
when
you
have
done
it,
that's
our
source
and
that's
our
source
data.
So
we
don't
I,
don't
see
a
case
when
we
need
so
two
levels.
Yeah.
A
A
Yeah,
so
we
hate
her
journey
here,
our
import
model,
which
is
generally
doing
the
import
itself.
It's
quite
basic
when
we
have
the
our
processors
pool
which
defining
how
to
protest.
The
source
is
a
generation
SV
related
externally
in
base64,
and
then
it's
doing
applaud
itself,
but
first
of
all
we
find
out
which
processor
we
have
to
use
and
we
do
in
applaud
and
then
we
set
in
their
response,
which
is
totally
other
topic
for
now.
The
journey,
all
it's
nothing
else
here
and
from
interfaces
we
have,
you
know
the
source
interface.
A
A
A
C
A
B
B
B
A
A
A
A
Yeah
I
guess
for
now:
that's
all
so
I'll
make
this
changes
and
oh
yeah
I
had
only
I
had
generally
one
question:
we
have
this
architectural
pull
request
with
which
we
merged,
in
which
we
are
continuously
changing.
You
have
some
good
work
around
there
like.
Should
it
make
every
time
the
pull
request
to
change
it?
Oh
good.