►
From YouTube: Choosing Between Self-managed and gitlab.com (SaaS)
Description
by Mark Cesario
GitLab Enterprise Solutions Architect
A
A
So
self
managed
or
on-prem
the
customer
is
directly
responsible
related
to
the
infrastructure
network
for
server
database.
I.
Think
you
get
it
Bob
wolf.
You
know
they
can
install
on
the
bus,
but
they're
still
responsible
for
all
this.
Mr.
curity
where's,
the
SAS
is
this
get
lab,
comma
SAS
offering
is
off
the
shelf.
It
may
be
quickly
literally,
can
be
up
in
hours.
A
Friction
service,
big
differences
pros
on
both
sides
and
we'll
walk
through
those
right
now
before
we
do
have
a
little
customer
story.
I
think
it's
good
to
know.
Probably
everybody
knows
Chris
Hill
if
they
were
at
that
scale
and
Chris
started
on
a
Jaguar
and
as
a
great
story.
If
you
click
this
you'll
drive
into
this
blog
one
of
our
blogs
and
basically
he
brought
in
get
lab.
It's
a
self
self
managed
they
controlled
infrastructure
and
network,
which
was
important
because
they're
actually
pushing
out
the
cars.
A
The
Land
Rover
as
people
are
driving
so
really
successful.
I
think
they
went
if
I
got
too
quickly
feedback
from
about
four
to
six
weeks
down.
The
thirty
minutes
would
give
great
story.
Then
I
had
two
years
here.
He
is
takes
his
family
from
the
UK
to
Seattle,
starts
working
at
t-mobile
as
the
senior
manager,
software
development
and
Chris
made
a
decision
early
on
that
hey
I
I.
Don't
have
that
six
months
window
to
spend
out
building
infrastructure
of
network
done
server
security.
A
All
of
that,
let's
partner,
would
get
Ladd
use,
get
lab,
comm
start
working
on
a
solution,
very
successful
story.
This
right
here
is
a
link.
You'll
have
for
Chris's
recent
talk
and
hey
Bill,
you
alw
summit,
and
it's
worth
the
20
minutes
and
I
spun.
Yet
breaking
point
where
Chris
starts
talking
with
that
link.
So
the
point
here
is
that
self-managed
SAS
both
important
both
viable.
A
So
let's
look
at
the
pros.
What
I
would
call
a
positive
assess
outcomes
required
capabilities?
You
need
forget,
LED,
that
calm
at
the
SAS
solution
low
to
no
overhead
right
Edmund.
You
don't
even
see
the
little
sprocket
up
at
the
time
infrastructure
cost
taken
care
of
by
Atlanta
Atlanta,
hired,
no
ability
accessible
anywhere
any
paid
anywhere
in
the
world,
minimal
loss
of
data
disaster
recovery.
All
of
that
is
part
of
yet
lab
calm.
A
You
do
not
have
to
deal
with
those
big
issue
for
Chris
at
t-mobile.
The
big
pros
and
I
see
what
self
manages
you
have:
total
control,
install
and
minister,
your
environment,
your
infrastructure
bare
metal,
VMS
kubernetes.
If
you
have
custom
hooks,
you
have
some
custom,
integrations
that
you
can't
have.
You
have
to
have
its
prior
to
your
whatever
your
gonna
go
at
self-manage
may
be
very
large
file,
so
we're
talking
a
large
file
if
you're
showing
handle
those
and
the
right
infrastructure
of
them
right.
A
You
know
hardware
or
database
whatever
you
can
do,
that
with
self-managed
give
lab
can
be
kinda
limited
to
what
get
led
that
comm
offers.
So
what
I've
got
on
the
bottom
here
is
a
link
that
takes
you
to
a
nice
list
of
all
of
these
differences
and
what's
important.
What's
you
know
where
you
can,
where
you
can
make
your
decision?
A
So,
what's
important
to
you
right,
you
being
the
customer
is
control
its
control
flexibility,
custom,
integration,
self-manage
really
is
the
option
now,
if
it's
more
of
resources,
infrastructure
costs,
implementation
time,
those
sort
of
key
issues
get
lab.
Comm
is
probably
a
better
option.
There's
always
security,
that's
always
an
issue
that
needs
to
be
considered
as
well.
So
do
you
take
the
red
pill
totally
managed
by
the
customer,
or
do
you
take
the
blue
pill,
which
is
managed
by
get
that
comment
lit
blissfully?
It's
a
choice.
Hopefully
I've
helped
you
get
to
there
understand
it.