AUTHOR: http://aws.typepad.com/aws/2008/03/programming-ama.html LINK!

Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Dekoh - Amazon EC2 case study | Main | New EC2 Features: Static IP Addresses, Availability Zones, and User Selectable Kernels »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef00e55174dc558833

Listed below are links to weblogs that reference Programming Amazon Web Services:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Gary

So it does cover EC2 and SQS in detail? I was a bit worried -- the O'Reilly TOC is only showing 3 chapters and they really only cover S3: http://www.oreilly.com/catalog/9780596515812/toc.html

Jeffrey McManus

Python and Ruby, ugh. Why couldn't he have just done his code examples in Lisp?

TheRealBill

As someone with the book it should really be titled "Programming Amazon Web Services with Ruby".

Most of the examples are using a higher level Ruby module (or whatever they are called) to hide the actual implementation. If it were titled above this would not be an issue or need for clarification. As titled it purports to be a (general) guide to programming AWS. Saying "things go on and there are three ways to do this but we'll be using [insert ruby AWS module here] instead" is a serious let-down.

I've nothing against Ruby per-se (though I do prefer Python and C++) or a book for AWS via Ruby. So long as it is correctly titled so people don't mistake it. Seems to me though that as a Ruby book it would be a bit of a let-down as it is tutorial level stuff you can probably find in the Ruby AWS module docs. But that's me.

What would have made it better, other than reclassifying/retitling it? Describing the calls. Instead of saying "there is a REST call that does this, but we'll use this higher level language-specific module", describe the call itself, show the details. Then, once that is done show an example using a higher level module - as an *example*, not the "description".

Note that as a Python programmer Id would have the same comments if the overly dominant code example language was Python, I'd just be typing "Python" instead of "Ruby". It isn't the language that is the issue, it is the use of higher level interfaces that hide what is going on with AWS. For example, if the author wished to demonstrate listing bucket contents, showing in whatever languages chose the "raw" calls to the AWS servers would be usable. Showing an example in Python or Ruby that merely calls a function that says "gimme the list" is not - unless you are using those/that language.

So if you are a Ruby scripter looking at AWS this book will likely help you. If not, probably not much help here that isn't in the AWS docs.

@Gary
Not so much on the EC2 but a decent set of chapters on SQS, with the above mini-review in mind.

Mar Matthias Darin

Hi,

If you are looking for a C code example, I have one here:

http://bit.ly/h3epGl

It demonstrates the Amazon Product API for start to finish.

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30