►
From YouTube: Ortelius TOC Nov 2021
Description
November 2021 Ortelius TOC Board Meeting
A
A
A
A
lot
quite
a
bit
has
happened
since
the
last
board
meeting,
which
is
a
good
thing.
Let
me
just
go
through
I'm
going
to
what
I'm
going
to
do.
Is
I'm
going
to
go
through
some
of
the
what
we've
done,
what
we've
accomplished
and
then
I'm
going
to
hand
the
road
map
over
to
steve,
just
hey,
jeremy,
there
you
are
I'm
going
to
have
the
hand
the
road
map
part
of
it
over
to
steve
and
just
to
let
everybody
know
steve,
probably
hasn't
seen
all
these
screens.
A
A
I
don't
see
him
on
today
to
hank
who
I
bugged,
at
a
from
a
linkedin
connection
to
tara
and
phil
and
phil
has
been
super
involved
in
the
project
from
the
years
back
tim,
kelton
and
doug
orr.
We
still
keep
in
contact
with
them.
They
we
keep
updated.
They
we
update
them
on
what
we're
doing
on
a
regular
basis.
They
were
the
first
two
people
on
the
toc
and
then
of
course,
bill
pertelli,
our
distinguished
coach
and
board
advisor
and
then
jerry,
jeremy,
davis,
from
red
hat
and,
of
course,
steve.
A
A
We
we
started
from
zero
and
siddharth
parikh,
who
is
running
our
ambassadors
at
the
time
bugged
me
to
create
a
linkedin
group
for
ortillius
and
that
quickly
jumped
to
292
members
in
a
very
short
period
of
time.
We
started
that
linkedin
group,
I
think
maybe
siddharth.
When
do
you
think
we
did
that
in
august.
B
A
A
So
what
we've
done
is
we've
created
our
own
conference.
We
host
it
on
twitch.
We
do
not
try
to
get.
We
don't
sell
it
like
a
regular
conference,
we're
sort
of
disrupting
that
we
don't
try
to
get
sponsors.
We
don't
try
to
drive,
lead
generation
or
anything
like
that.
We
simply
have
a
lot
of
fun
and
we
educate
and
we
give
our
contributors
an
opportunity
to
speak
for
the
first
time
at
a
conference
we
host
it
on
twitch,
I
I
call
it
the
campiest
conference.
A
A
A
We
participated
in
hacktoberfest.
This
was
a
weird
year
for
hacktoberfest.
They
did
not
digitalocean
didn't
start
pushing
that
they
were
going
to
have
a
hacktoberfest
until
like
the
second
week
of
october,
or
maybe
even
later,
we
kept
trying
to
reach
out
and
saying
hey.
Is
there
a
hacktoberfest
happening?
And
finally,
a
new
website
was
put
out
there.
We
did
end
up
with
27
accepted,
pull
requests,
which
is
it
kind
of
doubles.
What
we
normally
do
so
that
that
was
exciting.
A
We
have
been
in
the
conference
scene
this
year.
We
were
at
get
ops,
con,
north
america,
talking
about
ortillius
and
some
of
our
vision
for
what
we're
going
to
do
in
our
roadmap.
We
had
several
speakers
at
cdcon,
including
a
couple
of
people
who
are
not
contributors
but
have
found
the
product
and
done
some
kind
of
analysis
of
it
and
presented
it
adidagawal.
A
She
was
one
of
our
may
20th
presenters.
She
did
a
presentation
on
domain
driven
design.
She
did
a
great
job.
It
was
her
first
presentation
during
our
visionary
summit
and
we
asked
her
to
submit
that
to
devops
world,
since
it
was
virtual
and
made
it
easy
for
her
to
do
and
she
got
accepted.
We
were
super
excited
and
I
was
able
to
do
a
presentation
specifically
around
how
ortillius
tracks
microservices
so
we're
getting
some
exposure
out
in
the
in
the
general
world
we
have
opened
up.
We
have
started
our
first,
a
proper
governing
board.
A
In
order
for
us
to
be
an
incubating,
go
beyond
being
an
incubating
project,
we
have
to
have
a
governing
board
and
we
need
history
around
how
that
governing
board
operates.
We
built
out
new
bylaws
for
the
governing
board.
We
had
elections.
Actually
the
elections
are
still
running,
but
we
needed
to
we
needed
to
add
a
full
governing
board.
So
what
we
did
was
in
the
governing
board.
A
Steve
taylor
has
a
and
we
copied
this
from
jenkins
steve
taylor
has
a
permanent
position
on
the
board
and
there'll
be
six
additional
board
members
and
we
will
elect
three
new
ones
every
year.
So
it's
a
rotating.
Normally
it
would
be
a
two-year
term,
but
the
first
year
three
people
will
have
a
one-year
term.
So
next
year
we
will
have
an
election.
So
we
have
some
new
people
coming
in
every
year,
but
we
have
some
stability.
A
Brian
dawson,
from
the
linux
foundation,
through
in
his
hat
and
as
well
as
ann
marie
fred
from
red
hat
siddharth,
actually
recruited
her
for
us
siddharth,
has
been
our
ambassador
lead
over
the
course
of
the
last
18
months,
and
then
we
have
added
aisha,
khalik
and
sasha
wharton
and
sergio
canales.
So
we're
excited
to
see
how
this
new
governing
board
works
and
they'll
be
meeting
about
four
times
a
year
or
if
they
need
to
to
make
any
other
kind
of
voting
decisions.
C
A
C
A
So
we
will
know
that
after
they
close
on
november
27th
and
we'll
be
announcing,
who
is
the
new
champions
chair
on
the
20
on
the
on
december,
8th,
okay,
and
on
that
note,
I'm
going
to
pass
it
over
to
steve
to
go
over
the
road
map
discussion.
We
have
quite
a
few
things
in
the
pipeline.
We
have
a
lot
of
work
that
we
now
understand
that
we
need
to
do
and
just
to
get
us
started.
We
initially
when
we
first
started
as
deploy
hub
and
before
we
created
the
open
source
project.
A
The
only
the
only
thing
that
really
competed
against
us
that
we
could
see
in
the
open
source
world
was
backstage.
Now,
if
you
have
had
any
experience
with
backstage
you'll
understand
that
backstage
is
a
a
microservice
registration
catalog
but
they're,
not
managing
versions.
We
are
adding
the
version
and
the
dependency
mapping
and
the
bom
reporting
to
a
catalog.
A
There
are
other
tools
that
are
out
there.
There's
one
I
haven't
even
listed
on
here
called
noble9,
so
they're
starting
to
get
they're
starting
to
have
they're
starting
money,
is
starting
to
be
put
into
this
area.
You
know
we
started
with
a
just
talking
about
it
and
having
a
dream
to
build
out
this
catalog
and,
as
you
can
see,
we
have
quite
a
few
now
new
entries
into
the
marketplace.
C
C
A
So
we
talked
about
doing
this
than
the
last
one.
It
is
pretty
much
ready
to
go.
We
have
a
dev
environment
that
the
team
is
finally
doing
final
testing
and
documentation
on,
but
we
did
add
to
the
component.
We
added
license
consumption.
We
added
it's
it's
what
license
it's,
that
service
uses,
as
well
as
its
readme
information.
A
We
added
swagger
information
and
we
added
integrations
to
things
like
pagerduty
and
slack.
This
speaks
to
service
level
objectives.
This
is
probably
one
of
the
areas
that
gets
the
most
attention
in
the
commercial
market
and
in
fact,
a
lot
of
the
the
tools
that
I
had
on.
The
previous
slide
are
really
just
focused
on
ownership
and
production
and
providing
a
catalog.
So
anybody
who
wants
to
who
needs
to
support
a
microservice
knows
who
to
call
in
from
a
production
support
standpoint.
C
And
on
this
one
of
the
things
that
we
do
differently
than
everybody
else
is
this
information
is
versioned
with
the
component
version.
So
what
that
means
is,
if
you
have
a
version
of
your
microservice
running
in
production
and
you
have
a
new
one
in
qa,
you
don't
want
to
see
or
in
development.
You
want
to
see
how
the
the
swagger
information
has
has
changed.
Maybe
they've
added
another
parameter
or
something
like
that.
We
have
the
data
there
to
be
able
to
do
that
that
difference
report
as
part
of
that
process.
C
Also
on
the
cves
part
we
can
see
if
cves
are
being
fixed
and
resolved,
comparing
what's
coming
down
the
pipeline
from
development
into
production,
so
the
cve
box,
you
know
your
goal
is
to
have
it
empty
and
that's
some
of
this.
This
service
catalog
information,
that
is
that
we're
collecting,
is
going
to
be
really
important
when
we
start
doing
some
more
investigative
work
and
analysis
of
that
data
and
how
it
compares
to
what's
in
in
development
compared
to
what's
in
production
and
through
the
pipeline.
C
You
know,
after
the
fact
we're
looking
at
it
at
basically
at
compile
time
when
you
build
your
microservice,
what
is
it
dependent
upon
and
what
is
it
providing
basically,
the
way,
we've
kind
of
implemented
it
and
is
basically
a
couple
json
files
and
the
idea
being
is
we
have
a
a
microservice
will
produce
certain
endpoints
or
in
the
pub
sub
world,
they'll,
publish
certain
topics
and
then
it
may
or
may
not
consume
additional
endpoints
or
consume.
You
know
subscribe
to
certain
topics
once
we
have
this
mapping
at
the
component
level.
C
We
can
then
start
building
these
relationships
up.
So
we
can
see
that
a
depends
upon
b
b
depends
upon
c
and
c
may
depend
upon.
You
know
x,
so
those
relationships
will
be
able
to
be
discovered
through
this
mapping
mechanism
and
part
of
that
is
gonna.
Allow
us
to
really
look
at
a
a
version
of
an
application
and
be
able
to
look
at
how
all
the
transactions
relate
to
each
other,
it's
more
of
an
in-depth
type
of
bomb
report.
C
So
it's
going
to
be
really
being
able
to
take
these
low-level
relationships
at
the
component
level
and
roll
those
up
into
application
versions
and
so
on.
So
it
will
really
give
us
a
nice
view
into
what's
happening
between
at
application
level.
You
know
what
it's
consuming
now
one
of
the
things
down
the
road
is.
C
We
can
look
at
applying
telemetry
data
to
that
and
really
looking
at
where,
where
the
developers
think
a
transaction
going
is
going
and
where
it
actually
is
going
at
that
level
and
also
being
able
to
repair
report
errors
and
things
like
that
and
roll
up
log
data
and
metrics
from
that
side.
But
for
now
we
are
going
to
be
one
of
the
things
on.
The
roadmap
is
service
to
service
dependency
maps.
C
So
if
you
want
to
see
what
one
looks
like
just
a
google
hierarchical
edge
bundle
and
you
can
play
with
some
data
there,
one
of
the
things
I
like
about
that
that
visualization
is
it'll
deal
with
circular
dependencies,
even
though
developers
aren't
supposed
to
do
it,
they
do
it
anyways.
So
you
have
a
depends
upon
b.
B
depends
upon
c
and
c
depends
upon
a
for
some
reason.
They
do
it.
It's
not
the
best
programming
perspective,
but
that's
one
of
the
things
that
the
edge
bundling
will
allow
us
to
map
out.
C
Okay
go
to
the
next
one,
so
this
this
project's
actually
in
flight,
but
more
on
the
discovery
phase.
This
is
coming
out
of
the
our
australian
architecture
working
group,
so
brad
mccoy,
I'm
at
ben.
I
think
utkarsh
is
involved
in
a
few
other
people.
I
may
be
missing
on
on
that
level.
Sasha,
but
what
basically,
what
we're
looking
at
is:
how
does
artillus
fit
into
the
get
ops
model,
and
what
does
that
mean?
As
as
far
as
you
know,
where
do
we
get?
C
Where
do
we
start
something?
Where
do
we
end
something?
The
tools
that
we're
looking
at
at
this
level
are
kept
ortulius
and
argo,
and
obviously
we're
going
to
be
using
github
as
part
of
that
process?
The
cloud
native
part
for
our
kind
of
our
playground
is
azure
doesn't
really
matter,
but
that
just
happens
to
be
where
we
are
setting
up
our
development
and
test
our
playground
areas
up
in
our
our
zoor
cluster.
C
C
C
Of
course,
we
have
our
our
our
developers
there
with
their
fish
sticks
and
hot
dogs
and
their
beers,
because
that's
the
way
we
envision
developers
doing
their
commit
into
github
triggering
off
the
whole
process.
I'm
not
going
to
walk
through
every
single
step,
that's
happening
here,
but
basically
the
next
step
as
part
of
the
road
roadmap
is
to
actually
start
coding.
C
C
C
We
did
have
way
back
when
we
were
doing
our
microservices
we're
actually
using
flask
python
flask
as
our
underlying
microservices
framework,
and
when
we
went
to
roll
that
out,
we've
realized
that
it
wasn't
gonna
work,
so
we
actually
did
a
pivot
over
to
fast
api
for
python,
and
thanks
to
karam
and
a
few
other
folks,
ukarsh
we've
been
able
to
figure
out
how
to
make
those
resilient
ron
and
a
kubernetes
cluster.
Really
nice
deal
with
recoveries
and
scaling
very
easily
so
going
forward.
C
With
that
being
said,
one
of
the
things
that
we'll
also
be
adding
is
taking
our
istio
environment
and
allowing
us
to
expand
that
into
a
process
where
we
can
actually
have
some
of
our
microservices
in
in
the
dev
environment
and
the
rest
coming
from
our
prod
environment
as
part
of
that
process.
So
most
of
our
stuff
is
read
only
that
we're
we're
doing
so.
C
A
Schedule
and
goal
for
completion
of
this
micro,
this
architecture,
is
it
going
to
be.
Are
we
doing
that,
starting
that,
after
the
get
ops
and
the
service
to
service
dependencies?
What's
what's
what
is
the
team
thinking?
I
know
that
some
of
this
stuff
has
to
be
decided
by
the
governance
board,
but
in
terms
of
how
they're
going
to
run
that,
what's
the
thought.
C
So
initially
the
thought
is,
we
just
have
to
wrap
up
our
service
catalog
and
get
that
released.
We
are
on
that
part
we're
actually
focusing
on
the
very
last
step,
which
is
the
installation
piece
we
wanted
to
have.
It
came
out
from
the
community
that
we
should
have
a
a
single
line,
install
of
ortulius
into
your
kubernetes
cluster.
C
A
C
C
We
have
to
write
260
microservices
to
migrate
off
of
our
existing
monolith
and
just
not
a
practical
way
to
address
something
where,
when
we
need
to
have
new
functionality,
we'll
add
a
new
functionality
as
microservices
and
be
in
this
hybrid
mode.
I
suspect
the
hybrid
mode
will
be
around
for
several
years.
C
So
some
of
the
things
that,
as
usual
microservices
come
out
looking
at
how
our
database
is
going
to
change.
One
of
the
things
that
we
did
do
over
the
last
six
months
is
expand
our
database
to
be
a
support,
managed
databases,
so
a
postgres
managed
database
not
only
on
google,
but
also
on
azure
and
aws.
C
So
that's
one
of
the
things
that
we
allowed
for
the
configuration
and
also
we
brought
in
a
container
a
docker
container
that
would
actually
run
pro
stress
locally
for
developers.
So,
basically
you
can
just
start
up
a
container.
You
don't
have
to
worry
about
installing
postgres
or
anything
like
that,
so
the
developers
have
a
way
to
have
access
to
the
database
with
some
pre-loaded
data
to
work
with.
So
that's
some
of
the
things
that
we've
done
in
the
in
the
past.
C
The
graph
database
may
come
into
play
when
we
look
at
expanding
the
service
and
service
relationships
as
part
of
the
process.
The
more
like
tracy
calls
it
we're
data
hoarding
and
it
may
make
sense
to
move
to
a
graph
database
just
for
speed
to
navigate
the
relationships.
Also,
the
graph
database
may
come
into
play
with
machine
learning
that
we
may
need
to
do.
C
A
A
The
sooner
that
will
happen
and
we're
using
we're
using
artillious
as
a
test
case
for
this,
and
what
needs
to
be
done
to
make
sure
that
you
can
separate
data
between
those
clusters
and
be
able
to
route
a
single
new
service
to
a
group
of
users.
So
we're
we're
using
artillios
as
a
bit
of
a
test
case
around
that.
C
And
just
to
point
out
some
other
things
that
we've
done,
even
though
this
was
a
slide
about
just
some
links,
the
ortelius.io
we've.
Actually,
that
is
fully
implemented
as
a
hugo
server
that
runs
in
our
cluster
and
is
being
deployed
by
deploy
hub
and
artelias,
so
we're
actually
using
artelias
and
deploy
hub
to
deploy
our
stuff
to
our
azure
cluster.
A
C
C
C
How
old
is
your
version
of
a
package
compared
to
the
current
version?
Are
you
running
a
version
of
a
module?
That's
three
years
old.
You
know
because
that
could
affect
how
something's
running
in
production
you're
so
far
behind
that's
overlaid
on
top
of
the
cves
and
vulnerabilities
and
then
also
there's
some
new
projects,
starting
out
of
the
open
source
security
foundation.
C
C
Git
ops,
the
design
process
is
wrapping
up
and
then
we'll
go
into
the
information
implementation
phase,
and
we
have
kubecon
coming
up
cubecam
in
spain
that
will
probably
try
to
target
at
least
a
a
poc
around
at
that
level
for
kubecon,
spain.
I
think
that's
in
may
so
that's
kind
of
like
the
short
term
roadmap
that
we
have
going
on.
B
Yeah,
so
the
thing
that
I
worry
about
that
I
I'll
admit,
I
don't
have
a
ton
of
personal
familiarity
with
this,
but
you
know
the
first
thing
that
comes
to
mind
is
maintaining
integrity
in
a
multi-faceted
system.
So
what
are
your
thoughts
like?
Is
there?
Are
there
like
known
best
practices
around
us
that
you're
following
or
are
you
like
breaking
new
trail
with
with
what
you're
doing
here.
C
Right
now
we
are
sticking
with
the
single
monolith
database
until
we
understand
better
around
the
poly
and
how
how
our
transactions
can
fit
into
it.
It's
going
to
be
really
transaction
specific,
driven
and
not
necessarily
we're
going
to
take
our
whole
database
and
blow
it
into
a
poly
database.
That's
just
not
going
to
be
something,
that's
practical!
C
C
Things
like
when
you
look
at
gathering
pieces
from
like
the
the
telemetry
side
and
prometheus
that
it
may
make
sense
for
those
pieces
to
go
into
a
separate
database
instead
of
going
right
into
our
monolith.
So
when
we
start
collecting
metric
data,
that
may
make
sense
where
we
put
that
as
part
of
it,
because
if
we
lose
integrity,
it's
not,
as
you
know,
we're
not
going
to
shoot
ourselves
in
the
foot.
A
B
B
C
Exactly
especially
when
you
look
at
the
graph
databases,
there's
there's
about
a
half
dozen
of
them,
and
some
of
them
are
very
language
specific.
So
if
you're
writing
in
java,
there's
going
to
be
one
that
that's
tailored
to
work
with
java,
really
nice
there's
other
ones
that
are
tailored
to
go
around
the
go
link.
You
know
so
it
it's
one
of
those
that
we're
looking
at.
A
We
really
what
we
really
need
as
part
of
our
open
source
community,
and
I
continue
to
look
for
it
is
we.
We
have
plenty
of
university
students
who
are
really
interested
in
machine
learning
and
data
science,
but
we
don't
have
a
good
mentor.
So
if
anybody
out
there
knows
a
good
mentor
in
this
area,
we
have
so
much
data.
A
We
really
believe
that
we
could
do
a
lot
of
predictive
reporting
and
we
can
start
doing
the
things
that
I
keep
talking
about
around
risk
analysis
based
on
the
data
that
we
have
and
there's
probably
things,
I'm
not
thinking
about.
So
we
have
a
lot
of
college
students
out
there
who
are
interested
in
data
science
and
machine
learning,
it's
kind
of
what
they're
they're
where
their
head
is,
but
we've
not
I've
not
identified
a
good
mentor
who
can
kind
of
take
the
side
of
the
the
technology
on
and
give
us
some
clear
direction
on.
A
C
So
you
know
something:
that's
running
in
development
versus
something
that's
run
in
production
would
have
a
different
weight
to
it
and
traversing
these
relationships
is
and
and
kind
of
understanding
them
is
going
to
be
where
the
data
science
is
going
to
come
into
play.
So
it
may
not
be
ml
cruising
through
terabytes
of
data,
but
it
may
more
be
on
the
ai
side
trying
to
understand
how
to
make
better
decisions
around.
A
The
data
even
from
a
pattern
matching
perspective,
and
we
we
literally
could
go
in
as
steve
pointed
out,
we're
going
to
be
tracking
cbes.
We
could
be
able
to.
Potentially
we
could
use
the
data
and
say
you
know
what
this
cve
has
been.
This
has
been
repaired
and
we're
seeing
it
in
other
microservices
and
provide
an
entire
report
for
your
entire
enterprise.
It
says
these
are
the
microservices
that
still
have
these
vulnerabilities
that
we
that
you're
not
haven't
addressed
yet
so
again.
A
D
A
D
A
Thank
you,
hank
yeah,
absolutely
and
I'm
glad
tara.
I
thank
you
for
bringing
up
the
database
part
because
data
is
what
we're
in
the
business
of
of
grabbing
and
doing
something
with
so
it's
it's
really
a
quarter
the
discussion
and
bringing
additional
value
to
the
to
this
open
source
project
and
making
it
more
relevant
in
terms
of
this
discussion.
A
That's
happening
right
now
around
supply
chain,
because
if
you
think
what
we're
really
doing
is
we
are
doing
a
very
detailed
job
of
tracking
microservices
supply
chain
for
an
organization
and
potentially-
and
we've
always
talked
about
this-
we
want
to
be
able
to
do
it
even
at
an
open
source,
microservice
level.
So
if
we
were
hosting
this
in
a
in
a
way
that
we
could
right
now,
we
have
it
in
at
the
deploy
hub
level.
A
We
have
a
sas
environment
that
we
keep
looking
at
starting
to
add
open
source
microservices
that
people
can
consume,
because
we
know
that
they're
coming
they're
going
to
be
there,
but
once
we
start
doing
that,
we
can
then
report
on
everybody
who's
anybody
in
the
world
who's
using
a
particular
microservice.
I
know
that
sounds
lofty,
but
it's
just
data,
it's
very
possible
for
us
to
do.
We
could
show
every
microservice
that
has
a
vulnerability,
that's
that
needs
to
be
corrected
and
provide
that
kind
of
reporting.
E
Yeah
kind
of
this
is
hank.
I'm
going
to
take
a
different
approach.
I'm
going
to
take
a
bottoms-up
approach.
Kind
of
my
my
daily
week
is
infrastructure
right.
So
one
of
the
things
we're
looking
at
in
and
you
look
at
a
lot
of
people
that
are
not
circuit
cloud
plates
that
have
brick
and
mortar
that
have
on-prem
assets
that
have
data
right
or
you
have
edge
devices.
You
can
call
it
another
data
center
devices.
E
Looking
at
that
hybrid
model,
one
of
the
things
that
we're
looking
at
is
how
do
we
simplify
that
and
there's
a
few
platforms
out
there
that
we've
done
some
analysis
on,
but
it
speaks
to
mapping
and
micromicroservices
dependency
mapping
and
how
we
track
all
those
things.
So
one
is
they're
platform.
Nine,
another
one's
spectro
and
tanza
came
up
with
with
a
system
called
tap
which
changed
the
application
platform.
E
9
takes
a
get
ops
approach
to
deploying
infrastructure
as
a
whole
and
couples
that,
together
with
the
application
stack
into
the
infrastructure,
stack
deploying
it
to
a
containerized
environment,
whether
that's
a
bare
metal,
an
aks
cluster
ets
cluster,
whatever
it
looks
like
so
I'd,
be
curious
to
see
where
this
goes
with
it
with,
I
guess,
with
the
lens
that
there's
there's
always
going
to
be
some
sort
of
hybrid
model
on
how
you
manage
those
edge
data
center
to
cloud
computing
workloads
consistently
across
dependencies
and
stuff.
So
anyway,
just
putting
that
out.
E
C
Yeah,
so
one
of
the
things
in
the
artillious
world
is
a
component
can
be
as
can
pretty
much
represent
anything
it
could
be.
You
know
a
two
gigabyte
websphere
ear
file,
or
it
could
be
a
docker
image
or
it
could
be
a
test
case.
It
also
can
be
a
terraform
to
stand
up
the
the
cluster
so
for
us,
infrastructure
is
just
seen
as
another
component
that
we
need
to
bring
into
the
picture
of
what
is
needed
for
this
application.
This
version
of
the
application
to
run.
C
C
So
that's
the
one
of
the
goals
that
we're
trying
to
bring
into
play
is
that
that
viewpoint
like,
like
you,
said
that
lens
of
of
where
we're
viewing
the
data
from
now
because
of
the
relationships
that
artelias
has,
you
can
look
at
it
from
the
developer's
point
of
view.
You
know
my
blast
radius,
I'm
I'm
breaking
this
component.
Who
else
am
I
going
to
affect
to
the
sre
view?
I
have
this
this
new
version
of
the
application.
C
A
A
Now
the
way
we
position
ortilius
we
we
have
to
you
know
we
have
to
pick
a
poison
so
to
speak,
and
we
felt
that
microservices
was
the
best
thing
to
to
to
position
it
around.
But
it's
truly
it
can
it's
just
parts
or
parts,
it's
simply
managing
parts
in
their
relationship.
So
it
doesn't
matter
what
the
parts
really
are.
If
you
really
boil
it
down
to
you
know
what
it
can
do,
but
that's
so
broad
it'd
be
hard
for
people
to
understand.
Until
you
have
asked
those
questions
like
hank
just
asked.
C
They've
put
a
lot
of
hard
work
in
extra
time
time
at
weird
hours,
and
we
really
appreciate
everybody.
That's
been
contributing
and
making
the
the
project
move
forward.
We
have
like,
like
we,
you
saw
on
the
roadmap.
We
have
some
fun
stuff
coming
up,
but
that's
not
the
only
thing.
So
if
you
have
new
ideas,
please
bring
it
to
the
working
group
meetings.