►
From YouTube: Backstage.io review
Description
Backstage wevpage: https://backstage.io/
Backstage demo video: https://www.youtube.com/watch?v=lRZr-8wkf7M
A
Hi,
my
name
is
victor
knight,
and
I
would
like
to
show
you
a
quick
overview
of
the
software
called
backstage
excellent
io,
because
I
think
it's
it
could
be
interesting
to
all
people.
It's
actually
it's
a
very
similar
idea
of
what
they
want
to
build.
That
gitlab
has
with
a
single
application
for
the
whole
devops
life
cycle,
but
they
have
a
totally
different
approach
to
it.
A
A
I
will
link
this
youtube
video
as
well
under
the
under
this
current
video
that
I'm
recording.
So
this
is
an
app
store
for
all
the
developer
tools.
They
have.
It
says
that
supercharged
developers
and
skates
a
really
standard
interface
for
which
engineers
interact
with
all
these
tools,
including
github
circle,
ci,
the
balances
networks
and
many
many
other
things.
It's
very
much
pluggable
and
it's
part
of
the
cnc.
It's
currently
cncf
sandbox
project.
A
A
I
already
set
up
the
configuration,
so
I
could
log
in
with
gitlab
and
now
it's
basically
almost
empty.
There
are
two
pre-made
services,
but
I'm
not
going
to
go
into
these
ones.
Instead,
I
will
show
you
the
ones
that
I
created
for
this
demo
and
I
will
create
another
one
as
well.
Let's
start
with
creating
one,
I
hope
I
won't
fail
doing
that.
Let's
start
with
the
react
template
as
you
can
see,
they
have
templates
and
you
might
think
that
oh,
we
have
project
tablets
as
well.
Actually
you
are
wrong.
A
What
they
have
is
a
logic
that
runs
when
you
create
a
new
project.
It's
not
just
a
git
fork
of
an
existing
project.
As
a
result,
they
can
set
up
environments
variables
they
can
set
up.
You
know
advantages
cluster.
At
this
specific
moment
they
can
set
up
everything,
because
there
is
logic
behind
these
things,
and
I
would
say
that
we
have
all
the
details
for
that
as
well:
unique
name
backstage
demo,
demo.
A
React
I
really
started
because
I
don't
need
to
have
actions
next
steps.
The
owner
user
management
is
through
resources
here
as
well.
This
is
not
set
up
properly,
so
it
won't
make
much
sense,
but
anyway,
let's
do
something
and
then
come
to
the
store
path.
This
is
very,
very
interesting
actually
because
I'm
just
going
to
give
them
a
path
that
does
not
exist
yet.
A
A
Back
as
you
can
see,
it
took
around
five
minutes
to
to
get
all
of
it
done
it
had
a
prepare
step.
It
did
something
there.
I
had
no
idea
what
it
was
then
templating
one
here.
It
actually
runs
the
create
react,
app
command.
That
creates
the
repository
itself
and
many
other
things
as
well
could
be
done,
and
then
it
publishes
repo
to
gitlab
and
registers
it
within,
but
in
backstage
now
we
can
open
it
indicator
in
the
service
catalog,
and
here
we
are
it's
a
website
backstage
demo.
A
A
A
few
things
around
this
one
is
that
you
might
think
that
actually
we
have
the
same
thing
because
we
have
repositories.
We
have
a
nice
structure
with
groups
that
end
in
repository,
but
actually
the
mental
model
of
backstage
is
totally
different
following
the
idea
of
our
users.
Many
of
them
think
this
might
be
better
many
users,
especially
microservice
oriented
users,
and
I
presume
that
many
of
us
are
about
these-
that
usually
our
users
organize
map
the
organization
to
a
group.
A
That
means
that
the
developer
team
owns
a
whole
group
and
then
higher
level
like
a
squad
is
a
parent
group
of
that
group,
and
then
there
might
be
the
engineering
organization
or
department
that
is
the
parent
of
that
etc.
So,
if
you
want
to
find,
microservice
then
actually
have
to
know
the
owner,
because
you
have
to
know
that,
okay,
in
order
to
find
another
purchasing
microservice,
I
know
that
it
has
to
be
somewhat
purchasing
organization
in
squad
a
in
team
b,
and
then
I
can
find
repository
here.
Dimensional
model
is
just
the
opposite.
A
It
just
says
that
I
want
to
find
a
purchasing
microservice.
So
what
I'm
doing?
I'm
going
to
catalog
and
I'm
searching
for
it.
Actually,
I
can
have
it
search
for
that,
but
just
the
other
way
around.
The
idea
here
is
that
we
want
to
find
given
service
with
its
owner
that
it's
responsible
people
with
its
code
base,
documentation,
apis
etc,
and
this
is
how
they
approach
this
topic.
A
Anyway,
let's
get
back
here
and
let's
create
a
new
another
component,
this
will
be
an
application
that
I've
created
already,
so
I'm
just
going
to
import
it
actually
to
give
you
an
idea.
Why
I'm
doing
that
here
you
can
see
that
for
links,
add
some
kind
of
links
to
metadata
thing
and
then
there's
some
tech
docs
what
it
might
be.
A
So
I
created
already
an
application
that
actually
provides
these
things
so
register
an
existing
component,
and
here
what
something
you
can
say,
the
record
in
the
service
register,
because
actually
history
is
described
in
the
format.
This
is
nothing
new,
nothing
fancy,
I
would
say
so
that's
important
again.
This
will
just
react
up
like
what
did,
but
this
one
has
a
link
to
one
of
the
hunger
news
sites
that
I
really
recommend
and
it
has
a
link
to
tech
docs
as
well.
A
A
A
Then
I
going
to
yeah,
you
can
have
you
see
a
few
things
here
like
cicd,
that's
by
default
circle,
ci
lighthouse,
google
errors
could
be
kubernetes.
Docs
is
the
one
that
I
just
showed
you
two
balances,
I'm
going
to
show
you
this
and
lead
our
coding
sites
and
requests
with
a
good
help.
Basically,
so
let
me
show
you
another
project
that
I'm
going
to
import
to
show
you
its
kubernetes
integration.
A
A
A
Here
we
are
fine,
but
actually
we
can't
find
some
config
mags.
There
are
some
image
problems,
probably
and
so
on
and
so
forth,
and
then
it
has
my
cluster
still,
which
has
eleven
pods
running
and
nine
and
six
spots.
Had
errors
have
errors,
the
errors
were
actually
already
goods
and
outs
at
the
top
and
here's
everything
else.
As
you
can
see,
with
the
die
stronger
deployment,
I
have
a
bit
more
information
than
just
the
number
of
ports
running
or
not
running.
A
A
Basically,
this
is
the
kubernetes
integration.
There's
nothing
fancy
about
this
kubernetes
integration
and
I
would
say
we
can
provide
the
same
thing.
It
just
uses
labels
you
have
to
tab
both
to
your
kubernetes,
manipulating
these
labels
and
you
have
to
say
the
same
thing
in
the
annotations
part
of
this
registered
service.
This
yaml
file
is
a
service
register
file
used
by
backstage.
A
A
A
A
A
You
can
have
the
posterior
various
things
there
and
so
on
and
so
forth.
This
is
a
little
set
up
a
little
bit
outside
of
the
service
registry,
but,
as
I
can't
have,
post
per
service,
which
would
be
might
be
more
interesting
in
some
use
cases,
but
really
at
the
same
time
it
shows
us
something.
What
are
the
data
that
these
people
are
looking
at?
That
spotify
is
interested
in
and
probably
other
similar
companies
are
interested
as
well.
A
Another
really
nice
thing
that
I,
I
think
would
be
super
simple
to
add
to
git
lab
and
could
be
a
nice
marketing
feature,
I
would
say,
is
decredar,
I'm
sure
that
many
of
you
have
seen
this
from
various
analyst
reports
and
so
on
and
so
forth
at
first.
My
idea
was
that
this
shows
the
technologies
used
in
service
registry
and
it
doesn't
make
much
sense
in
that
case
it
does
make
some
sense,
but
not
much,
but
actually
what
it
does
is
very
different
from
that
this
is
somewhere.
A
These
are
the
recommended
technologies
for
us,
so,
depending
on
the
riskiness
of
your
project,
your
timeline,
etc.
You
can
pick
the
technologies
that
suit
you
best
and,
as
a
result,
this
is
coded
again
outside
of
the
service
registry.
It
doesn't
use
those
data
that
are
in
the
service
registry,
but
we
could
actually
provide
both
something
like
an
overview
of
what
higher
services
look
like
and
another
one
that
is
the
cto
recommendation
of
which
technologies
to
use.