[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tarsnap is here to stay.

To: Scott Wheeler <scott@directededge.com>
Subject: Re: Tarsnap is here to stay.
From: Michael Sierchio <kudzu@tenebras.com>
Date: Mon, 10 Mar 2014 10:06:14 -0700
Cc: Tarsnap Mailing List <tarsnap-users@tarsnap.com>
In-reply-to: <56BA30B4-627E-48BC-B2F2-3103785A2E7B@directededge.com>
References: <531C4689.8070907@qeng-ho.org> <531D027C.5030200@tarsnap.com> <531D0E3E.10009@timando.net> <03da01cf3c6e$b88f1e50$29ad5af0$@TheEwhiteboard.com> <56BA30B4-627E-48BC-B2F2-3103785A2E7B@directededge.com>

On Mon, Mar 10, 2014 at 8:31 AM, Scott Wheeler <scott@directededge.com> wrote:
>
> On Mar 10, 2014, at 3:40 PM, Daniel Wilson <Daniel@TheEwhiteboard.com> wrote:
>
>> As I understand it, the underlying infrastructure is AWS ... so ... massive availability is already provided. It would be one of the most difficult systems in the world to bring down with an uncoordinated DDOS.
>
> AWS doesn't make things scale with magic pixie scaling dust.  You still have to set things up specifically for auto-scaling to happen; I would wager that the majority of sites / web-services on AWS *do not* do that.

As evidenced by entire companies going down when AWS has problems in a
single region, or even a single availability zone. Architecting for
the cloud means doing more than forklifting an existing app.

- M

References:
- Tarsnap is here to stay.
  - From: Arthur Chance <freebsd@qeng-ho.org>
- Re: Tarsnap is here to stay.
  - From: Colin Percival <cperciva@tarsnap.com>
- Re: Tarsnap is here to stay.
  - From: Tim Anderson <tim@timando.net>
- RE: Tarsnap is here to stay.
  - From: "Daniel Wilson" <Daniel@TheEwhiteboard.com>
- Re: Tarsnap is here to stay.
  - From: Scott Wheeler <scott@directededge.com>

Prev by Date: Re: Tarsnap is here to stay.
Next by Date: Re: Tarsnap is here to stay.
Previous by thread: Re: Tarsnap is here to stay.
Next by thread: Re: Tarsnap is here to stay.
Index(es):
- Date
- Thread