►
From YouTube: Mar 30, 2023 - Ortelius Architecture Meeting
Description
The conversation continues around the implementation of the new architecture. This meeting includes a language discussion.
A
B
B
This
connection
here
between
microservice
and
the
database
abstraction
layer
is
basically
a
just
right.
Now,
it's
a
python
function
call
that
we
make.
So
it's
not
really
like
a
another
microservice
that
we
need
to
call
now
one
of
the
things
when
I
was
running
through
the
test
cases
at
ukirch
set
up
that
every
time
we
have
an
object,
let's
say
the
name
of
a
component
or
a
user.
B
Every
time
we
have
that
we
go
through
and
make
a
call
over
to
the
back
end
piece
over
to
nft,
storage
and
right
now
we're
doing
that
in
order
to
get
the
Sid,
which
is
the
how
the
nft
and
ipfs
does
its
addressing.
So
the
the
Sid
is
basically
a
fancy
hash
of
the
content
of
what
you
put
in
as
a
part
of
your
file.
B
B
So
one
of
the
things
I
was
able
to
find
is
said
that
nft
storage
and
ipfs
can
handle
is
what
they
call
a
a
a
Content
archive
format
or
a
Content
addressable
archive
and
basically
like
it
says
here
you
can
think
of
it
as
a
tar
file.
So
what
I'm
thinking
is
we
can
and
one
of
the
benefits
if
we
go
down
to
the
benefits
here.
One
other
thing
we
could
do
is
we
could
actually
calculate
the
Sid.
The
content,
identifier
on.
A
B
So
two
things
that
will
happen
when
we
do
when
we
go
about
this
process
is
the
we
will
only
be
doing
one
call
and
we
can
go
up
to
100,
megabytes
and
I.
Don't
think
we'll
have
any
of
our
data
that
we're
pushing
over.
This
can
be
over
100
megabytes
in
a
single
call
and
then
also
we're
gonna
only
have
one
transaction
instead
of
multiple
transactions,
which
can
help
with
the
speed
going
back
and
forth
between
the
nft
storage
and
in
our
application.
B
So
so
that's
one
thing:
I
found
that
that
will
will
help
us
on
that
front
at
the
at
this
database,
abstraction
layer
that
we
we
have
here
that
the
database
abstraction
there
would
be
actually
working
with
the
when
it
needs
to
go,
call
out
to
nft
storage.
It
would
basically
creating
the
the
car
file
or
basically
the
car
blob
and
passing
it
over
when
we
do
the
upload
or
the
save
to
the
nft
storage.
B
B
The
spec
is
out
there,
so
we
can
actually
write
the
python
Library
ourselves
to
create
the
car
file
based
on
the
goaling
and
the
node.js's
as
examples.
So
basically,
trans
translate
that
those
over
to
the
python
version.
The
other
thing
that
we
can
do
is
at
the
database
abstraction
layer.
When
we
go
to
work
with
nft
storage.
B
We
actually
insert
instead
of
working
directly
from
the
database
subtraction
layer
to
the
NFC
storage
that
we
actually
wrapper
this
in
a
microservice
and
that
microservice
would
be
a
either
a
girl
leg
or
an
node.js
microservice
that
will
create
the
car
file
and
do
the
upload
at
that
level
so
that
that's
so
that
that's
like
option.
One
is
where
your
own
python
Library
option.
B
Two
is
is
rapper
the
nft
storage
with
the
microservice
and
option
three
is
to
change
the
microservices
from
python
over
to
golang,
so
the
all
the
micro
servers,
none
of
them
have
been
written.
Yet.
So
it's
not
like
we're
losing
anything
but
option.
Three
would
be
to
write
the
each
microservices
goaling
with
the
database,
abstraction
layer
in
golang
as
well
and
because
go
link
supports
had
that
power
module.
B
We
can
then
have
the
database
distraction
right
directly
to
the
nft
storage,
so
that
was
one
of
the
things
I
I
found
basically
yesterday
that
we
kind
of
have
to
figure
out
how
we
want
to
proceed.
So
I
can
kind
of
like
generate
the
highlights
of
all
these
micro
services
so
for
folks
to
start
working
on,
so
those
were
kind
of
like
our
our
three
options
and
just
want
to
get
everybody's
feedback
on
that.
C
I
like
go
because
I
really
want
to
learn,
go
kubernetes,
written
and
go
so
if
you
want
to
create
your
own
operator
or
create,
or
if
we
ever
need
to
customize
kubernetes
or
to
this,
then
we
already
have
that
knowledge.
So
you
kind
of
knocking
two
two
birds
with
one
stone
kind
of
thing
right.
If
we're
all
learning
go,
it's
very
versatile
language.
Very
current
language,
I
think
you
can
pretty
much
write
anything
with
it
right,
I,
don't.
B
B
B
B
We
can
change
the
microservices
over
to
golang
and
use
Fiber
as
the
little
the
web
framework,
or
we
can
change
them
over
to
node.js
and
use
Express
Express
express.js
as
the
the
web
framework
there.
So
we
do
have
four
options
because
on
the
back
end,
if
we
go
everything
node.js
on
the
database,
abstraction
layer
and
the
nft
storage
can
be
all
done
through
node.js,
because
those
modules
exist
there
now.
Also
now
you
mentioned
Sasha
like
kubernetes
to
be
written
and
go
I.
C
Yeah
geez
I'm,
really
not
an
expert
in
this
area
at
all,
but
I
was
just
thinking
out
loud
sounds
like
okay,
so
we
run
everything
microservices
kubernetes
is
all
in
go
if
go.
Support
is
supporting
what
you
just
explained
now
about
ipfs,
and
now
you
just
say
that
I'd
say
the
employees
is
already
in
go.
C
C
B
B
C
B
B
B
A
C
B
A
B
C
B
B
A
B
B
C
C
A
C
C
C
B
C
B
B
B
Because
we
will
have
to
re,
do
a
little
bit
of
work
that
ukarsh
did
with
on
the
python
module,
but
we
can
take
his
logic
and
trans
transpose
it
over
dolang,
pretty
quick.
So
it's
not
like.
We
did
a
lot
of
work.
That's
gonna
be
a
throwaway,
but
we
will
need
to
redo
a
little
bit
bit
of
it,
but,
like
I
said
we're
early
on
and
I
think.
C
C
B
C
C
B
C
A
C
A
C
A
A
B
B
B
B
C
B
B
Now,
with
both
of
these,
the
the
Swagger
integration
is,
is
a
little
messy
but
I
think
that's
something
we
could
can
deal
with,
because
I
I
want
to
make
sure
that
for
these
restful
apis,
we
are
generating
the
this
Flagger
file.
For
so
for
folks
to
be
able
to
use,
because
we're
going
to
need
that
from
for
the
front
end
perspective,
yeah.
C
B
I'm
not
sure
like
in
in
the
rust
world,
when
you
create
your
when
you
do
your
cargo
build,
which
is
how
you
build
an
executable
and
rust,
it
actually
brings
down
every
single
piece
of
it
doesn't
bring
down
Source
binaries.
It
actually
is
on
the
source
code
and
compiles
that
at
that
point
in
time
now,
I
don't
know,
I
think
go
works
the
same
way
when
you
go
to
build
it,
it
goes
and
fetches
the
source
every
time
it
still
has
something
like
a
requirement
file,
or
you
know
some
a
package.
B
C
Okay,
would
it
would
it
make
Mike
the
micro
Services
quicker
to
build?
Is
it
because
it's
got
reduced
code?
Does
it
make
a
smaller
I,
don't
know
I'm
sure,
like
a
smaller
container
or
something
in
something,
and
that
doesn't
make
you
look
make
our
containers?
Will
it
make
the
container
better
performing
if.