►
From YouTube: Feedback on Scaling and Availability page
Description
In this call Sid and Mek discuss the pain points in digesting the information in the Scaling and Availability page.
A
A
This
is
inconsistent:
okay
under
a
thousand
okay,
great
sorry's
in
mm.
Okay.
Get
that
what
is
this
then
for
exactly
2000
users
or
no
probably
want
to
say
two
thousand
to
five
thousand
or
something
like
that.
I
would
say
something
else.
I
would
say
up
to
four
everything
up
to
a
thousand
users
up
to
two
thousand
two
users
and
just
keep
the
round
numbers,
because
it's
not
an
exact
science
and
we
shouldn't
we
shouldn't
pretend
to
that.
It
is,
and
it
says
here
please
consult
our
high
availability
documentation.
A
The
whole
idea
is
to
get
away
from
hey.
This
is
the
page
about
hi,
available
high
availability.
We
need
a
page
that
talks
about
availability
and
all
its
trade-offs.
There
is
functionality
and
get
lab.
That
is
like
a
che
for
tio
and
forget
Tilly,
but
availability
is
not
just
our
features.
It
is
also
like
what
is
whether
you
get
it
as
a
company.
What
are
your
requirements
and
everything
else?
So,
let's
get
away
from
that
and
we
change
the
name.
Let's
make
sure
we
change
our
references,
Danny
talks
about
get
luck,
components
and
scaling
instructions.
A
A
A
This
all
feels
like
it's
you
it's.
It
belongs
somewhere
else
completely
about
all
the
components
but
I'm
not
sure
I'm,
okay,
with
having
it
on
the
page
at
least
have
it
on
one
page
and
just
link
to
your
page,
and
this
is
not
a
third-party
service.
That's
that's!
That's!
That's!
A
third-party
services
are
very
that's
managed
by
another
organization
like
wow.
I
can
have
a
load
balancer
that
is
I
bought
yeah.
It's
not
good
lab
controlled,
but
that's
third-party.
You
should
see
it
from
the
customers
perspective
from
the
customer
perspective.
A
B
It's
being
worked
on
yes,
so
if
I
were
to
take
the
time
to
explain
here,
I
think
I
agree
that
the
the
range
of
the
users
are
not
to
the
point
that
we
want
it
to
be
yet
and
there's
there
is
this
in
in
the
middle
of
state,
where
we
want
to
add
more
information
for
under
a
thousand
users.
However,
the
additional,
where
for
the
existing
reference
architectures,
were
on
a
solid
number,
so
I
think
the
feedback
is
to
have
a
range
that
is
not
overlapping.
A
B
A
A
A
A
So
this
is
helpful,
but
why
doesn't
this
page
talk
about
like
hey?
If
you,
if
you
have
an
installation
size
smaller
than
this,
probably
you're
off?
What
would
that
cups?
And
if
you
have
this
many
users,
we
recommend
XYZ,
because
our
the
problem
that's
been
prevalent
in
the
in
the
company
has
been
this
page
guides.
I
want
to
do
a
high
availability
installation,
even
they
don't
have
the
expertise
and
it
causes
a
ton
of
trouble
for
them.
It
cuz
there's
a
ton
of
trouble
for
our
support.
That's
what
we
have
to
fix,
so
we
need.
A
A
This
this
whole
page
should
be
about
what
is
there,
but
also
about
what
should
I
select
one
and
people
have
been
very
afraid
to
kind
of
make
make
a
statement
like
so
right
now,
every
time,
Telus,
customers,
a
different
story,
every
support
engineer,
tells
people
a
different
story,
so
we're
advising
mostly
wrongly
because
leaders
there's
a
best
version
and
they're
not
getting
the
best
version.
Most
importantly,
we're
not
telling
them
here
so
they
go
off
and
like
oh,
you
are
what
availability?
Yes,
what
should
I
didn't?
Do?
Oh
I
should
do
the
highly
available
thing.
A
B
B
A
I'm
much
more
worried
about
like
the
customers
like,
if
you
don't
have
experience,
maintaining
like
a
highly
available
installation
with
console
and
everything
else.
You're
just
gonna
shoot
yourself
in
the
foot
and
it's
gonna
be
much
harder
to
remediate.
So
as
a
customer
you'll
end
up
with
lower
availability,
then
you
would
ever,
if
you
just
install
it
on
a
single
server
and
the
backup
said
you
can't
restore
and
I
mean
we
should
holy,
be
even
more
opinionated,
and
now
it
gets
pretty
dodgy.
A
I
would
say:
hey
always
start
out
with
like
a
single
server
and
do
backups,
and
only
after
you
master
that
you
go
to
this,
and
only
after
you
master
that
you
go
to
this.
A
chair
maybe
took
the
people.
Some
people
will
skip
that.
There
will
be
the
people
that
are
actually,
if
that
should
skip
that
so
trade
offs
and
opinionated
about
like
no
experience
no
scale,
don't
do
it.
B
A
A
B
A
A
B
A
Improvement,
so
thanks
to
that
allergy
that
listening
to
me
thank
you
and
I'm
again.
I'm
excited
I'm,
very
passionate
about
getting
this
right.
This
has
been
very
hard
and
it's
causing
our
customers
a
ton
of
frustration
and
cost
us
a
ton
of
money
and
an
effort,
but
I
recognized
it.
There's
no
I'm
frustrated
with
the
problem,
not
with
any
person.
I
recognize
that
this
is
tough
to
get
right
and
it's
not
being
your
responsibility.