►
From YouTube: Ortelius Visionaries 2022
Description
An Amazing Community of Committers
On May 20th, 2022 the Ortelius community will host our 4th ‘Microservice Visionaries’ gathering to celebrate the community committers of Ortelius, discuss microservice best practices, and drive awareness of the benefits and challenges of implementing a truly shared microservice oriented architecture. We host the majority of the event on the Ortelius Twitch TV Channel giving our committers a platform for presenting technical topics.
https://ortelius.io/blog/2022/04/15/ortelius-microservice-visionaries-2022/
A
B
B
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
E
E
A
A
A
A
A
A
A
A
A
A
A
B
D
B
B
F
G
D
B
D
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
H
A
A
D
D
B
I
M
D
I
I
I
We
also
do,
as
we
know,
presentations
that
we're
going
to
be
hosting
that
will
be
on
twitch
as
sergio
indicated
and
those
presentations
have
all
been
pre-recorded
as
soon
as
this
is
over,
we
will
start
using
that
content
over
the
course
of
the
next
six
six
months
to
drive
more
more
traffic
to
our
website,
and
that
brings
me
to
a
point
that
I
forgot
to.
Oh,
I
forgot
to
put
my.
I
bet
you
guys
can
hear
me
better
now.
I
I
We
have
250
google
group
members
so
when
we
send
out
an
email,
it's
now
going
out
to
250
members
and
we
have
67
committers,
so
we
have
definitely
defined
a
pretty
awesome
growing
community.
The
the
community
continues
to
grow.
I
can
say
what
we
haven't
done
as
well
is
the
67.
Even
though
we
have
67
committers,
we
need
more
activity
around
pull
requests
and
when
steve
gets
back,
I
think
I'll.
Have
him
talk
about
that?
Just
for
a
minute.
I
You
know
it's
always
good
to
talk
about
what
you
did
well
as
well
as
what
how
where
it
is
that
we
need
to
improve
on
outreach,
is
doing
really
really
well.
Syme
has
really
taken
this
project
on
and
has
has
done
a
great
job
of
the
podcast.
In
particular,
we
had
four
podcasts
this
year
so
far,
which
is
great
because
this
is
only
month
five.
I
The
podcasts
are
are
getting
out
there,
depending
on
who
it
is
if
people
are
starting
to
pick
it
up
and
watch
the
podcast
we
have
brad
mccoy
is
doing
a
presentation
in
valencia
at
the
cd
events,
I'm
doing
a
presentation
at
supply
chain
security
con
I'm
doing
one
at
jfrog,
I'm
doing
one
with
a
trisentis
and
I'm
also
doing
one
at
cdcon.
So
we
are
getting
the
ortilius
message
out
through
some
of
these
activities.
I
So
if
you've
been
part
of
one,
my
I
think
my
suggestion
here
in
this
area
is:
we
need
more
of
you
to
be
brave
to
submit
for
doing
these
talks.
Some
of
you
are
really
really
good
presenters
and
I've
noticed
that
you're
a
little
hesitant
to
like
to
submit
to
a
devops
world.
I
think
we
all
have
to
be
a
little
more
brave.
We
need
a
little
bit
more
of
arvin's
approach.
I
Arvind
always
puts
his
self
out
there
and
I'm
always
so
proud
of
him
when
he
does
so
some
of
the
work
that
we've
done
on
the
product,
just
because
some
of
you
are
not
on
the
architecture
meeting.
So
just
some
areas
that
we
have
focused
on,
so
we
really
focused
on
solving
some
of
the
problems
around
supply
chain.
One
of
the
problems
that
we
started
hearing
about,
that
we
were
able
to
add
as
a
feature
into
ortillius.
Is
this
aggregation
of
s-bom
information
up
to
the
application
level?
I
So
what
we
did
was
we
started
aggregating
that
data
up
so
now
at
the
application
level,
you
can
view
an
s-bomb
and
you
can
view
all
the
the
vulnerabilities
based
on
all
of
the
underlying
microservices
we're
the
only
ones
right
now
that
are
capable
of
producing
this
in
the
catalog.
So
it's
an
area
that
we
should
be
super
proud
of
now.
On
that
same
note,
we
added
package
search
searches
across
all
applications.
So
you
can
you
can
submit
this
when
I
ran
this
search.
I
I
just
said
every
everything
show
me
every
package
I'm
using,
but
you
could
put
in
here,
for
example,
log4j
and
you
could
see
every
application,
that's
consuming
log4j
and
you
could
see
what
version
of
the
application
is.
What
component
is
using
it
and
what
version
of
the
package
it's
using
so
now
we're
starting
to
take
the
intelligence
around
this
devops
gathering
and
starting
to
use
it
to
produce
important
kind
of
reports.
I
F
F
F
So
what
we're
planning
to
do
with
the
xrpr
ledger
is
be
able
to
store
a
component
version,
the
json
definition
for
component
version
on
the
blockchain
and
then
in
the
ledger,
and
then
in
the
doing
the
same
thing
for
an
application
version
and
storing
that
json
definition
on
the
blockchain
ledger
as
well.
This
gives
us
an
immutable
view
of
what
those
versions
look
like
and
it's
going
to
fit
well
into
the
the
supply
chain
concept,
because
everything
in
the
supply
chain
people
are
trying
to
make
it
immutable.
F
So
you
can
make
sure
that
nobody's
messing
with
with
your
applications
and
stuff,
and
this
is
where
we
can
use
that
information
that
immutable
information
to
drive
different
supports
drift.
Those
type
of
things,
so
the
actual
implementation
is
going
to
be
in
using
xrpl
and
nfts,
which
is
non
non-fungible
tokens
as
part
of
the
backing
place.
So
that's
what's
kind
of
happening
on
that
front.
F
F
So
let's
say
you
have
a
component
version
out
there.
It
has
two
vulnerabilities
and
then
somebody
finds
a
new
one
today,
because
the
blockchain
is
immutable.
We
wouldn't
be
able
to
go
back
and
update
that
to
say
that
there's
three
vulnerabilities
now,
but
we
would
be
able
to
make
that
association
in
real
time
to
the
vulnerability
database
and
show
that
there's
now
three
three
vulnerabilities.
When
yesterday
there
were
two.
F
F
So,
if
you
think
about
you
know,
you
have
to
know
like
what
operating
system
or
what
hardware
the
binary
was
built
on.
Was
it
built
on
an
arm
or
an
amd
processor,
because
that'll
change?
How
the
output
of
the
program
is
what
what
version
of
the
operating
system?
What
patches
were
on
the
operating
system
for
the
compiler?
All
that
information
needs
to
be
stored
in,
and
that's
going
to
come
through
as
different
s-bombs
that
we
will
go
through
and
aggregate
together
and
throw
on
the
blockchain.
I
So
if
any
of
you
are
curious
and
want
to
know
more
about
s-bomb
steve
did
write
a
really
interesting
blog
out
on
the
deploy
hub
site
steve.
You
want
to
pull
that
up
and
maybe
put
it
in
the
chat
and
some
of
you
may
know,
but
I
was
elected
to
the
board
of
the
open
ssf
as
the
general
member
for
the
community.
I
So
I
we
got
invited
to
go
to
washington
dc
last
week
and
we've
been
on
a
what
they
call
one
of
the
streams
for
better
securing
open
source
software
and
the
stream
that
we're
on
is
called
s-bombs
bombs
everywhere,
and
one
of
the
areas
that
we
saw
as
a
problem
is
the
accessibility
of
s-bombs
and
the
use
of
it.
Because
we
all
have.
We
have
the
ability
to
generate
s-bombs
now,
but
nobody
really
uses
them.
I
People
are
starting
to
think
about
applying
them
in
some
way,
but
not
really
so
that
this
was
some
of
the
motivation
in
making
sure
that
we
are
exposing
s-bombs
and
associating
them
to
an
application
version
and
then
figuring
out
a
way
using
blockchain
to
make
them
immutable.
So
that's
kind
of
the
the
genesis
of
this
particular.
I
Some
of
the
developers
who've
been
working
on
the
blockchain
effort
for
their
work,
so
it
would
be
probably
a
short
kind
of
burst
because
it's
really
a
poc,
but
this
gives
us
some
funding
to
actually
pay
some
of
the
people
who
have
been
working
on
this
all
right,
and
on
that
note,
let's
talk
about
badges.
Some
of
you
may
have
gotten
a
badge
over
the
period
of
the
the
evening.
Let's
just
go
over
some
of
the
folks
mark
eisenberg,
he
was
got
a
badge
at
the
ambassador
bronze
level.
I
He
did
a
podcast
for
us.
We
have
three
or
actually
four
new
speakers.
We
have
turja
miklos,
pavin
and
pia.
They
are
our
first
time
speakers
at
the
at
the
summit
today,
so
you
will
be
able
to
hear
some
of
their
their
talks.
All
of
them
have
come
to
us
from
different
individuals.
Siddharth
has
been
great
to
recruit
a
couple
of
the
folks
from
that
west
and
I
have
heard
their
presentations
and
they're
excellent.
I
So
let's
say
you
want
to
do
it
present
a
talk
at
kubecon
or
any
of
the
linux
foundation,
events
or
a
devops
world.
They
will
often
ask
you
for
recorded
versions
of
your
presentations
in
the
past.
This
was
really
hard.
This
was
a
barrier
that
I
struggled
with
because
I
would
do
presentations,
but
they
wouldn't
record
all
the
presentations
they'd
only
record
some
of
the
like
the
keynotes,
so
I
wouldn't
have
good
material
to
put
out
there
until
I
started
getting
recorded,
and
then
I
had
that
material
and
then
I
started
getting
invited.
I
So
if
you
have
never
done
a
presentation
these
every
six
month,
events,
there
are
a
lot
of
workforce
to
put
together
they're
fun.
We
have
sergio
to
thank
for
really
pulling
all
of
this
information
together
and
and
building
the
platform
to
present
it,
but
it
gives
you
the
opportunity
to
get
your
name
back
out
there
in
terms
of
doing
presentations
and
that's
the
that's
one
of
the
main
reasons
why
we
do.
It
is
so
that
the
community
has
a
platform
to
kick
off
their
outreach.
I
So
now
he
is
now
one
of
our
legends,
so
he
has
now
received
a
bronze
in
at
the
legend
category.
For
those
who
who
may
not
know
how
we
have
this
structured,
we
have
three
categories
that
you
can
earn
badges
in.
We
have
ambassadors
who
are
our
outreach
group,
so
anybody
who
participated,
for
example
in
today's
presentations
are
part
of
the
ambassadors.
I
Syme
has
reached
a
silver
level
for
ambassador.
He
has
done
a
great
job
with
building
out
the
outreach
community.
He
continues
to
really
push
that
podcast,
and
that
is
super
important
because
he's
doing
it
on
a
monthly
basis,
so
we're
starting
to
get
kind
of
repeat
business,
and
he
has
been
able
to
recruit
some
very
interesting
folks
for
doing
that,
and
then
we
have
our
superstar
for
this
time,
which
is
sergio
he
has
achieved
silver
legend.
I
N
I
Not
easy
to
do
I
we,
I
also,
I
think
I
forgot,
let
me
see,
did
I
I
think
I
might
have
forgotten.
Yes,
I
did.
I
forgot
victor
farcik.
He
has
also
received
a
he's
at
the
ambassador
bronze
level
for
participating
in
a
a
podcast,
so
anybody
who
participated
in
a
podcast
over
the
course
of
the
last
five
months
also
got
a
bronze
badge
all
right
now
we
are
actually,
I
say
head
to
twitch,
but
we're
not
gonna
do
that.
I
So
we
decided
to
really
talk
about
why
we
created
a
microservice
catalog
in
the
first
place
and
sasha
is
going
to
lead
that
discussion
so
we're
going
to
for
the
next.
You
know
15
20
minutes
we're
really
going
to
talk
about
the
genesis
of
a
microservice
catalog,
because
we
want
to
use
this
opportunity
to
to
do
some.
I
would
call
missionary
work
so
that
all
of
you
who
have
been
here
and
have
start
are
working
on.
I
P
K
D
D
P
Q
I
P
I
You
get
better
at
it,
the
more
you
do
it,
the
the
more
the
better
you
get
at
it,
brian
dawson.
I
saw
that
he
just
he
joined
brian.
Could
you
say
something
about
that,
because
you've
been
doing
presentations
for
a
long
time?
And
you
know
this
visionary
summit
is
really
part
of
educating
and
providing
everyone
a
platform
to
learn
to
present.
R
R
R
Continue
to
push
through
it
continue
to
push
through
the
nervousness
encounter,
different
situations
screw
up
in
different
places.
You
know,
learn
what
I
can
learn,
but
also
realize
that
that
no
matter
what
the
sky
wasn't
gonna
fall.
I
don't
know
you
know
tracy
of
exactly
what,
if
that's
what
you're
looking
for,
but
that's
sort
of
what
my
journey
has
been
right.
D
I
Nobody
else
until
then
that
I
had
that
I
had
no,
no
other
presentation
that
I
had
done
had
done
that
for
us,
so
I
was
able
to
then
once
I
had
that
done
done,
that
presentation
for
devops
world.
I
used
that
to
apply
for
other
speaking
engagements,
so
I
have
cloudbees
to
thank
for
my
opportunity
to
be
able
to
to
to
speak
because
it
was
really
hard.
I
still
have
not
been
accepted
at
kubecon,
yet
I
look
forward
to
that.
I.
I
Got
in
there
I
I've
not
achieved
that
yet,
and
I
I
I
continue
to
try.
I
I
submitted
recently
for
kubecon
in
october,
so
we'll
see
what
happens,
but
I
get
I
get
accepted
and
so
many
others
and
it's
because
I
had
that
one
opportunity
to
have
my
presentation
recorded
and
then
people
people
see
that
I
actually
could
present.
So,
if
you're,
a
good
presenter
we're
going
to
capture
it
and
you
can
use
it.
Q
F
And
none
of
you
know
all
that
knowledge
was
just
kept
in
that
in
those
conference
rooms
for
a
couple
days
and
then
you
went
home
and
it
all
was
lost,
which
was
a
shame
and
nowadays
with
folks
recording
stuff
and
pushing
it
out.
I
think
we're
getting
information
out
to
a
wider
group,
which
is
great
yeah,
sasha
you're
up
you're
up.
S
I
So
sometimes
you
stumble
into
you
can
kind
of.
I
call
it
force
gumping
your
way
into
a
new
idea,
but
if
you
think
about
our
history
in
terms
of
where
deploy
hub
came
from,
we
in
a
previous
company
called
openmake
software
were
really
into
builds
software.
Compiling
links,
that's
all
we
thought
about
all
the
time
was
how
to
make
the
build
faster,
how
to
make
it
more
accurate
how
to
control
it,
how
to
tighten
it,
how
to
make
sure
you
didn't,
have
debug
flags
running
in
a
production
environment.
I
Not
everything
uses
the
same
compiler
in
a
monolith
application
you
may
have
different,
you
may
have
a
resource
compiler
and
you
have
a
regular
compiler.
So
every
object
had
its
own
thing
right.
It's
had
its
own
way
of
doing
things
when
we
started
looking
at
how
we
were
shifting
from
monolith
to
microservices.
I
We
started
understanding
something
really
important,
and
that
was
we
lose
the
logical
application,
which
means
that
we
don't
have
a
way
to
control
dependencies
as
they're
moving
across
the
life
cycle
in
the
same
way
as
we
did
if
a
new
library
was
updated
in
git,
and
now
you
recompile
every
application
that
uses
that
statically
linking
it
and
pushing
it
out
to
production.
So
how
do
you
solve
that
problem?
And
that's
really
where
we
started
thinking
about
how
to
build
out
a
component
driven
release
process
and
that's
really
how
we
thought
about
it?
I
A
component
driven
release
process
and
phil
gibbs,
who
wrote
some
of
the
back
in
started,
understanding
that
it
wasn't
just
a
component-driven
release
process,
but
we
needed
to
version
it.
We
needed
to
understand
the
versions
in
order
to
be
able
to
do
incremental
releases
and
when
you
think
about
a
microservice
world,
every
microservice
is
independently
deployed,
so
we
are
always
doing
incremental
releases.
I
So
you
pull
all
that
together
and
you
step
back,
and
you
say
how
do
you
solve
it,
and
you
begin
thinking
about
things
like
service
catalogs
and
how
a
service
catalog
solved.
The
problem
for
enterprises
for
managing
the
bigger
applications
that
an
athletic
that
a
enterprise
would
use
and
how
to
centralize,
where
those
bigger
applications
or
those
big
bigger
services
were
like
what
version
of
oracle?
Should
we
download
if
we're
going
to
stand
up
a
new
environment?
I
I
K
I
The
essence
of
everything
that
we
we
have
always
done
from
the
beginning
of
our
career
in
terms
of
tracking
changes.
It's
a
configuration
management
problem
that
we're
solving,
but
that
term
now
is
called
supply
chain
management.
So
basically
we're
it's
the
same
thing,
just
a
new,
a
new
just
a
new
angle.
P
I
P
I
And
by
the
way,
that's
why
we
do
this
celebration
on
may
20th.
It's
because
may
20th
is
the
date
that
abraham
ortilius
released
his
first
world
atlas
and
in
essence,
if
you
think
about
what
our
what
the
ortillius
catalog
is,
it
is
a
map
of
every
microservice
who's,
consuming
it
where
it's
running
what
cluster
so
we're
literally
mapping
out
a
cluster
with
artillios.
P
F
Yeah,
so
what
like
tracy
was
saying,
one
of
the
things
that
we
recognized
is
we
needed
to
represent
deployable
objects
as
components
and
to
dive.
In
a
little
more,
we
needed
to
look
at
the
versions
of
those
components,
because
you
could
have
one
version
in
production:
that's
different
than
the
version.
That's
in
qa
that's
different
than
the
version,
that's
in
development,
so
we
needed
to
have
that
that
versioning
com
aspect
to
ortelius
and
that
allowed
us
to
really
look
at
how
things
change
over
time.
Now.
F
The
next
thing
that
we
recognized
was
that
you
needed
to
package
together
those
component
versions
into
something
that
you
can
represent
at
the
application
level.
You
could
also
think
of
an
application.
We've
been
toying
with
this
for
years
is
whether
we
stick
with
application
go
to
project
or
solution
or,
however,
we
want
to
think
of
it.
But
there's
going
to
be
the
next
higher
level
where
we
package
those
component
versions
into
an
application
version,
and
that's
where,
because
we
have
that
logical
application
version,
we
can
actually
diff.
F
You
know
what
are
what
com,
what
components,
change
between
production
and
what's
in
the
pre-prod
environment,
so
the
sres
can
see
what
type
of
impact
they're
they're
going
to
get
when
they
roll
this
out.
So
that
was
one
of
the
key
things
that
we
put
into
ortilius
now,
one
of
the
challenges
that
we're
kind
of
having-
but
I
think
it's
going
to
work
out-
is
we're
recognizing,
like
docker
images,
which
we
consider
a
component
version,
have
packages
within
them,
so
we
actually
have
components
within
components
right
now.
F
F
So
that's
kind
of
like
where
the
s-bomb
comes
in
we're
looking
at
taking
the
s-bomb,
which
is
going
to
list
out
the
package
level,
information
associate
that
to
the
component
version
and
then
we'll
do
another
level
of
aggregation
of
the
component
versions
up
to
the
application
version
level.
Now
some
of
the
things
that
we
haven't
gotten
into
at
the
s
bomb
level
is
like
how
to
record
hardware
s
bombs.
P
I
Oh,
quite
some
time
ago,
actually
so
before,
deploy
hub
was
created,
we
had
the
base
of
vortilius
was
owned
by
a
company
called
openmake
software.
It
was
the
metamorphosis
of
our
build
tool,
turning
into
a
release
management
tool,
because
people
kept
asking
us
to
manage
releases,
but
I
always
I
didn't
really
feel
like,
even
though
the
team
at
the
time
believed
that
there
would
be
one
release
tool
to
rule
them
all.
I
never
believed
that.
I
always
believed
that
you
know
every
component
has
its
own
logic.
I
I
We
did
a
lot
of
magic
when
it
comes
to
restructuring
the
company
so
that
the
the
code
base
that
is
now
ortillius,
could
come
out
of
openmake
software
and
go
into
deploy
hub
and
then
deploy
hub,
contributed
that,
but
we
knew
I
knew
years
before
that
I
wanted
to
have
an
open
source
version
of
this
particular
product.
You
know
there
is
something
to
be
said
as
you
get
as
you
progress
in
your
career
and
you
get
a
little
older.
I
I
I
You
you
end
up
selling
your
company
early
when
you
do
that
which
means
you're
letting
go
of
your
the
code
base
anyway.
The
second
way
would
be
to
take
the
open
source
route,
which
means
that,
instead
of
handing
it
off
to
a
vc,
we're
handing
it
off
to
the
community
and
allowing
the
community
to
drive
where,
where
and
how
the
product
is
going
to
be
built,
and
ultimately
those
products
are
always
much
better
than
what
a
vc
board
can
decide
on,
because
they're
going
to
just
focus
on
income
income
income,
which
is
important.
I
But
if
we
were
to
do
that,
I'm
guessing
that
we
would
still
be
looking
at
trying
to
solve
monolithic
problems
because
that's
where
most
of
the
money
is
right.
Now
it's
not
in
microservices
everybody.
We
talk
about
them,
but
most
companies
are
still
doing
monolithic
development.
Not
a
lot
of
companies
are
doing
microservices
we're
looking
at
solving
a
problem
that
most
companies
will
see
in
maybe
two
or
three
years.
I
I
That
is
one
of
the
areas
that
we
need
to
improve
on
and
then
the
other
area
that
we
need
to
improve
on.
While
it's
starting
to
improve
is
adoption-
and
I
know
that
sergio
has
talked
about
that.
So
I
think,
as
we
look
the
from
now
to
the
next
six
months
of
in
our
beer
and
donuts,
we
will
hopefully
have
some
adopters
doing
these
presentations.
I
We
had
one
that
was
going
to
depeche,
but
he
had
a
he.
He
just
couldn't
pull
it
together,
and
I
know
that
next
time
he
in
december,
I
think
he
will
do
a
presentation
on
on
their
adoption.
But
that's
those
are
areas
that
we
need
to
focus
on
in
terms
of
improving
this
particular
open
source
community.
I
P
I
P
F
Yeah,
so
we
have
some
fun
things
happening
and
you
know
we.
We
talked
about
the
blockchain,
so
that
is
going
to
be
an
area
of
interest
that
we
need
to
build
out
more
along
the
s,
bombs
and
vulnerabilities.
That
part
we
have.
You
know
we
we've
plumbed
it
together,
so
we
have
some
basic
stuff
working,
but
there's
some
improvements
that
we
need
to
make
on
that
that
side,
one
of
them
is
being
able
to
fetch
the
data
from
the
open
source
security
foundation.
F
F
We
have
libya
that
aisha
is
working
on
she's,
taken
a
new
position,
so
she's
had
a
kind
of
back
off
for
a
little
bit
on
that,
but
we
have
libyar
stuff,
which
is
like
giving
us
how
like
the
age
of
packages
if
you're
consuming
them,
are
you
using
the
latest
one?
Are
you
five
versions
behind
utkarsh
did
a
little
bit
of
work
on
some
new
representation
of
how
things
are
happening
with
application
versions
over
time,
so
some
new
graphing
or
graph
libraries
that
we'll
be
using.
F
So
those
are
the
type
of
things
that
we
have
going
on
and
also
brad
mccoy
has
been
pushing
the
get
ops
process
with
captain
and
argo.
We
are
trying
to
get
to
that
last
sprint
of
getting
the
final
pieces
in
place
to
pull
it
all
together.
So
we
have,
you
know,
work
done
over
here,
work
done
over
there
and
we
just
need
to
put
it
all
together.
So
that's
some
of
the
things
that
we're
going
to
be
focusing
on
in
the
next
six
months.
I
And
there's
some
things
I
have
on.
I
have
things
on
my
wish
list
too.
I
I
think
we
should
start
having
a
discussion
about
integrating
with
backstage,
because
if,
if
there's
folks
already
have
adopted
backstage
and
they
they
tag
their
when
they
register
microservice
and
backstage
you
can
tag
it
and
those
tags
could
be
directly
mapped
to
our
domains
and
then
we
could
start
doing
the
versioning
on
the
back
end.
So
I
think
we're
interesting
complement
to
backstage
and
backstage
is
also
a
cncf
project.
It's
probably
going
to
be
graduating
soon.
F
F
There
will
be
integrations
that
we'll
need
to
make
down
the
road
with
sigstor
persia,
so
there's
a
lot
of
stuff
at
the
supply
chain
level
that
will
because
the
way
ortiz
is
designed,
we're
just
gonna,
be
we
just
suck
up
all
this
data
to
be
able
to
pull
things
together.
One
of
the
other
things
that
we're
working
on
on
on
the
deploy
up
side
is
like
a
dev,
app
devops
adoption
dashboard.
F
I
P
I
I
I
I
P
I
I
I
We
should
be
able
to
be
scanning
cbes
across
the
cluster,
for
example,
and
being
able
to
report
on
that
kind
of
stuff.
So
we
need
some
data
scientists.
So
if
you
know
anybody
reach
out,
I
I've
knocked
on
many
doors
on
linkedin
and
looked
for
data
scientists,
we've
never
gotten
anybody
to
kind
of
embrace
it
and,
of
course,
python
developers.
I
Anybody
who
wants
to
learn
more
about
how
to
build
microservices,
because
ortilius
is
a
true
microservice
architecture
now
has
offered
some
challenges,
because
I
don't
think
the
industry
is
ready,
including
microsoft
in
their
marketplace.
So
we've
had
we've
we've
run
into
some
problems
with
that,
but
it
is.
It
is
a
true
microservice
environment,
so
anybody
who
wants
to
be
part
of
microservice
team
and
learn
that
and
have
already
already
has
like,
go
or
python
or
even
js,
we're
looking
for
them.
P
I
H
M
F
Guarantee
that
that's
not
me
I've,
I
try,
but
I
fail
I
can.
I
can
do
do
the
technical
stuff,
but
yeah
kirsch
is
definitely
right
that
if
we
had
somebody
that
would
be
able
to
you
know,
look
at
the
issues,
help
figure
out
how
to
group
them
together
how
we
can
get
some
focus
on
it.
I
think
that
would
be
a
huge
help
to
get
some
fast
coding
done.
I
Well,
we're
planning
on
trying
to
have
dinner
with
with
brian
and
marky
jackson
next
week,
so
maybe
we
can
recruit
marky
to
come
back
because
he
is
an
excellent
project
manager.
I
know
that
he's
gotten
other
things
going,
but
man
it'd
be
great
to
have
him.
Take
a
look
at
some
of
our
stuff,
we'll
we'll
shoot
for
that
any
brian.
Do
you
think
we
have
any
chance.
I
It
okay!
Well
that
takes
us
to
the
end
of
this
first
section
of
beer
and
donuts.
I
hope
you
all
enjoyed
this
live
version
of
it
and
congratulations
to
everybody
who
got
a
badge
proud
of
you
all
and
thank
you
for
all
the
hard
work
for
those
of
you
who
are
climbing
the
ladder
and
getting
into
those
legend
and
the
silver
levels.
It's
it's
not
an
easy
task
to
do.
We
do
have
it
set
up.
We
have
to
do
some
work.
I
I
D
B
D
A
A
A
E
18
houston,
we
have
a
problem.
In
august,
2014
social
media
was
bombarded
with
photos
of
a
ufo
hovering
over
houston
texas,
taken
from
different
spots
around
the
area.
The
ufo
seemingly
consisted
of
several
lights,
forming
a
ring
at
the
center.
You
can
make
out
a
single
orb
as
if
the
other
circular
lights
are
revolving
around
it.
The
ufo
almost
shares
a
resemblance
to
saturn.
Although
some
experts
have
theorized
there's
nothing
otherworldly
about
it.
Fletcher
gray
of
the
mutual
ufo
network
deduced
it
likely
stemmed
from
nearby
highway
lights.
E
It's
also
worth
noting
that
houston
endured
a
thunder
and
lightning
storm
that
night,
which
may
have
contributed
still.
How
fitting
would
it
be
if
alien
life
visited
space
city
number
17,
the
kumbhorgas
ufo
video
in
2007,
a
turkish
night
guard
named
yachin
yanman
working
in
istanbul's
holiday
village,
noticed
strange
activity
in
the
sky
and
started
filming.
He
kept
his
eyes
on
the
skies
throughout
the
next
few
years.
E
Recording
a
treasure
trove
of
ufo
footage,
the
ufo
that
repeatedly
pops
up
in
these
videos
certainly
looks
like
a
spacecraft
even
calling
to
mind
the
ones
from
war
of
the
worlds
upon
further
inspection.
Some
claim
that
you
can
spot
two
alien
heads
peeping
out
of
what
appears
to
be
a
window
or
a
door.
Our
eyes
may
be
deceiving
us,
but
ufologist
nick
pope
described
yaman's
findings.
As
quote
a
turning
point
for
turkish
ufo
studies.
Adding
quote
the
authorities
can
no
longer
turn
a
blind
eye
to
this
phenomenon:
number
16.
new
mexico
1957..
E
Ever
since
the
roswell
ufo
incident
in
1947
new
mexico
has
been
a
hot
spot
for
alleged
alien
activity.
Almost
10
years
after
the
historic
sighting
new
mexico,
local
ella
louise
fortune
had
another
close
encounter
of
sorts
cruising
down
highway
54
on
october
16th
1957,
the
nurse
took
a
photo
of
a
bright
white
flying
disc,
the
ufo
reportedly
hovered
around
the
holloman
air
development
center
for
15
minutes.
That
said,
the
fact
this
occurred
near
an
air
force
base
might
provide
a
logical
explanation.
E
Even
after
the
aerial
phenomena,
research
organization
studied
the
imagery,
though
nobody
could
come
up
with
a
conclusive
answer:
number
15,
the
lubbock
lights
in
august
1951,
three
texas,
technological
college
professors
noticed
somewhere
between
20
and
30
lights,
shimmering
in
the
sky.
Five
days
later,
texas
tech,
freshman
carl
hart
jr
gazed
out
his
bedroom
window
to
find
a
cluster
of
lights,
forming
a
v-shape
hart
managed
to
take
five
photos
of
the
lights
getting
them
published
in
various
newspapers
and
life
magazine.
E
This
caught
the
attention
of
the
air
force,
which
launched
an
investigation
at
first
they
believed
the
lubbock
lights
were
really
plovers.
The
air
force
eventually
announced
that
it
wasn't
a
bird
or
a
spaceship,
but
a
quote
easily
explainable
natural
phenomenon
without
unveiling
what
the
phenomenon
actually
was.
Well,
that's
not
suspicious
at
all
number
14
salem
massachusetts
1952.,
as
if
being
the
site
of
infamous
witch
trials
wasn't
bad
enough.
Salem
was
also
invaded
by
aliens
at
one
point:
okay,
maybe
we're
exaggerating
just
a
tad,
but
this
was
definitely
a
weird
occurrence.
E
On
august
3rd
1952
a
u.s
coast
guard
looked
outside
a
lab
to
find
four
large
vibrant
lights
up
above
the
21
year,
old
guard
snapped
a
photo
through
a
window,
and
people
have
been
making
calculated
guesses
as
to
the
exact
nature
of
these
objects.
Ever
since
flying
saucers,
a
witch's
spell
lamp
lights.
In
any
case,
salem
just
got
even
eerier
number
13
iss
light
beam
in
2016.
E
A
video
surfaced
on
youtube
from
nasa's
live
feed
of
the
international
space
station,
seemingly
showing
an
object,
making
atmospheric
entry.
The
feed
was
then
suspiciously
cut
off,
although
nasa
claims
that
this
was
due
to
technical
difficulties
and
the
object
was
likely
debris
or
lights
from
earth.
However,
a
subsequent
video
from
the
same
feed
showed
what
appeared
to
be
a
similar
object.
Departing
earth,
followed
by
a
bright
golden
beam
of
light,
is.
U
E
E
V
E
Ufo
circles,
though,
the
mission
is
best
remembered
for
footage
captured
on
september
15th,
while
not
easy
to
make
out
the
video
shows
objects
zooming
by
and
bright
lights
flashing
in
earth's
orbit.
According
to
nasa,
these
were
ice
particles
responding
to
the
engine
jets,
astronomer
phil
plate
has
backed
up
these
claims,
but
we
gotta
admit
the
believer
in
us
likes
to
wonder
it's
not
the
only
space
shuttle
mission
to
have
caught
ufologists
eyes
in
1996
footage
from
sts-75
seemed
to
show
objects
buzzing
around
the
broken
tether
of
a
drifting
satellite
debris
or
curious
visitors.
E
E
W
E
Traffic
control
specialists
from
wellington
tracked
the
lights
which
an
australian
television
crew
then
recorded
in
color.
The
tv
crew
came
along
for
the
cargo
plane's
next
flight
from
wellington
back
to
christchurch.
Shortly
after
takeoff,
the
crew
captured
footage
of
a
giant
illuminated
orb
new
zealand's
ministry
of
defense
has
provided
several
possible
explanations,
including
lights
from
boats,
cars
or
venus,
but
alternative
explanations.
X
E
The
black
knight
satellite,
the
black
knight
satellite,
remains
one
of
the
most
famous
conspiracy
theories
in
ufo
circles.
It's
said
that
this
mysterious
satellite
has
been
orbiting
earth
for
13
000
years
in
1954,
ufo
investigator
donald
kehoe
claimed
that
the
air
force
had
discovered
two
artificial
satellites,
despite
the
fact
that
such
technology
did
not
exist
at
the
time,
it
would
be
another.
Three
years
until
we
launched
the
first
artificial
satellite
sputnik,
regardless
various
newspapers
like
the
st
louis
post
dispatch
and
san
francisco
examiner,
picked
up
the
story.
E
The
black
knight
regained
interest
in
1998
when
nasa
released
this
photo
from
the
sts-88
mission.
While
most
would
agree,
it
was
space
debris.
Others
are
not
letting
go
of
their
black
knight
theory,
number,
nine,
the
phoenix
lights,
the
phoenix
lights
have
inspired
a
documentary
and
multiple
horror
movies,
but
nobody
can
say
for
sure
what
happened
on
march,
13th
1997.
E
Y
E
This
incident
can
be
broken
into
two
phases.
First,
a
v-shaped
formation
was
seen
flying
over
phoenix,
although
little
footage
exists
of
this
event,
and
the
footage
we
do
have
is
low
quality,
there's
more
documentation
of
the
second
event,
which
saw
five
circular
lights
floating
in
the
night
sky.
There
were
many
events.
E
30
the
next
morning,
even
with
numerous
photographs,
videos
and
eyewitness
accounts,
though
a
giant
question
mark,
continues
to
hover
over
phoenix
while
the
u.s
air
force
chalked
the
lights
up
to
military
flares.
Many
have
argued
against
these
claims
and
even
arizona
governor
fife
symington
described
what
he
saw,
as
quote
otherworldly.
Well,.
L
E
A
little
speck
can
certainly
stir
up
a
lot
of
speculation
in
2017.
The
chilean
government
agency,
tasked
with
examining
ufo
sightings,
released
footage
of
a
flying
object
that
defied
explanation.
The
footage
which
had
been
classified
for
almost
three
years
was
taken
by
the
chilean
navy
from
a
helicopter.
During
the
day,
the
pilot
failed
to
make
contact
with
the
object
which
moved
like
another
helicopter
even
more
curious.
The
object
didn't
pop
up
on
air
traffic
control
radar
in.
L
E
L
E
Seven,
the
battle
of
los
angeles.
This
incident
took
place
in
february
of
1942
three
months
after
the
japanese
bombing
of
pearl
harbor
receiving
word
of
another
possible
attack.
Air
raid
sirens
went
off
around
los
angeles
county
and
the
area
endured
a
blackout
throughout
the
night.
1400
shells
were
fired
into
the
air.
Five
people
died
as
a
result,
and
property
damage
was
significant,
although
it
reportedly
turned
out
to
be
a
false
alarm.
The
la
times
published
a
photo
of
the
air
raid
with
searchlights
directed
at
what
looked
like
a
spaceship.
While
the
photo
was
touched
up.
E
E
Number
six
mexican
air
force
video
on
march
5th
2004,
the
mexican
air
force
recorded
footage
of
11
ufos
at
11
500
feet
above
southern
campeche
state
surrounding
a
military
jet.
These
lights
were
detected
during
a
routine
search
for
drug
traffickers.
Jets
pursued
the
ufos
but
eventually
gave
up
and
the
objects
disappeared.
While
some
believe
this
was
the
work
of
flares
explanations,
also
ranged
from
ball
lightning
to
a
meteorite
deteriorating
in
earth's
atmosphere.
Whatever
these
objects
were.
H
A
A
A
L
E
A
little
speck
can
certainly
stir
up
a
lot
of
speculation
in
2017.
The
chilean
government
agency,
tasked
with
examining
ufo
sightings,
released
footage
of
a
flying
object
that
defied
explanation.
The
footage
which
had
been
classified
for
almost
three
years
was
taken
by
the
chilean
navy
from
a
helicopter.
During
the
day,
the
pilot
failed
to
make
contact
with
the
object
which
moved
like
another
helicopter
even
more
curious.
The
object
didn't
pop
up
on
air
traffic
control
radar
in.
L
E
L
E
5,
the
mexican
air
force
video
on
march
5th
2004,
the
mexican
air
force
recorded
footage
of
11
ufos
at
11
500
feet
above
southern
campeche
state
surrounding
a
military
jet.
These
lights
were
detected
during
a
routine
search
for
drug
traffickers.
Jets
pursued
the
ufos
but
eventually
gave
up
and
the
objects
disappeared,
while
some
believe
this
was
the
work
of
flares
explanations
also
ranged
from
ball
lightning
to
a
meteorite
deteriorating
in
earth's
atmosphere.
Whatever
these
objects
were
infrared
equipment
operator,
lieutenant
mario
adrian
vasquez
is
convinced
that
they
were
quote
completely
real
pilot.
E
E
Even
by
ufo
standards,
this
one's
perplexing
it
all
started
in
april
2013
at
the
rafael
hernandez
airport,
located
in
aguadilla
puerto
rico,
a
video
was
taken
of
an
unknown
object
swiftly
flying
over
land
and
then
seeming
to
submerge
underwater.
After
doing
so
multiple
times,
the
object
appears
to
split
in
two
supposedly.
The
us
department
of
homeland
security
tried
to
keep
this
under
wraps,
but
the
video
was
eventually
leaked
by
an
anonymous
whistleblower.
A
group
known
as
the
scientific
coalition
for
ufology
was
responsible
for
posting
the
footage
online.
E
E
E
Released
under
the
file
name
go
fast.
This
video
was
taken
over
the
east
coast
in
january
2015
by
an
fa-18f
super
hornet
during
the
uss
theodore
roosevelt
ufo
incidents,
the
footage
was
captured
using
raytheon's
advanced
targeting
forward-looking
infrared,
pod
or
atflier,
and
just
as
entertaining
as
the
footage
itself
is
the
fighter
pilot's
comments.
While
the
audio
is
somewhat
hard
to
understand,
you
can
certainly
grasp
the
astonishment
they
experience
while
watching
the
object.
Oh,
my
gosh
dude.
V
E
Also
released
by
the
pentagon,
flier
1
was
filmed
on
november
14
2004
around
the
san
diego
coastline
like
go
fast.
This
video
was
also
taken
aboard
a
super
hornet
using
at
flear.
The
footage
was
captured
during
the
uss
nimitz
ufo
incident,
in
which
the
navy
had
a
radar
visual
encounter.
The
video
centers
on.
A
A
M
M
M
M
M
M
M
M
M
A
AA
To
my
talk,
what
should
you
know
to
contribute
to
hoteliers
so
bit
about
hoteliers
itself?
What
is
rebellious
and
what
is
standing
for
for
delias
is
the
open
source
project.
Hoteliers
is
a
microservices
catalog
that
govern
your
micro
services,
supply
chain,
tracking
supply
chain,
tracking
versions,
blocks
radius,
inventory,
s4
sves
and
the
team
that
supports
them,
providing
a
product
proactive
view
of
your
micro
service
application
and
it
changes
over
time.
Orterius
is
an
indicating
project
under
the
corners
of
the
cd
foundation
and
the
part
of
the
linux
foundation
project.
AA
So
what
should
you
know
to
contribute
your
interest
in
less
than
a
10
minute
guy,
before
I
tell
you
the
procedure
and
processes
involved
in
in
contributing
to
ortalia's
kit
of
repositories
and
what
are
the
different
way
you
can
contribute
to
hotel?
Yes,
but
I
think
that's
concept
is
really
important
for
me
to
explain
why
should
you
start
contributing
to
orterius
open
source
project,
so
I
did
get
back
in
time
and
things
that
motivated
me
to
be
a
part
of
doterra's
contributor.
Is
this
term?
AA
You
can
learn
anything,
but
you
can
be
remembered
for
what
you
have
shared
so
now,
who
I
am,
who
is
who
you
are
listening
to?
My
name
is
simon.
I
am
a
developer
advocate
at
bank
clouds,
cloud
native
slumber,
co-founder
cdf,
hello,
today's
ambassador,
and,
if
you
want
to,
if
you
want
to
touch
stay
in
touch
with
me
here,
the
twitter
unlimited
profile
for
me
say.
K
AA
And
stay
connected,
so
let's
share
my
journey
go
back
in
time
at
2020
march,
when
the
pandemic
starts,
I
see
the
empty
doors.
I
see
the
empty
office,
I
see
the
gun
for
humpty
conferences
and
that
is
really
really
get
me
isolated
and
completely
depressed.
What
should
I
do
now?
The
reason
I'm
depressed
is
because
my
learning
cycle
great
because
my
self
learning
circle
is
started,
engaging
the
people
like
what
you
are
learning
today
and
I
want
to
explore
from
other
people
what
they
are
learning.
AA
I
guess
it's
june
2020
when
I
meet
tracy
ragan
for
the
hoteliers
community,
because
we
are
joined
because
I'm
joining
the
conference
city
gone
virtually
and
then
we
connected
somehow-
and
he
introduced
me
to
the
hoteliers
open
source
community.
So
I
landed
in
the
website
and
then
I
joined
the
discord
server
and
the
people
are
really
really
helping
me.
I
didn't
know
my
learning
cycle.
I
tried
to
resume
my
learning
cycle.
AA
AA
I
need
help
with
this
technology
as
the
time
for
aggressive
and
the
community
helped
me
a
lot
that
I'm
able
to
explain
it
to
the
other,
the
things
that
I'm
learning
today,
that
is
because
of
the
community
sport
that
is
because
of
the
individual
empowerness
by
the
community,
I'm
really
really
lucky
to
have
part
of
that
wonderful
community.
Thank
you
sergio.
Thank
you,
sasha!
Thank
you,
steve,
brad
and
tracy
for
helping
me
in
helping
me
in
my
in
my
journey
in
the
learning
the
journey
of
microservices.
AA
So
now
I
think
you
kind
of
motivated
like
I
try
to
motivate
you
why
you
should
contribute.
I
sh
share
my
knowledge
why
I
started:
let's
put
it
into
the
open
source
project
and
after
this
a
few
step,
I
explained
what
I
get
for
learning
with
open
source
community,
but
now
I
think
you
should
familiar.
Why
should
you
start
contributing
now?
There
are
some
ways
you
can
start
contributing
to
your
daily
life.
You
can
start
by
coding.
AA
You
can
start
by
doing
some
other
stuff
like
if
you
are,
if
you're,
not
good
at
coder
but
you're,
a
good
graphic
designer.
You
can
join
us
our
team
and
you
can
start
contributing
on
that
part.
If
you're,
not
a
good
database
administrator
or
you
are
at
the
hitops
or
you
are
the
let's
say
the
ops
engineer,
you
can
start
contributing
with
those
on
those
specialized
field.
We
have,
though,
we
need
this
kind
of
person
in
our.
AA
AA
I
our
discord
service
always
available
for
everyone
to
ask
questions,
give
us
a
feedback
and
start
conversation
and
and
tell
us
what
are
the
different
ways
you
can
contribute
to
the
oculus
project.
We
will
happy
to
help
you,
but
in
terms
of
the
coding
there
are
some
guidelines
that
we
have
conduct
that
we
have
prepared
for
the
people
who
are
a
beginner
to
start
contributing
to
our
dailies
project.
So
now
I'll
stop
here
and
resume
the
talks.
AA
So
now
you
can
go
to
the
getup.com
hotelier,
slash,
hoteliers
and
first,
if
you
like
our
stuff,
give
us
a
star
and
then
go
read
the
documentation
and
tell-
and
you
can
see
the
various
contributors
are
listed
here.
You
can
talk
to
them
every
time
in
our
hotelies
discord
server,
but
that's
documentation
is
our
failures.
Project
is
residing
on.
You
can
go
to
the
different
folder
check
to
see
what
are
the
different
image
building
mechanism.
We
are
using
how
our
tests
are,
how
power
tests
are
written,
how
our
different
type
of
procedure
are
existed.
AA
What
are
the
difference,
get
off
action
that
we
are
using
that's
all
available
here
and
when
you
submit
a
pull
request
of
start
contributing
to
retaliators
committed
project,
we
will
add
you
to
the
dip
repository
like
these
are
the
people
who
are
managing
the
cd
environment,
helping
the
same
productivity.
These
are
the
people
responsible
for
that
there
are
some
data
science
and
visualization.
AA
These
people
have
are
responsible
for
that.
We
have
deployment
integrity,
integration.
You
can
look
at
the
see.
What
are
the
different
type
of
stool
that
we
are
using
as
of
today
and
what
are
the
different
contributors
that
are
responsible
for
the
managing
those
tools?
You
can
look
at
the
marketplace
and
domains
who
are
responsible,
ui,
ux,
testing,
documentation
and
architecture,
the
development
all
these
people
are
available
for
daystar
and
now,
if
you're
part
of
the
project
management
team,
you
just
give
us
a
full
request.
AA
We
add
you
here
on
tracyrecon
and
nato's
chair
on
below
that
list.
Is
that
or
if
you
want
to
be
a
part
of
development
team,
we
will
add
you
to
this
this
list
or
on
any
of
whichever
field
you
are
in.
We
try
to
add
you
in
the
prepared
field,
so
this
is
a
repository.
You
have
to
check
check
up
first,
what
are
the
different
ways?
You
contribute,
what
is
your
talia
setup
repository
in,
and
that
is
the
first
procedure
in
contributing
the
ortegas
project.
AA
Now,
step
number
two:
you
go
to
the
hoteliers,
slash
dot,
io,
slash
blog
on
your
tillius
journey
blog
and
that
is
written
by
the
wonderful
community
member.
We
have
siddharth
and
he
is
put
pulled
together,
a
wonderful
information,
because
when
you
look
at
the
hoteliers
get
up
before
get
up,
we
have
so
many
other
different
repositories
also
existed.
How
you
should
explore
what
repositories
for
me
and
how
you
should
start
which
contribute
which
deposits
to
start
contributing
to.
We
have
this
information
available
on
our
youtube
channel.
You
just
go
through
it.
It's
a
simple!
AA
I
think
three
minute
old
video
will
tell
you
all
the
the
positivity
we
have
and
what
they
are
doing
and
what
part
of
it
so
siddharth.
Thank
you
very
much
for
pulling
this
together
and
you
can
also
stay
in
touch
with
our
joining
our
meetup
or
community.
Joining
the
deportaious
google
group
and
the
scorcher.
AA
Now
we
look
at
the
two
different
ways:
go
to
the
github
repository
check.
The
different
repository
see
all
the
different
repositories
we
have
by
looking
at
this
block,
and
now
the
third
step
is
go
to
the
hoteliers
contributor
guard.
When
you
go
to
it.
They're
also
welcome
things.
You
should
know:
community
membership
developer
resources,
how
to
tips
full
requests
to
receive
a
glass
eclipse,
ide
setup,
all
things
available,
let's
say:
go
to
the
developer
resources.
So
if
you
give
me
the
visual
studio
setup
here
that
you
need
to
have
and
also
the
postgresql.
AA
Postgres
and
also
the
docker
helm
and
all
the
things
like
where
the
people
who
variable
the
images
from
so
these
are
all
things
available.
You
just
go
through
it
and
I
think
it
takes
you
two
or
three
minutes
to
go
through
all
this
stuff
and
then
you're
able
to
contribute
your
first
full
request
through
today's
depository.
When
you
go
pull
when
you
submit
the
pull
request,
it
is
up,
then,
when
you
start,
you
are
part
of
the
continuous
repository
or
contributor,
and
then
we
will
add
you
as
a
number
as
well.
AA
So
these
are
the
three
safe
remember
to
go
to
the
tvs,
github
dot
com
check,
to
see
the
siddharth
blog
on
how
how
you
should
start
contributing,
and
the
third
step
is,
go
to
the
contributor
guide
and
check
to
see
what
are
the
different
tools
and
the
developer
tools
and
what
a
different
visual
studio,
what
the
things
we
are
using.
So
these
are
the
things
that
you
all
needed
in
order
to
start
contributing.
AA
Now
we
look
at
everything
like
how
you
should
start
contributing
as
it
well
as
a
coder
or
any
other
way.
So
now
the
last
question
like
what
should
I
share
my
job
like
what
I
get
for
contributing
to
the
open
source
hoteliers
project?
So
I
have
censored
my
cloud
native
vocabulary.
I
have
gained
local
practice.
I
have
removed
fear
and
gain
love
while
talking
in
public.
I
have
found
the
knowledge
how
people
talk
in
public.
I
have
found
the
knowledge
how
other
people
learn
kubernetes
and
other
cloud
native
and
microservice
technologies.
AA
Every
day
I
have
found
the
knowledge
how
other
people
build
their
products
on
top
of
kubernetes.
I
have
fine
success
stories.
I'm
able
to
give
a
speech
at
kubecon,
valencia.
I
am
now
a
cdf
and
rotelius
ambassador
and
I
am
a
member
of
a
community
where
I
every
time
I
need
help,
I'm
closer
to
experts
and
people
who
are
easily
approachable
and
their
passion
is
to
help
further
what
else
I
needed.
So
these
are
the
things
I
get
from
contributing
to
the
hoteliers
open
source
project.
AA
So
at
last
I
am
resume
I'm
able
to
resume
my
cuban
learning
cycle.
I
try
I'm
everyday
trying
to
engage
with
people
what
you
are
learning
every
day
and
I
find
the
things
that
they're
learning
I
drive
exploring
and
then
I
strive
to
explore.
I
I
try
to
explain
it
to
other
and
then
share
the
details
with
the
hortelius
slack
discord
server
and
then
I
drive
will
upgrade
the
knowledge.
AA
What
what
I
learned
from
this
exploration
and
what
I
learned
from
this
another
open
source
or
another
technology,
and
then
I
try
to
evaluate
my
stuff,
like
people
asking
questions
like
what
how
this
is
different
from
other.
That's
part
of
the
evaluation
that
I
also
get
from
talking
to
people
on
discord,
servers
in
the
hoteliers
community.
So
I'm
able
to
resume
my
knowledge
what
else
I'm
going
to
need
it.
AA
So
remember
that
I
said
it
on
the
first
or
third
slide
but
motivated
me,
because
I
I
hope,
that's
the
term
motivated
you
as
well,
so
you
can
learn
anything,
but
you
can
be
remembered
for
what
you
have
shared.
So,
thank
you.
Everyone
for
listening
to
my
job
now
for
the
extra
resources
go
to
the
hoteliers.io,
go
to
the
github.githubgithub.coms.
AA
And
join
our
and
follow
us
on
our
twitter
handle
or
tvs
os
and
join
our
and
stay
connected
with
us
on
the
retailers
linkedin
page
as
well,
and
if
so,
if
you
want
to
say
hi
to
me,
go
these
are
the
resources.
These
are
the
my
profile
on
twitter
and
linkedin
available
for
you.
I
hope
to
see
you
again
in
the
future
in
another
microservices
visionary.
Thank
you,
everyone
for
listening
to
my
talk
and
thank
you.
Everyone
for
joining
into
microservices,
ortelius
micro
services,
visionary
2022.,
stay
safe,
stay,
healthy,
bye,
bye,
everyone.
T
Hi
everyone
good
morning,
good
afternoon,
good
evening
to
people
from
different
parts
of
the
world,
welcome
everyone
to
artelia's
visionaries
2022.
My
name
is
kirsh
and
for
the
next
10
minutes
we'll
be
discussing
three
of
the
famous
design
patterns
that
might
help
you
in
designing
your
microservice
based
applications.
T
So
if
you're
developing
micro
service
applications,
so
audilius
is
your
friend
artelis
is
basically
a
microservice
catalog
tool
that
that
not
only
cracks
your
different
components,
different
microservices,
but
also
consulted
a
lot
of
useful
information
like
what
version
is
deployed.
What
is
the
stable
version?
T
T
Few
words
about
myself,
I'm
a
software
engineer
at
cisco,
india.
I
like
to
create
a
lot
of
services
using
different
cloud
platforms,
let
it
be
like
azure
or
gcp,
and
I
also
like
to
contribute
to
the
open
source
community.
I
like
collaborating
and
working
with
passionate
developers.
That
is
where
I
join
rtls
and
if
you
are
looking
for
the
same
hotel
is
the
best
place.
T
These
are
the
content
that
we'll
be
looking
at
in
the
next
10
minutes,
we'll
see
how
we
can
migrate
the
monolith
to
your
micro
service
based
architecture,
we'll
for
that
we'll
look
at
decomposition
patterns
to
manage
data
in
a
distributed
ecosystem.
We'll
look
at
three
of
the
design
patterns
like
sagar
design
patterns,
cqrs
design
pattern,
and
apart
from
that,
we'll
look
at
a
few
of
the
reliabilities
standpoint
itself.
T
You're
asked
to
convert
a
soa
architecture
based
application.
So
how
would
you
you
know?
How
would
you
what
will
be
your
think
thought
process?
So
what
we
can
do?
We
can
either
decompose
our
application
based
on
the
business
capability
that
has
or
what
we
can
do.
We
can
decompose
our
application
based
on
subdomains,
so
just
to
add
little
more
details,
so
decomposition
by
business
capabilities
means
identifying
the
different
layers
of
your
applications
that
are
responsible
for
different.
T
T
So
we
we
use
domain-driven
design
to
create
a
microservices
so
that
that
has
like.
You
need
a
lot
of
understanding
of
the
product
itself,
because
you
have
to
identify
like
which
components
you
can.
You
know
segregate
into
one
component,
and
so
let
me
show
you
some
figures:
okay,
so,
as
you
can
see
decomposed
by
business
capabilities,
so
it
is
fairly
straightforward.
T
So
what
we
can
do,
we
can
identify
those
and
we
can
isolate
them
and
create
a
different
service
and
standard
service
and
deploy
them
as
a
microsoft,
while
in
decomposed
by
subdomain,
we
have
to
identify
like
like
if
this
service,
if
this
api,
would
go
into
a
product
catalog
service,
or
that
you
know
so,
we
should
decide
in
delivery
service
or
something
so
these
kind
of
challenges
are
there.
So
that
takes
like
a
lot
of
and
throw
meetings
with
different
folks
to
identify
that.
T
Apart
from
that,
there
are
few
of
the
other
design
patterns
that
we
see
nowadays,
so
nowadays
what
we
see
so
we
identify
like
a
what
all
services
can
be.
You
know
self-contained
into
one
service,
so
that
is
one
design
pattern
that
you
can
use
the
other
one
is
if
you
are
creating
your
application
from
scratch,
so
I
have
seen
like
a
lot
of
people.
They
create
a
different
team
as
per
services,
so
there
will
be
one
team
that
will
be
only
concerned
with
the
data
call
them
as
a
data
team.
T
T
So
there
are.
There
is
a
famous
design
button
to
solve
this
distributed
transaction
problem
in
microservice.
That
is
called
saga
design
button,
and
we
can,
you
know,
tweak
the
saga
design
pattern
in,
like
whatever
space
suits
you,
but
the
overall.
The
base
architecture
will
will
be
very
similar
to
this.
So
first,
there
are
like
two
approaches
to
saga.
One
of
them
is
choreography
based
approach,
so
in
choreography
based
approach,
your
request
will
be
propagated
to
the
to
the
different
services
and
they
will
be
again
propagated
in
the
reverse
order.
T
T
The
second
approach
is
orchestration
based,
so
in
that
case,
what
we,
what
we
do,
we
create
an
orchestration
layer
that
is
responsible
for
orchestrating,
so
that
will
be,
you
know,
orchestrating
different
threads
and,
let's
suppose,
let's
see
this
diagram.
So
if
you
want
to
create
an
order,
so
what
you
need?
You
need
some
customer
information.
T
You
need
like
payment
information
or
even
you
need
inventory
information
that
the
product
is
available
or
not.
So
there
we
have
like
orchestration,
which
will
post
a
event.
So
here
we
have
used
a
message
broker,
so
it
is
posting
even
to
you
know,
which
will
be
consumed
eventually
by
customer
service
and
customer
service
based
on
that
event
will
return
some
other
event
to
the
other
topic,
which
is
a
reply
channel
on
the
reply
channel
and
this
create
order.
T
Module
will
consume
that
event
and
based
on
the
event
that
he
has
consumed,
he
will
identify
if
he
has
to
create
order
or
not.
So,
let's
suppose
there
if
he
has
got
a
success
from
a
customer
okay.
So
at
the
later
point
of
time
there
will
be
another
module
that
will
be
so
if
the
orchestrator
will
again
always
state
a
method
to
the
to
a
different
topic,
which
is,
let's
say,
a
payment
module,
and
let's
say
at
that
time,
the
payment
got
paid.
T
So
if
the
payment
got
failed,
the
eventually
the
output
would
be
the
eventual.
The
ultimate
response
would
be
a
fail
in
that
case.
So
this
is
how
we
maintain
the
orchestration
layer
and
in
some
cases
we
also
create
a
additional
layer
which
is
called
a
state
machine
so
which,
which
has
like,
which
maintains
a
state
for
every
request.
So
every
so,
let's
say
if
you
want
to
create
an
order,
so
order
can
have
like
that
order.
Can
you
know
generate
a
different
methods,
different?
T
Okay,
so
there
is
another
design
pattern
that
you
can
use,
alternatively,
to
sega
design
pattern
which
is
called
cqrs.
So
what
problem
we're
solving
here
in
the
cqrs
is:
let's
suppose
you
want
to
you
know
you
want
to
implement
a
query
that
received
data
from
multiple
services,
so
we
know
like
if
there
are
four
services
and
if
you
are
making
a
4
db,
calls
that
will
be
very
much
expensive
because
if
you
are
developing
a
large
scale,
applications
that
will
be
converted
to
1000
or
millions.
T
T
So
in
that
case
you
only
have
to
query
that
view
database
that
you
have
created-
and
in
that
case
you
decrease
number
of
queries
that
you
make
to
your
applications.
So
just
creating
a
view.
Database
is
not
a
very,
I
would
say
popular
method,
but
similar
kind
of
tweaks.
I've
seen
people
making
their
application
making
their
product
to
reduce
the
db
calls.
T
Okay,
coming
to
the
reliability
of
perspective,
so,
let's
suppose
you're
writing
a
code.
Okay.
So
what
happens
if,
at
some
point,
the
other
service
is
not
available,
or
let's
say
if
there
is
a
service,
a
which
has
to
publish
an
event
to
service
b
and
service
b
is
not
available.
So
at
that
point
of
time
what
should
be
the
flow
of
the
execution?
T
T
So
these
are
the
scenarios
when
we
consider
when
there
is
a
when
we
identify
like
the
other
service,
is
not
available.
So
let's
say
if
you
want
to
publish
a
event,
but
the
kafka
topic
is
not
available.
So
what
do
you
have
to
do
so?
You
can
implement
a
fallback
method
saying
there
is
a
different
topic.
T
Let's
say
error
topic,
so
you
can,
you
know,
push
those
events
into
into
those
cues
or
let's
say,
if
you're
not
able
to
make
connection
so
service
b
is
down
so
you're
not
able
to
consume
services
that
are
written
in
b,
my
backend
service.
So
in
that
case
you
can
write
a
fallback
scenario
that
will
return
some
generic
response
so
and
you
can
also
maintain
some
kind
of
record
record
for
that
and
you
can
process
that
afterwards.
T
So
in
that
case,
whenever
we
identify
like
there
are
some
services
which
are
not
responding
so
on
this
second
record,
the
implementation
that
we
write
will
be
will
be
set
on
and
in
that
cases,
whatever
request
it
will
receive
in
that
point
of
time
will
be
handled
by
a
fallback
scenario.
The
fallback
method
that
you
that
you
write
and
after
after
you
know
a
certain
point
of
time.
T
Let's
say
if
you
have
behind
some
time
off
for
the
circuit
breakers
after
that
timeout
that
circuit
breaker
will
will
be
off
and
then
again
it
will.
You
know
take
a
few
requests
and
see
if,
if
you
know
your
application
is
able
to
consume
the
services
of
the
other,
if
not,
then
it
will
again
go
to
the
on
state
and
all
the
requests
will
be
handled
by
fallback.
T
Y
T
T
B
Hello,
everybody
welcome
to
our
television
artist
2022.
Today
we
are
going
to
talk
about
team
2
topologies,
but
this
version
is
like
apply
in
the
field,
so
this
is
experience
from
a
real
project,
so
I
hope
you
enjoy
it.
This
is
mainly
what
is
tim
to
police.
Try
to
do
so
is
something
that
is
in
the
mind
of
a
lot
of
people.
We
are
going
to
add
a
little
information
of
what
happened
when
you
are
trying
to
use
it
right.
B
B
S
B
We
are
going
to
start
so
this
is
a
an
attack
for
an
hour,
so
we
are
going
to
do
it
today
in
a
light
tall
mode.
So
hang
on,
we
are
going
to
go
a
little
fast,
but
I
have,
I
hope
you
enjoyed
it.
So
what
is
deep
topologies?
This
is
mainly
what
is
team
topologies.
There
is
an
official
page.
There
is
a
a
whole
learning
process,
guidance
and
studies
about
it.
So
there
is
the
link,
you
can
watch
it
all
so,
but
this
is
like
the
main
ideas,
so
it
it's
a.
B
B
But
okay,
that's
like
the
idea.
That's
the
theory!
That's
like
this
side
that
tell
me
what
I
can
learn.
What
how
I
can
prepare.
So,
let's
go
to
the
field
and
try
to
put
this
and
make
this
happen.
Okay,
so
the
expectation
is
like
you're
going
to
your
organization,
you're
going
to
say:
oh
okay,
this
is
like
my
instructor.
This
is
like
the
the
most
common
police
that
I
have
the
the
interaction
between
them.
B
B
If
you
are
trying
to
deliver
some
workloads,
you're-
probably
going
to
depend
from
networking
from
storage
for
platforms
infrastructure.
So
but
what
usually
happens
is
that
is
like
your
team,
developing
something
with
maybe
a
counterpart
from
from
other
areas.
At
least
one
that
probably
is
going
to
talk
with
a
lot
of
people
will
try
to
do
it
and
after
that,
you're,
probably
just
going
to
have
a
a
really
nice
interaction
with
some
ticket
platform,
or
something
like
that.
B
So
I'm
trying
to
say
that
is
super
hard
on
the
on
the
beginning,
you're,
so
you
are
having
so
less
and
you
have
so
much
to
do
so.
Let's
speak
again
a
little
ahead,
so
what
we
can
do
in
the
beginning
is
pretty
much
a
project
team
that
is
not
connected
at
all
with
other
teams.
You
need
to
identify
some
stuff.
First
of
all,
you
need
to
focus
on
your
team.
Okay,
that's
the
main
thing!
B
You
need
to
optimize
what
it's
your
team
doing,
because
usually
on
an
organization
you're
not
going
to
have
like
extra
time
extra
people,
you
need
to
do
like
pretty
much
more
with
the
same.
So
you
need
to
optimize
and
optimize
it
pretty
much
developing
your
team,
making
them
giving
them
tools
to
do
his
work
faster
in
efficient
way.
So
you
can
save
time
at
the
end,
you
can
have
a
space
for
your
project
needs.
B
After
that,
you
need
to
give
continent
to
that
team,
and
usually
that
is
like
accomplished
goals.
There
is
no
team
that
is
going
to
move
forward
if
it's
not
like
giving
success
or
having
this
image
that
they
are
being
successful
in
what
they
are
doing.
And,
finally,
you
need
to
identify
what
is
like
what
is
happening
around
you,
because
you're
not
going
to
make
this
happen
just
by
yourself.
Okay,
usually
you're,
going
to
have
like
this
a
lot
of
teams
that
are
disconnected.
B
So,
if
you
you,
you
see,
all
the
x
mark
is
just
because
you're
done
having
that
interaction.
So,
first
of
all,
you
need
to
met
all
these
things
and
you
need
to
start
like
making
connection
a
way
to
talk
consistently
have
communication
with
these
teams.
You
need
to
change
a
lot
of
aspect
of
the
culture.
Here
is
a
little
shortlist
for
this,
but
it's
longer
than
that,
but
this
is
a
a
way
resume
of
what
you
need
to
change.
B
After
that
you
need
to
make
a
trusted
environment,
usually
in
organization
you're
going
to
discuss,
who
is
makes
more
sense.
Who
is
has
more
knowledge,
but
I
I
recommend
you
always
work
in
in
facts.
Right
always
do
something
look
like
give
something
that
is,
is
working.
Try
to
avoid
conversation
about
what
things
should
do,
what
is
probably
going
to
happen,
try
to
work
what
it's
happening
itself
like
in
reality
the
logic
team.
B
B
It's
just
give
the
space
to
your
team
grow
and
your
team
is
the
one
who
is
going
to
the
is
going
to
define
what
is
the
structure?
What
is
the
interaction,
or
what
is
the
work
is
going
to
do,
is
going
to
have,
if
you
give
the,
if
you
give
them
the
space
to
grow,
okay,
give
people
achievement
like
for
for
a
person
like
recognize
themselves
when
you
they
change
something
they
do
a
good
impact
when
they
support
each
other.
When
they
give
me
opportunities,
give
rewards
you,
we
usually
do
stuff
like
giving.
B
B
So
what
we
are
having
from
this
session
this
this
session,
it
is
really
hard.
It's
a
really
hard
work
to
do.
Team,
topologies
or
work
on
your
teams,
but
remember
you
need
to
support
your
people.
People
at
the
end
are
the
people
support
people,
and
that
is
the
thing
that
is
going
to
help
you
to
build
up
structures
and
connection
okay.
B
Don't
forget
that
agility
is
about
people,
it's
not
about
technology.
Okay,
agility
is
not
software
development
itself.
It's
about
people.
Doing
that,
so
don't
forget
it,
and
at
the
end
solutions
solutions
are
implemented.
They
are
going
to
be
successful
and
makes
sense
only
if
there's
you
have
people
to
can
can
support
that
that
I
don't
know
tools
it
itself
are
not
solutions
are
just
tooling
are
just
technology.
You
need
someone
that
is.
B
Doing
a
a
a
good
work
would
work
with
that.
So
don't
forget
it.
Okay.
This
was
like
the
lining
tool.
This
is
not
how
to
like
directly
implement
team.
Topologies
is
like
all
the
tips.
You
need
to
know
to
be
sure
that
you
can
grow
in
a
in
in
team
topologies
to
achieve
team
instructor
to
achieve
interactions
to
achieve
like
a
major
state
of
your
of
your
organization.
So
don't
forget
it.
People
are
the
center,
and
this
is
like
what
you
nee
usually
need
to
focus
to
make
this
happen.
B
A
A
A
A
A
M
M
A
A
AB
So
a
brief
about
me.
Currently,
I
am
an
assistant
director
cloud
practice
at
ernest
and
young
before
that
I
used
to
lead
the
cloud
center
of
excellence
team
at
accenture.
So
what
is
the
agenda
for
today?
So
this
is
a
10
minute
lightning
talk
where
I
will
discuss
the
challenges
with
current
micro
service
adoption
across
enterprises
at
scale.
What
is
a
microservice
catalog,
how
it
can
act
as
a
solution?
AB
So
micro
services
is
in
the
market
and
it
is
the
next
big
thing,
but
at
the
same
time,
the
number
of
micro
services
can
be
insane
over
a
period
of
time
in
an
enterprise.
So
here,
if
you
see
uber
in
2018
and
netflix,
you
can
see
this
is
the
micro
service
graph,
how
many
services
and
how
complex
that
interdependencies
are
so
managing
something
like
this
at
a
enterprise
level
at
an
enterprise
scale
is
very
difficult.
AB
So
what
are
the
difficulties?
So
as
long
as
you
have
5
10,
20
30
micro
services,
it
is
still
okay,
you
can
maintain
them,
but
the
moment
you
have
more
than
30
micro
services.
It
becomes
unmanageable.
The
cracks
start
appearing
in
the
system.
Why?
Because
there
is
no
clear
ownership,
nobody
knows
who
to
contact
if
that
service
breaks.
There
is
no
easy
way
to
reach
the
consumer
of
a
service,
or
today
is
the
owner
of
a
service
to
understand
who
is
responsible
for
this
service.
AB
There
is
no
easy
way
to
access
documentation
to
get
analytical
information
about
the
microservices
and
all
of
that
and
how
to
consume
it
so,
basically
at
scale.
When
you
have
a
lot
large
number
of
micro
services,
it
becomes
very
difficult
to
manage
it.
What
are
some
of
the
difficulties?
It
is
impossible
for
a
single
person
or
a
team
to
be
aware
of
all
the
micro
services
across
the
enterprise.
Okay,
nobody
can
pinpoint
when
a
service
goes
down,
that
who
is
the
owner
of
the
service?
AB
Who
should
I
reach
out
to
get
clarity
on
that
service,
which
leads
to
delays,
there's
a
lack
of
visibility
across
an
enterprise
into
what
is
the
kind
of
micro
service
adoption
state
in
that
enterprise
which
programming
languages
are
being
used
which
micro
service
frameworks
are
being
used,
and
there
is
a
high
degree
of
duplication?
Maybe
you
and
I
both
part
of
the
same
enterprise
are
developing
the
same
microservice
same
service.
We
are
not
even
aware
of
that.
AB
So
there
is
a
lot
of
duplication
and
a
lot
of
cost
to
the
company,
because
potential
reusable
opportunities
are
being
missed.
So
overall,
when
a
devil
from
a
developer
perspective.
Also,
when
a
developer
wants
to
develop
a
service,
he
doesn't
know
if
there
is
anything
that
he
can
use
as
a
building
block
to
his
own
service,
because
there
is
no
easy
way
to
get
a
view
of
all
the
services
in
the
enterprise.
AB
So,
basically,
whereas
we
wanted
micro
services
to
be
a
catalyst
in
our
digital
transformation
journey,
it
is
actually
becoming
a
kind
of
hampering
our
journey
in
a
sense.
So
it
is
not
only
adding
technical
complexity
which
obviously
micro
services
does
at
some
level,
but
they
are
also
introducing
organizational
complexity
and
they're,
posing
a
very
serious
threat
on
how
to
scale
the
enterprise.
AB
So
what
is
the
solution?
We
understand
that
these
are
the
challenges
right,
which
makes
sense
whenever
you
are
managing
something
across
5
10,
20,
30,
40,
500,
5000,
50,
000
services.
You
need
somewhere
where
you
can
get
a
unified
view
of
the
services,
and
that
is
where
a
micro
service
catalog
comes
into
play.
It
is
basically
service
discovery,
but
for
humans
it
is
a
record
or
a
list
of
all
the
micro
services
that
an
enterprise
has
running
in
production.
What
its
service
does.
AB
It
also
contains
metadata
about
the
service
like
owner
of
the
service
service,
now
queue
of
the
service,
where
I
can't
find
observability
or
promises
charts
for
that
service.
How
do
I
operate
the
service?
How
do
I
consume
the
service
using
a
catalog?
It
is
very
easy
for
a
developer
who
is
getting
onboarded
to
see?
Okay.
These
are
the
number
of
services
that
I
have.
This
is
my
service.
This
is
how
my
service
is
dependent
on
all
of
these
services.
So
I
should
be
aware
when
these
services
go
down.
AB
I
should
design
my
monitoring
accordingly,
I
should
design
my
observability
accordingly
and
it
gives
the
enterprise
leadership
the
executive
board
a
control
over
the
micro
service
adoption
across
the
enterprise
they
can
see.
Okay
today,
30
micro
services
are
there.
In
six
months
we
have
100
micro
services.
This
is
a
year
on
year.
Growth
of
microservices
is
a
kind
of
programming
languages
used
by
the
microservices
and
all
of
the
details
they
can
get
very
easily.
AB
So
microservice
catalog
gives
you
back
that
sense
of
control,
whereas
you
were
earlier
in
a
chaos
with
hundreds
and
thousands
of
services
having
a
micro
service.
Catalog
gets
you
back
that
control
over
your
entire
state
of
the
enterprise,
and
it
helps
your
developers
adopt
the
micro
service
journey
in
a
much
more
agile
way.
AB
So
this
is
a
functional
representation
of
how
a
service
catalog
works
at
a
very
high
level.
So
the
service
teams
who
are
publishing
the
services
who
you
can
call
as
service
publisher,
they
will
publish
the
services
onto
the
enterprise
catalog.
This
can
be
automatic
via
auto
search
or
auto
service
discovery
process.
It
can
be
manual.
You
can
upload
some
metadata
and
register
your
service
to
the
micro
service.
Catalog,
a
bad
job
might
be
running
which
will
scan
all
the
services
within
my
organization
at
a
regular
interval.
AB
So
many
things
can
happen,
but
at
the
end
of
the
day,
my
service
information
needs
to
be
pushed
or
inputted
into
the
micro
service
catalog
and
the
same
hand.
On
the
other
hand,
the
micro
service
consumers
who
are
consuming
my
micro
services,
they
will
basically
use
this
micro
service
catalog,
which
is
an
enterprise-wide
entity
as
a
single
source
of
truth
for
all
the
services
in
my
enterprise
they
will
go
there
and
try
to
find
which
services
makes
sense
to
them.
AB
So
this
is
kind
of
a
model
which
service
consumers
and
service
publishers
acting
as
a
whole,
cohesive
group
group,
with
the
benefit
of
this
micro
service
catalog
and
a
micro
service
catalog,
will
end
up
acting
as
a
single
source
of
truth.
You
can
build
complex
analytics
on
top
of
the
service
catalog.
You
can
answer
questions
like
what
is
the
rate
of
growth
of
micro
services.
In
my
enterprise
over
the
last
6
to
12
months,
some
teams
can
ask
questions
like
what
does
this
service?
I
do.
AB
What
are
some
of
the
options?
Some
of
the
very
well
known
options
is
obviously
ortelius,
which
is
an
open
source
project
under
continuous
delivery
foundation.
It's
a
very
well
known
micro
service
catalog,
you
should
go
and
check
it
out.
Also
deploy
hub
is
also
a
very
good
option,
which
is
an
enterprise
grade
option
that
can
help
you
simplify
all
of
the
same
problems,
tackle
all
of
the
problems
and
much
more
benefits.
It
can
give
you
like
service
dependency
and
a
lot
of
thing
automatic
search
discovery
and
a
lot
of
things
deploy
hub
can
give
you.
AB
So
what
is
the
conclusion?
So
basically,
what
we
are
trying
to
what
I
am
trying
to
portray
here
is
that
there
is
actually
a
very
real
challenge
and
a
very
real
danger
to
the
scaling
of
your
enterprise.
If
you
are
not
able,
if
you
are
not
able
to
have
some
sort
of
a
strategy
behind
it
for
a
few
services,
it
is
okay.
But
the
moment
you
cross
that
threshold
of
30
or
40
services,
it
becomes
very
difficult,
so
you
can
start
small.
AB
If
you
start
with
this
approach,
if
you
bring
this
into
the
core
mindset
of
your
engineering
first
engineering
strategy,
just
like
api
first,
just
like
micro
service
first
cloud
first,
this
should
also
be
part
of
your
core
engineering
strategy,
and
only
then
you
can
drive
micro
service
adoption
across
your
entire
enterprise
across
hundreds
of
teams.
In
your
enterprise
questions,
please
let
me
know
if
there
are
any
questions,
I
would
love
to
answer
them
and
thank
you
so
much
for
being
a
part
of
this
session.
A
A
A
Q
Y
J
J
J
J
But
your
business
was
really
successful
and
you
have
more
customers
that
are
wanting
your
services.
Now
people
are
from
different
parts
of
the
world
and
your
company
is
changing
its
name
from
mark
id
services
to
steven
globality
services
and
you
potentially
are
going
to
have
200
customers
from
india,
asia,
u.s
and
we'll
be
talking
into
you
have
40
employees
and
they
are
divided
into
multiple
teams.
J
So
you
are
given
the
task
to
come
up
with
a
solution,
a
plan
to
scale
things
up
to
grow
your
company,
so
you
come
up
with
already
great
plan
and
that
is
to
buy
more
servers
and
hire
new
employees
set
up
a
new
office
and
then
onboard
more
customers.
This
sounds
like
a
really
good
plan.
You
can,
let's
say
your
customers
just
say
we
need
everything
set
up
in
the
next
six
months.
J
J
You
should
also
think
of
that,
and
then
is
maintenance
so
because
you
are
hosting,
and
are
you
on
everything
you
have
to
make
sure
you
maintain
the
physical
and
also
the
software
side
of
things
same
goes
with
security.
You
don't
want
someone
to
just
come
in
and
knock
off
the
servers,
so
you
have
to
make
sure
there
is
physical
security
and
also
software
security,
so
the
applications
are
safe,
so
you
plan
for
all
of
them,
but
you
still
have
a
lot
of
other
things
to
do.
J
You
need
to
make
sure
the
updates
are
done
right,
think
about
monitoring
and
making
sure
everything
is
working,
fine
and
then
there's
backups
and
this
deadline.
So
let's
say
your
customer
says
we
want
things
to
be
done
in
next
six
months.
It
always
happens
that
they
might
come
back
and
ask
you
to
complete
things
in
the
next
three
months,
so
you
should
be
able
to
deliver
it,
and
also
there
is
compliance.
So
let's
say
your
customer
is
in
the
region.
J
They
don't
want
their
user
data
to
move
away
from
europe
into
another
other
non-european
country.
Think
of
it.
This
way
the
huts
don't
want
their
data
to
be
tackled
right.
So,
as
we
just
discussed
all
of
this,
this
is
going
to
take
a
really
long
time.
So
simply
put
things
just
got
out
of
hand,
so
you
really
can't
think
of
it.
You
have
to
come
up
with
a
better
service,
so
yeah
you
can
use
kubernetes
as
a
service.
J
Kubernetes
server
is
simply
a
cloud
service
provider
offering
hosting
their
own
kubernetes
control,
plane
and
worker
nodes
and
on
their
own
infrastructure
and
then
offering
you
a
worker
mod
for
you
to
use
as
your
own
mod
and
run
your
application.
Here
we
see
azure
and
red
hat,
have
their
own
offerings
called
azure
key
connected
service
and
red.
J
Similarly,
aws
has
their
own
and
google
has
their
own
operas.
You
can
use
any
of
them
depending
on
the
depending
on
what
your
needs
are.
So
what
is
part
of
kubernetes
service
so
the
whole
cluster,
the
control
plane
side
of
thing
is
control.
Plane.
Side
of
things
is
all
managed
by
the
cloud
provider
and
also
your
nodes,
which
is
the
infrastructure
of
your
nodes,
and
everything
is
also
managed.
You
will
be
given
your
own
mod
in
a
really
fast
way
like
it
could
take
only
a
few
minutes
after
you
request
a
request.
J
Provisioning,
so
we'll
just
see
how
you
can
use
it,
so
you
will
get
your
own
worker
node
and
all
on
that
node,
you
can
run
your
applications.
So
how
does
this
help
us
in
scaling?
So
in
terms
of
scalability,
your
control,
node,
your
control,
plane
and
also
the
other
nodes
are
all
maintained
by
your
cloud
provider.
J
So
it's
as
simple
as
you
clicking
a
button
and
you
will
be
getting
multiple,
multiple
nodes
in
any
number
of
nodes
that
you
want,
and
this
can
also
be
automated
so,
depending
on
the
load
that
you
have,
you
can
automatically
scale
or
shrink
the
number
of
nodes
that
you
have
and
then
there
is
availability
so
availability
as
we
discussed
your
service
should
be
up
and
running
at
least
most
of
the
time.
There
is
nothing
like
100
availability,
so
it
has
to
be
available
for
at
least
a
lot
of
time.
J
So,
depending
on
your
needs,
the
cloud
providers
have
different
offerings
that
can
help
you.
So
here
what
you
can
do
is
you
can
host
the
modes
on
different
region.
This
can
also
help
you
with
highly
available
clusters
in
kubernetes.
So
let's
say
you
host
nodes
in
east
u.s
and
indonesia,
and
then
maybe
pandora.
So
if
your
east,
east
u.s
region
goes,
let's
say
something
happens
there
and
all
the
data
centers
in
the
east
region
go
to
asia
region.
J
Would
handle
that,
but
if
you
also
need
that
your
data
should
not
move
from
east
u.s
region
and
asian
data
should
not
go
there,
then
you
can
also
do
that.
You
can
configure
everything
in
just
a
click
and
in
terms
of
disaster
recovery
you
can
have
your
own
backups.
You
can
have
backups
replicated
into
different
locations.
All
of
these,
if
you
are
planning
to
do
on
your
own,
you
are
planning
to
you,
know:
host
your
own
infrastructure
and
stuff.
It's
going
to
take
a
really
really
long
time
and
it's
not
even
feasible.
J
If
you
are
a
small
company
that
just
wants
their
application
on
kubernetes,
so
simply
put
the
maintenance,
authentication,
auto
scaling
disaster
recovery,
everything,
including
the
infrastructure,
security,
physical
security,
everything
is
handled
by
your
service
provider,
they
have
their
own
nodes
and
all
of
that
at
different
data
centers
across
the
world.
You
can
use
them
and
you
can
focus
directly
on
the
application
of
your
company
planning
and
also
in
terms
of
metrics.
J
Thank
you
and
follow,
or
tell
us
on
their
twitter
and
also,
if
you
are
interested
in
contributing
to
autism,
please
check
out
their
github
repo.
If
you
want
to
reach
out
to
me,
you
can
reach
out
here
on
twitter
linkedin
or
you
can
check
out
my
blogs
on.
Also,
if
you
have
any
questions,
I'd
love
to
answer
them
feel
free
to
ask.
A
A
A
AC
AC
AC
AC
AC
Here
you
can
see
the
three
different
values
files
which
allows
us
to
move
between
the
different
stages
where
our
values
div
and
our
values
test
and
our
values
probed
and
our
values.yaml
file,
which
is
for
all
default
configuration.
We
have
a
templates
folder
and
in
there
we
usually
put
our
config
maps.
AC
AC
AC
AC
AC
M
M
A
M
M
A
A
AD
AD
Today,
I'm
going
to
talk
to
you
about
why
people
should
come
before
tech
and
how
devops
can
transform
companies
towards
becoming
more
efficient
and
productive
with
more
happy
and
engaged
colleagues
delivery,
focused
leaders
often
prioritize
milestones
and
deadlines
over
people
and
culture
and
treat
technical
work
as
a
technology
and
process
challenge.
Only
this
talk
can
help
you
to
make
the
point
on
how
investing
into
implementing
generative
culture
measurably
contributes
to
a
more
effective
delivery
in
the
form
of
eliminating
known
value
at
work
from
the
overall
process.
AD
One
important
thing
to
mention
here:
if
we
are
not
focusing
on
people
and
practices
first
before
bringing
in
automation,
then
automating
that
processes
will
end
up
in
bad
results.
We
basically
will
do
the
wrong
thing
faster
before
we
talk
more
about
devops.
I'd
like
to
talk
about
how
silos
were
invented.
AD
AD
Basically,
this
is
about
splitting
the
original
end-to-end
delivery
to
smaller
sub-tasks
and
ad
workers.
Only
trained
to
do
and
focusing
on
one
of
those
those
workers
become
really
good
at
their
own
step
and
very
productive.
Therefore,
speeding
up
the
whole
pipeline
and
improving
its
delivery
performance
fast
forwarding
the
present
time.
The
focus
on
task,
specialization,
control
and
measurement
are
still
present
in
today's
organizational
structures,
although
it
is
proven
very
effective
for
manufacturing
pipelines,
it
does
not
answer
all
the
challenges
in
scope
for
modern
I.t
services
management.
AD
AD
Silo
mentality
occurs
when
a
team
or
department
shares
a
set
of
common
tasks,
but
operates
disconnected
from
other
groups,
with
the
power
derived
from
association
with
the
function
or
shared
technical
knowledge.
Some
examples
of
these
are
the
testing
team,
which
is
focusing
on
one
slice
of
the
process.
Optimizing
own
approaches,
tools
and
processes
disconnected
from
the
end-to-end
delivery.
AD
AD
They
don't
look
for
using
solutions
existing
outside
of
their
team
either,
so
they
are
likely
end
up
duplicating
them.
These
teams,
the
testing
team
and
feature
teams,
could
actively
focus
on
improving
how
the
tasks
are
getting
delivered.
End-To-End
but
prioritizing
their
own
team
above
the
organization
choose
to
work
their
own
siloed
way.
Looking
inwards,
only
silo
mentality
leads
to
a
lack
of
systems,
thinking
which
is
essential
for
continuous
improvement
of
the
organization
system.
AD
Thinking
basically
means
that
the
theme
understand
that
their
function
is
part
of
a
larger
system
interrelated
and
interdependent
on
other
teams,
and
the
system
is
more
than
the
sum
of
its
parts.
Losing
focus
from
the
big
picture
leads
to
local
optimization
of
tools,
solutions
and
processes
which
creates
process
complexity.
AD
The
complex
handoffs
between
teams
are
treated
as
external
to
those
silos.
Therefore,
out
of
focus
for
improvements
waiting
for
information
approval
decisions,
feedback
are
good
examples
of
the
lack
of
systems
thinking
if
systems
thinking
would
have
been
applied.
In
this
case,
for
example,
waiting
for
approval
could
have
been
automated
based
on
business
rules,
therefore
removed
as
an
external
dependency
for
the
team,
improving
its
end-to-end
delivery.
AD
Another
side
effect
of
losing
focus
from
the
big
picture
is
lack
of
building
or
contributing
to
shared
capabilities
and
resources.
This
results
in
duplicates
reworks
and
divergent
solutions
or
the
team
working
on
unnecessary
deliverables
or
features
again.
If
systems
thinking
would
have
been
applied,
the
team
would
have
reused
an
already
existing
solution
implemented
by
another
team
instead
of
inventing
the
wheel
again
in
lean
management
terms,
weighting,
over-processing
defects
and
over-production
are
forms
of
non-value.
AD
The
next
step
is
to
identify
bottlenecks,
so
removing
those
can
be
prioritized
for
the
biggest
positive
impact.
Devops
embeds
amplified
right
to
left
feedback
loops.
The
goal
of
almost
all
process
improvement
initiative
is
to
shorten
and
amplify
feedback
loops,
so
necessary
collections
can
be
continually
made
in
the
process
as
quickly
as
possible.
AD
AD
Devops
promotes
a
culture
of
continuous
experimentation
and
learning
to
enable
the
ongoing
creation
of
knowledge
for
individuals,
teams
and
the
organization
just
because
we
have
been
doing
things
a
specific
way
in
the
last
two
years.
It
does
not
mean
we
have
to
do
it
exactly
the
same
way
in
the
future.
AD
AD
Okay,
so
if
you
take
away
one
thing
from
this
session,
it
should
be
that
if
you
want
to
improve
and
scale
your
delivery,
the
right
place
to
start
with
is
talking
about
your
culture.
Can
you
identify
silo
mindset
in
your
teams?
Is
there
effective
collaboration,
cross-pollination
and
contribution
to
shared
capabilities?
AD
If
you
do
this,
it
will
have
a
massive
positive
impact
on
your
culture
and
the
automation
and
tooling
part
to
underpin
and
accelerate
your
processes
will
be
easy.
I
hope
you
find
this
task
useful
in
case
of
any
questions
or
comments.
Please
feel
free
to
reach
out.
You
can
see
my
medium
linkedin
and
twitter
handles
there.
AD
A
A
A
A
A
AE
AE
So,
let's
get
started
before
we
move
into
a
real
automation
area.
Let's
just
know
a
bit
more
about
our
organizing
coming
company,
which
is
audelius.
So
a
brief
summary
about
this
organization.
The
product
artillery
is
is
a
as
a
micro
service
management
platform
and,
as
we
all
know,
a
bit
that
in
microservices
architecture
we
have
a
lot
of
decoupled
pieces
and
there
comes
the
problem
here.
Those
problems
are
addressed
by
cataloging
by
decoupling
pieces,
like
version
details,
tracking
microservices,
blast
radius
and
much
more
other
information.
AE
AE
Because
of
this
distributed
nature,
if
you,
if
we
have
not
moved
out
yet
from
the
working
from
silos,
doing
the
deployment
separately,
one
by
one
dependent
on
each
other
or
so
you
know
there
comes
a
lot
of
cures,
and
that
is
why
we
need
divorce
practices
to
be
here,
some
automation
to
be
here,
and
these
operations
there
is
a
need.
So
that
is
where
I'm
going
to
bring
some
information
to
you
today
in
this
session.
AE
That
is
about
my
recent
experience
and
personally
in
the
recent
years
I
have
been
a
massive
devops
enthusiast
and
I've
been
working
with
in
these
sectors
has
already
mentioned.
Apart
from
this,
in
my
free
time,
you
can
find
me
cooking,
doing
online
vlogging
and
on
weekends,
doing
some
photography.
So
this
is
all
about
me,
okay.
So
let's
get
started
on
this
as
we
already
talked
a
bit
about
the
problem,
so
we
we
can
see.
You
know
these
dots,
colorful
dots
on
this
slide.
AE
If
you
see
so
these
small
small
dots
are
nothing
but
different
micro
services.
What
happens?
We
are
happy
now
we,
you
know
that
all
the
micro
services,
because
of
the
microservices
architecture
we
achieve
decoupling
and
but
at
the
same
time,
what
happens
like.
If
I
see
you
know,
let's
assume,
like
I'm,
the
release
manager
for
the
entire
project,
with
the
microservices
and
and
then
maybe
in
a
single
day.
We
need
to
deploy
many
microservices.
AE
So
then
there
comes
our
need.
You
know.
Maybe
there
is
one
change.
For
example,
I
want
to
change.
There
is
a
new
fresh
environment
and
we
have
in
that
new
fresh
environment.
Those
details
needs
to
be
get
added
to
all
the
deployment
related
things
and
for
all
the
micro
services.
So
how
do
we
you
know?
AE
Do
we
have
to
go
to
each
and
every
micro
service
that
the
source
code
and
make
some
changes
or
if
we
want
to
have
some
centralized
configuration
which
we
automate
and
you
know
which
makes
our
life
easy?
So,
let's
move
further
so
yeah.
So
there
are
many
configuration
automated
configuration
tools
available,
one
of
them
being
ansible.
AE
So
what
is
ansible
some
of
you
might
already
know,
but
we
want
to
start
with
the
step
one
here.
I
don't
want
anyone
to
just
you
know,
bounce
this
information,
so
ensemble
is
nothing
but
an
idea,
automation,
configuration
management
and
provisioning
tool.
It
uses
playbook
to
deploy
manageable
test
configure.
So
in
a
way
you
can
see
the
end-to-end
cicd
pipeline
right
from
the
part.
AE
When
we
start,
you
know,
building
a
code
to
then
doing
the
configurations,
testing,
managing
deployment,
everything
everything
can
be
covered
and
then
anything
from
full
server
environments
to
any
kind
of
project,
whether
it's
website,
whether
it's
good
application,
back-end
front-end,
anything
any
kind
of
application,
it
supports
all
of
them
and
it
takes
while
by
yammer
so
yeah.
So
if
you
are
familiar
with
yammer
ml
is
a
very
easy
to
read
and
write
a
very
simple
way
of
having
a
code
so.
AE
We'll
talk
a
bit
more
about
it,
so
this
is
what
is
ansible
now
further.
We
want
to
know
why
and
simple.
So,
as
I
just
mentioned
yes,
a
gamer
is
something
very
easy
to
read.
Its
syntax
is
pretty
simple
and
ansible
is
an
agentless
one
of
the
boon
which
we
have
about
it.
So
if
you
can
compare
with
other
configuration
automation
tools
like,
for
example,
if
I
talk
about
puppet
or
something
so
there,
those
are
not
agentless,
we
have
to
have
a
dedicated
server
and.
N
AE
AE
It
has
so
I
see
it
as
a
perfect
solution
to
get
started
in
terms
of
automating.
Your
microservices
configuration
further.
How
does
ansible
work
so
here?
If
you
see
in
this
first,
let's
talk
about
the
diagram,
so
a
person
there
using
a
machine.
Let's
call
this
machine,
as
you
know
the
place
where
the
ml
file
is
present
or
playbook,
you
can
call
it,
let's
call
it
ncbl
playbookwebservers.tml
and
then
from
that
playbook
we
want
to
connect
to
different
web
folders
like
web1
web
2
web
3.
AE
These
are
the
hosts
different
hosts
and
if
you
see
the
sample
web
server
cml
file
there,
so
the
syntax
is
also
pretty
simple,
like
we
start
html
file
with
like
three
dash
and
then
we
add
more
information
with
single
dash
and
name
hosts
here.
The
host
in
the
diagram
are
like
web
one,
two
three,
and
likewise
we
just
add
at
their
tasks,
subtask
whatever
we
want
to
do
like
install
blah
blah
blah
restart
this
copy.
This
to
this
move,
this
file
delete
this
file
rename
this
file.
AE
So
all
those
things
we
can
just
add
over
here
in
this
playbook.
So
this
is
a
very
basic
example.
Of
course,
we
can
have
some
better
design
also
there,
but
that's
about
the
advanced
thing.
Okay.
So
now,
let's
have
a
look
of
the
architecture
and
civil
architecture
here,
if
you
see
so
again
a
couple
of
things
which
are
the
main
pillars
of
ensembl
architecture,
so
users
from
the
user
side,
if
we
see
ansible
there
is
something
called
host
inventory,
so
host
inventory
is
a
file
which
which
has
the
detail
of
the
host.
AE
For
example,
let's
take
some
project
like,
for
example,
which
has
certain
three
environments.
Just
you
know
maybe
dev
test
and
production,
so
those
three
environments:
they
will
the
target
environments
their
server
details.
We
call
them
like
host
and
then
this
host
inventory
will
have.
You
know
that
dev
server,
some
host
environment
details
or
like
that
test,
environment
and
blockchain
environment
then
again
playbook.
AE
We
just
saw
an
example
of
playbook
where
yaml
file
is
there
and
we
have
tasks
and
subtasks
or
something-
and
we
just
call
those
tasks,
then
talking
about
the
modules.
This
is
a
very
important
part
of
ansible
core
modules,
custom
modules,
so
ansible
works
on
basis
of
modules.
I
would
recommend,
if
you
are
interested
after
this
session,
whenever
you
have
time,
go
to
the
ansible
documentation
and
there
just
look
after
the
modules
it
has.
So
there
are
different
kind
of
modules
for
different
areas.
AE
For
example,
if
you
want
to
go
with
the
calendar
time
or
something
if
you
want
to
work
with
just
operating
system
related
things,
so
there
are
different
models
for
different
areas.
Have
a
look
of
it.
There
are
standard
modules.
There
are
modules
where
you
can
customize
them,
and
then
there
are
plugins
available
add-ons,
for
example,
like
ebay
logging,
etc,
etc,
and
then,
in
terms
of
connect
connectivity-
and
there
are
again
some
standard
functions
available,
how
do
we
connect
with
the
different
hosts?
AE
Okay,
so
moving
further
a
playbook
structure?
So
we
did
have
a
look
of
you
know
how
playbook
iml
code
like
similarly
here
we
have
the
flow
diagram
of
it.
So
if
you
see
from
playbook
the
first
ml
file,
which
which
is
invoked
when
we
start
current
simple
functionality,
so
it
will
just
start
with
playing
connecting
to
the
host
and
then
playing
the
tasks,
and
then
tasks
will
further
invoke
the
modules,
depending
on
what
modules
we
have
written
over
there.
So
it
will
just
invoke
those
modules
and
those
functions.
AE
Flow
of
this
step,
one
where
we
have
some
docker
some
counterization
and
help
of
that
move
further.
We
are
here
in
this
example,
which
triggers
audelius
to
version
microservices,
track
application,
configuration
management
and
build
the
maps
which
are
required
so
after
having
everything
contourized,
then
further,
the
audio
source
code
is
available
with
the
right
version
with
the
right
track
and
everything
moving
to
the
star
step:
three,
where
the
the
scheduling
is
already
done,
which
is
based
either
on
demand
or
on
the
series
triggers,
so
those
deployment
gets
triggered.
AE
AE
AE
Audios
can
execute
existing
playbook
to
perform
deployments
yeah.
We
just
talked
about
that.
Then
audilius
called
after
ansible
has
executed
a
deployment
and
record
information
about
a
deployment.
For
example,
what
are
the
microservices
deployed?
What
are
the
environments
where
the
deployment
is
then
done
and
the
logs
which
are
generated
so
all
those
things
all
those
things
can
be
captured?
I
have
been
gathered
here
and
then
about
the
pre
post
and
custom
actions.
AE
This
is
a
very
important
part
where
ansible
is
being
used
and
in
the
component
level,
where
link
happens,
and
then
this
is
in
two
areas:
pre-action
and
post
action,
so
pre-action
would
be.
If
we
talk
about
kubernetes
area,
these
playbook
to
scale
kubernetes
clusters
prior
to
deployment
when
we
want
to
scale
up
their
servers
and
after
the
deployment
again,
we
use
them
to
run
sql
plus
to
load
I
sql
into
oracle
db.
So
this
is
the
area
how
or
orterius
product
is
using
n
symbol.
AE
So
let's
learn
a
bit
more
about
creation
of
ansible
playbook,
how
it's
done
in
what
alias
and
there's
a
screenshot
as
well
so
auto
lease
product.
You
know
dynamically,
creates
ansible
viewer
book
to
on
and
it
runs
on
the
fly,
as
you
can
see
here,
the
end
circle
area
and
simple
playbook,
our
unit.camel.
AE
AE
So
again,
here,
as
we
already
discussed,
pre
post
and
custom
actions
are
the
three
main
areas
where
ansible
interaction
is
done
from
orderless
and
as
we
are
using
ansible
to
execute
ham
deployment
of
the
product
of
a
component
to
the
kubernetes
cluster.
And
if
you
see
here
that
custom
action
is
already
mentioned
and
that
ham
chart
is
being
used
as
a
part
of
this
okay,
so
that's
all
about
a
quick
session
on
ansible
how
we
can
use
it
as
a
part
of
automating.
The
configurations
for
microservices
questions
are
welcome.
AE
H
AE
And
if
you
want
to
know
more
about
its
upcoming
events
or
something
just
go
to
the
linkedin
area
and
do
follow
linkedin,
if
you
like
the
session
and
would
like
to
have
more
sessions
and
in
case
you
know,
feel
free
to
get
in
touch
with
me.
I
have
mentioned
my
twitter
and
my
linkedin
are
more
active
on
linkedin
on
my
linkedin
profile.
F
Arterius
is
an
incubating
project
under
the
cd
foundation,
and
our
mission
is
to
simplify
the
adoption
of
microservices
through
a
world-class
microservices
management
platform,
driven
by
a
supportive
and
diverse
global
open
source
community.
In
other
words,
we
have
a
great
team
from
all
over
the
world
on
the
open
source
project
here.
F
So
our
topic
today
is
we're
going
to
talk
about
hardening
cyber
security
in
a
cloud
native
environment,
meaning
that
we
need
to
track
not
just
a
microservice
s-bomb
but,
more
importantly,
the
applications
s-bomb
in
a
decoupled
architecture.
It's
almost
impossible
to
create
an
application
s-bomb
without
using
something
like
ortelius.
F
F
F
So
when
we
first
had
the
monolith,
we
would
go
ahead
and
create
a
single
s-bomb,
because
we
had
a
big
giant
package
that
we
were
working
with.
You
know
we
delivered
this
big
giant
package
and
therefore
we
had
one
big
giant
s-bomb
and
that
s-bomb
was
usually
created
out
of
the
build
process
to
compile
linkstep.
F
So
what
we
need
to
do
is
take
another
look
at
what
a
microservice
application
really
looks
like
it
actually
is
a
a
collection
of
microservices,
all
all
the
microservices
that
are
needed
to
make
the
application
run.
So
if
we
have
100
microservices
that
are
used
to
make
our
application
run,
we're
going
to
have
to
pull
all
those
together
and
represent
our
application.
Logically.
F
So
because
of
this,
we
have
a
lot
of
change
happening
that
we
need
to
keep
track
of
and
because
of
that,
the
s-bombs
get
even
more
complicated
because
remember
when
we're
talking
about
these
microservices
being
having
their
own
build,
we
have
to
look
at
those
builds
happening
all
day.
Long
and
those
builds
are
create
their
own
individual
s-bomb
and,
in
truth,
s-bombs
are
not
only
are
there's
many
levels
to
them.
So
we'll
have
a
hardware
s-bomb
we're
using
arm
versus
amd.
F
F
Q
F
So
how
do
we
fix
the
problem?
Well,
we're
going
to
aggregate
up
all
those
microservice
s-bombs,
including
their
vulnerabilities
up
to
the
application
level,
and
we're
going
to
pull
that
together
at
the
logical
viewpoint.
So
this
aggregation
has
to
occur
to
give
us
that
view
from
the
application
point
of
view.
F
So
how
do
we
make
all
this
work?
First,
like
a
a
producer
of
the
microservice
and
one
of
those
developers
is
going
to
give
us
and
create
us
the
base
version
of
the
microservice
in
the
in
ortelius.
This
base
version
is
going
to
give
us
the
starting
point
to
start
tracking
the
s-bombs
and
the
relationships.
F
One
of
our
future
enhancements
is
when
the
developer
registers
their
new
service
that
will
integrate
with
backstage
or
cookie
cutter,
to
go
ahead
and
generate
the
back-end
pipeline
plumbing.
To
have
everything
all
ready
to
go
on
on
the
pipeline
side.
Also,
we'll
be
adding
tags
to
domains
to
help
searching
for
microservices
a
bit
easier
and
then
the
consumer
who's
going
to
be.
F
Now
we
do
this
once
again.
This
is
at
the
the
base
version,
and
this
gives
us
the
starting
point
and
from
there
on
it's
going
to
be
self-maintaining
as
the
ci
process
comes
along.
We
update
a
service,
we
know
where
the
previous
one
was
used
and
therefore
we
can
generate
new
application,
logical
application
versions
going
forward.
So
it's
it's
really
nice
because
it's
you
know,
you
define
it
once
and
forget
about
it,
and
it
just
keeps
going
collecting
the
data
that
you
know
we
need
to
aggregate
forward.
F
F
So,
even
though
some
of
them
most
of
them
will
probably
only
make
it
to
a
certain
point
in
your
pipeline
process,
it
gives
you
the
choice
of
which
ones
to
want
to
be
a
release
candidate
and
therefore,
which
ones
are
going
to
make
it
out
to
production.
We
need
to
keep
track
of
all
that
information,
so
we
have
a
history
in
a
timeline
of
what's
happening
with
your
application,
as
changes
are
being
made
to
it.
F
So
when
we
look
at
it
from
the
the
pipeline
automation
point
of
view,
the
microservice
developer
is
going
to
go
ahead
and
make
changes
to
their
service.
They're
gonna
kick
off
their
their
docker,
build
after
the
docker,
build
we're
gonna
bring
in
ortilius
to
grab
information,
we'll
actually
run
a
s-bomb
scanning
tool,
something
like
sift
that
will
give
us
the
the
s-bomb
for
that
service.
F
From
there
we
can
drive
the
cves
and
vulnerabilities.
Also
we're
going
to
grab
information
about
the
artifact
itself.
Things
like
the
docker
tag,
dr
shaw
docker
digest
the
github
version.
The
git
commit
servers,
catalog
information,
all
that
is
gathered
by
the
artillious
step
in
the
pipeline
and
then
from
there.
We're
gonna
go
ahead
and
update
artilles
intelli
artilleries
about
all
that
information,
and
it
will
go
ahead
and
give
us
a
new
logical
view
of
our
application
at
that
point.
F
So
we'll
create
a
new
version
of
the
component
and
subsequently
create
a
new
logical
version
of
the
application,
and
this
gives
us
the
ability
to
aggregate
again
the
s-bomb
up.
Look
at
the
the
versioning
of
your
application,
as
is
happening
over
time,
do
difference.
Reports
do
trend
analysis,
those
type
of
things
at
the
application
level
and
that's
the
important
thing
we're
doing
this
for
every
single
service
and
therefore
we
get
this
nice
complete
picture
at
the
application
level.
F
So
what
what
does
it
look
like
when
we
start
looking
at
the
data?
From
the
application
point
of
view
you
can
see
here
in
the
left
table
panel?
We
got
our
vulnerability
list
and
in
that
vulnerability
list
you
can
see
which
component
the
vulnerability
is
showing
up.
So
if
they,
the
same
vulnerabilities
and
multiple
microservices,
we'll
report
that
or
if
it's
only
in
one
we'll
be
able
to
show
that
as
well,
but
here
you're
able
to
see
from
the
application
point
of
view.
Where
do
you
all?
F
Your
vulnerabilities
exist
across
all
your
services
that
are
that
your
application
is
using
and
then
on
the
right.
We
have
our
s
bomb
and
here
we're
listing
all
the
packages
that
are
being
consumed
across
all
the
the
services
and
what
licenses
those
packages
are
using.
You
know
that
the
licensing
is
concerned.
Maybe
you
have
a
like
a
new
license
in
there
and
the
lawyers
say
you
can't
use
anything
from
gnu.
This
will
allow
you
to
find
that
information
at
the
application
point
of
view.
F
I
I
I
can't
tell
you
how
much
how
thankful
steve
and
I
are
for
the
efforts
that
this
team
has
put
in
to
artelius
and
building
out
this
visionary
summit,
lots
of
great
content
and
we'll
be
pushing
this
out
on
social
media,
so
watch
for
it
and
share
it
with
your
friends.
Thank
you
again
and
it's
a
wrap.
We
will
do
this
again
again
in
six
months.
I
That
gives
everybody
an
opportunity
to
get
as
much
content
out
there
as
possible
if
you've
never
presented
before
consider
presenting
next
and
december,
probably
december,
around
december
8th
at
our
next
visionary
summit
have
a
great
summer,
everyone,
and
let's
get
some
great
coding
done
over
the
course
of
the
next
four
months.
We
got
lots
to
do.
Thank
you.
Bye.