►
From YouTube: Ortelius Architecture Feb. 17, 2022
Description
Updates on 3D Graphs and a discussion around integration with Cookiecutter or Backstage is included.
A
A
B
Yeah,
so
the
progress
was
we
were
able
to
isolate
the
sample
example.
That
was
there
on
the
website,
and
we
also
created
the
html
file
for
that.
So
right
now
what
we
are
trying
to
identify
the
what
labels
you
know
what
data
we
need
to
like.
Basically,
we
need
an
api
to
feed
that
chart,
so,
like
steve,
has
sent
me
a
couple
of
pointers
around
which
I
can
plot
sample
data
for
various
components
and
components.
A
I
know
he
saw
he
showed
me.
One
kind
of
3d
bar
chart
that
I
thought
was
pretty
cool
and
it
showed
kind
of
for
an
application
which
components
had
the
most
change
in
them.
Are
you
guys,
thinking
about
doing
any
kind
of
a
3d
chart
of
any
kind
to
represent
the
transit
of
what
I
call
transitive
microservices?
B
Yeah,
it
was
there
in
the
initial
discussion
that
we
had
something
like
like
a
tree
map
kind
of
thing,
wherein
we
will
have
like
various
components
on
the
very
first
layer
and
when
we,
you
know,
get
deep
dive
into
a
single
component.
We
can
identify
what
all
dependencies
are
there
for
that
component.
A
Yeah
and
have
you
guys
looked
at
how
datadogs
displays
that
data,
because
they're
pretty
they've
got
some
pretty
cool
graphics
and
they
display
a
lot
of
data.
It
is
more
hierarchical.
I
think-
and
I
think
the
3d
stuff
is
starting
to
make
more
sense
for
these
really
complicated
dependency
maps
because
they
get
pretty
complicated,
but
datadogs
has
got
some
pretty
cool
stuff,
some
of
it.
It
looks
like
you
know,
it's
like
one
little
point
that
it
explodes
out,
so
it
can
be
hard
to
see.
B
A
And
you
know,
vr
is
going
to
become
more
and
more
popular,
so
everybody's,
going
to
eventually
some
companies.
I've
spoken
to
are
are
starting
to
buy
vr
headsets
for
all
of
their
employees,
they're
starting
to
do
vr,
vr
meetings
so
they're
starting
to
use.
You
know
the
metaverse
now
to
hold
meetings,
and
apparently
it's
pretty
interesting.
A
I've
heard
different
stories
about
the
the
meetings,
but
apparently
it
makes
you
feel
more
like
you're
all
in
the
same
room.
So
it
might
be
something
that
you
know
a
few
of
us.
If
we
want
to
buy
the
vr
headsets
we
might,
we
might
play
with
it
and
see
what
it's
like.
Oh,
we
there
was
a
company
in
santa
fe
that
I
think
erickson
had
invested
in
and
they
were
doing
nothing
but
building
out
vr
reports
or
really
complicated
reports.
A
A
A
I
have
reached
out
to
the
cto
of
aspen
mesh
they're,
pretty
interested
in
the
stuff
that
we're
doing,
and
they
do
have
an
interest
in
us
potentially
being
able
to
give
them
route
to
them.
The
logical
application,
so
you
could
literally
a
deployment,
would
would
no
longer
be
pushing
a
you
know.
Even
in
a
git
ops
world.
It
would.
A
So
let's
say
you
had
a
cluster
that
was
running
dev
and
then
you
could
aspire
to
mesh.
You
could
switch
it
from
dev
to
test
just
by
rerouting
which
which
cluster,
which
microservices
the
application.
The
versions
that
they're
using
so
deployment
would
no
long
would
really
be
a
call
to
ask
the
mesh
to
reroute
to
a
different
version
of
microservice.
A
Now
they
know
that
that
can't
be.
That
may
be
difficult
with
a
mono
database,
but
this
more
we
get
into
poly
databases,
the
more
likely
that
could
happen,
and
I
think
they're
starting
to
look
at
what
that
would
look
like
in
a
in
a
true
decomposed
kind
of
architecture,
value
stream
any
either.
One
of
you
have
any
updates
on
that,
or
should
we
have
any
chat
about
it?.
B
A
C
C
A
C
A
A
There's
one
section
that
is
one
category
of
catalogs
are
like
backstage
backstage,
focuses
on
setting
up
your
microservice
development,
environment
and
tracks
all
the
tools
you're
working
with
and
who
you
are.
So
you
register
it
to
the
backstage
platform
and
define
all
the
tools
kind
of
like
we
have
in
our
services,
where
you
can
show
the
cves
the
swagger,
and
they
have
a
lot
more.
A
That
they've
connected
to
it
like,
like
the
vault
or
like
the
secrets,
then
there's
what
we're
doing,
which
is
really
trying
to
track
the
life
cycle
of
a
microservice
and
relate
it
back
to
the
versions
of
the
applications
so
that
we
have
a
better
understanding
of
what
we're
moving
into
and
what
we're
managing
in
these
environments.
So
we're
tracking
the
versioning
and
the
the
and
the
inventory
and
then
there's
the
the
far
side.
So
there's
the
dev
side
and
then
the
op
side
are
the
the
tools
that
are
tracking
service
level
objectives
and
they're.
A
A
A
So
there
would
be
a
piece
of
it
that
we
would
say
once
you
register
your
service.
What
cookie
cutter
template
you
want
to
use
and
when
they
select
that
we
let
cookie
cutter
generate
that
the
other
way
would
be
to
go
ahead
and
look
at
backstage
and
let
backstage
be
the
collection
point
and
we
pull
that
data
from
backstage
into
our
environment
or
we
even
just
have
a
link
to
backstage.
A
A
I
believe
that
I
believe
that
we
can
do.
We
could
probably
create
any
kind
of
a
template,
but
right
now
I
think
we
should
just
look
to
see
how
it
how
it
works,
and
that's
it
that's
all
you'd
have
to
do
is
just
give
us
a
good
idea
of
what.
How
cookie
cutter
you
know
is
how
it
would
work
and
how
we
might
be
able
to
integrate
it.
B
A
A
It
says
a
centralized
software
catalog,
so
I
guess
they
do
consider
themselves.
They've
changed
the
I
think
the
messaging
around
it,
but
before
the
real
point
of
it
is
to
go
register
your
microservice.
This
was
written
by
spotify
and
they
had
a
problem
with
standardizing
on
the
lifecycle
of
every
microservice,
so
they
wanted
to
force
developers
or
not
force
them,
but
give
them
the
standard
ones
that
they
should
use,
and
this
is
how
this
got
started.
A
So
I
feel
like
this
might.
If
there
are
apis
that
we
could
pull
this
information,
that
they
already
have
about
the
base
version
of
the
microservice
that
we
could
potentially
then
just
integrate
with
backstage
and
then
manage
all
of
the
backend
pieces,
all
the
versioning,
all
the
inventory,
all
of
the
the
the
environment
changes,
and
that
might
be
a
healthy
way
to
go.
Considering
I
would
consider
it
a
sister
project
since
we're
both
in
the
linux
foundation.
It
would
make
sense
for
us
to
integrate
at
this
level,
so
we
have
two
rows.
A
We
could
go
down
to
solve
this
and
I
think
that
integrating
it
with
backstage
might
be
easier
than
building
it
out
with
cookie
cutter,
but
arvin.
I
would
say
this
would
be
a
really
good
research
project
for
you
to
kind
of
get
started
on,
and
if
you
want
to
take
a
look
at
backstage
as
well
and
learn
a
little
bit
about
backstage.
That
would
be
a
good
project
for
you
as
well.
A
A
A
A
We
need
more
people
who
can
can
help
with
the
coding,
because
it's
you
know
some
of
our
stuff
are
some
of
our
java
stuff
is
pretty
ugly
and
you
have
to
really
have
a
background
in
java
to
do
it,
but
some
of
this
new
stuff,
for
example,
arvin.
If
we
did
an
integration
of
backstage,
we
would
do
that
in
the
microservice
you
would.
You
would
write
that
just
in
a
separate
microservice
to
create
that
integration,
and
it
could
be
done
in
python
that
oh
here
I
should
add
this
client
to
this.
A
A
All
right,
I
think
that
that's
probably
a
good
plan
and
that's
why
I
was
reaching
out
to
more
people
who
have
the
background
for
teaching
that
they
might
be
able
to
get
involved
in
the
hackathon
as
a
somebody
who
could
help
teach
fujar
hasn't.
I
haven't
seen
him,
but
I
know
that
he's
working
with
steve
on
a
regular
basis
because
I
see
emails
from
them
he's
continuing
to
kind
of
automate
our
test
cases.
I
know
that
this
time
and
that's
the
same
with
aisha,
aisha
is
still
working
on
doing
some
work
around
the
years.
A
A
A
What
usual
wants
to
do
is
be
able
to
come
up
with
a
standard
plan
and
a
and
documentation
for
going
about
doing
that.
He
is.
He
runs
a
consulting
organization
and
he
would
like
to
take
that
plan
and
take
it
to
potential
customers
who
are
trying
to
manage
a
lot
of
microservices
and
they
want
to
do
something
around
get
ops
so
he's
working
on
they're.
The
two
of
them
are
working
on
that
as
well.
A
So
brad
claims
that
they're
pretty
close
to
doing
the
they've
kind
of
got
a
poc
together
and
that
team
is
growing.
Brad
has
recruited
over
the
last
month
he's
recruited
about
10
additional
people
to
work
on
this,
so
the
that
get
ups
model
is
moving
forward
and
I
think
it
already
has
the
integration
to
argo.
A
And
they're
recording
all
that,
so
if
anybody's
interested
they
can,
you
can
always
watch
what
they're
doing
and,
if
you're
interested
in
getting
involved
in
this
ujwal
and
and
brad
and
steve
just
started
talking
about
it
and
I'm
happy
to
make
sure
you're
added
to
any
of
those
meetings,
and
we
probably
should
make
the
we
should
start
recording
those
as
well.
So
you
know
it's
kind
of
like,
and
this
is
what
we
learned.
We've
been
learning
from
the
jenkins
community.