From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,c70dc869310ffb51
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,UTF8
Path: 
 g2news2.google.com!news2.google.com!news.glorb.com!news.alt.net!news-xfer.nntp.sonic.net!posts.news.sonic.net!nnrp1.nntp.sonic.net!not-for-mail
Message-ID: <4d337a94$0$44021$742ec2ed@news.sonic.net>
From: "R. Tyler Croy" <tyler@linux.com>
Subject: Re: Annoucing memcache-ada 0.1
Newsgroups: comp.lang.ada
References: <4d335a76$0$43992$742ec2ed@news.sonic.net>
 <2b5cd851-c148-41f4-95e7-14f235846e6a@q18g2000vbk.googlegroups.com>
User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (Linux/2.6.34.7-0.7-desktop
 (x86_64))
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Date: 16 Jan 2011 23:09:08 GMT
Organization: Sonic.Net
NNTP-Posting-Date: 16 Jan 2011 23:09:08 GMT
NNTP-Posting-Host: da96998a.news.sonic.net
X-Trace: 
 DXC=3@1HXJcmCQ<a@_k;K[aPP0m4K\QM1CV^01OYf0H`?;X1R=YDf8DeNF>`DkJ<8fF2g9NT:19VomFd8`nd=B7<WBE;
X-Complaints-To: abuse@sonic.net
Xref: g2news2.google.com comp.lang.ada:17439
Date: 2011-01-16T23:09:08+00:00
List-Id: <comp.lang.ada>

Maciej Sobczak <see.my.homepage@gmail.com> wrote:
> On Jan 16, 9:52 pm, "R. Tyler Croy" <ty...@linux.com> wrote:
> 
>> I hope somebody finds it useful, can't wait to see some examples of caching
>> with AWS! :D
> 
> The biggest advantage of AWS, when compared to "traditional" web-
> server hosting stateless scripts, is that AWS is stateful and being an
> in-process part of the complete application makes out-of-process
> caching useless.
> In other words, with AWS there is no need to cache anything in a
> separate process, because data can be stored for future use as a
> regular object in the program. This is not just faster, but also
> safer.
> 
> I have to admit, however, that web technologies are not my strongest
> point and I might miss some interesting use cases.

Heh, that's fine, lucky for you my whole job is in web technologies ;)

Anyways, the big advantages I can see with coupling AWS with memcached by way of
memcache-ada are:

    * Scaling to N web servers serving dynamic content, using a network-attached
      cache such as memcached, you could have web01 do the heavy lifting generating a
      page and then all the other webs (web02 - web05 for example) serve the cached
      version of the page. This can be accomplished via other means via Nginx or
      Varnish (for example), but neither of those will be able to cache arbitrary
      chunks of computed data, merely the responses

    * Providing an intermediary layer to your backing data store (MySQL, PostgreSQL,
      etc). While each RDMS has some amount of in-process caching, it can't really
      compare to the ability to continually add memcached instances. We use
      ~64GB of memcached storage at $WORKPLACE for caching various bits of data here
      and there, this is at the low-end for most big web companies. Indexes can only
      go so far, you can get a lot of mileage out of cheap caching of results from
      your DB.

I'm not sure what AWS is capable of in terms of the Distributed Systems Annex,
but I've never found a web project that couldn't be improved by a little extra
caching here and there :)


Cheers

-- 
- R. Tyler Croy
--------------------------------------
    Code: http://github.com/rtyler