Comments on: Amazon S3 persistent Ruby objects http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/ nutrun Tue, 06 Jan 2009 03:16:22 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Amazon Web Services links for 2008-03-25 | Elastic Grid Blog http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-354 Amazon Web Services links for 2008-03-25 | Elastic Grid Blog Wed, 26 Mar 2008 09:10:21 +0000 http://new-site.nutrun.com/?p=100#comment-354 [...] about using Amazon S3 persistent Ruby objects and an extended version using Amazon [...] [...] about using Amazon S3 persistent Ruby objects and an extended version using Amazon [...]

]]> By: amazon » Amazon S3 persistent Ruby objects http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-280 amazon » Amazon S3 persistent Ruby objects Sat, 20 Oct 2007 07:18:20 +0000 http://new-site.nutrun.com/?p=100#comment-280 [...] Read the rest of this great post here [...] [...] Read the rest of this great post here [...]

]]> By: evan http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-279 evan Thu, 12 Jul 2007 07:41:02 +0000 http://new-site.nutrun.com/?p=100#comment-279 Are you using YAML so you can index the data external to your app, or...? I don't really see a benefit over Marshal, especially with the overhead of instantiating the custom class every time. Are you using YAML so you can index the data external to your app, or…? I don’t really see a benefit over Marshal, especially with the overhead of instantiating the custom class every time.

]]> By: George Malamidis http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-278 George Malamidis Mon, 09 Jul 2007 12:25:51 +0000 http://new-site.nutrun.com/?p=100#comment-278 J, indeed. I've updated the article to reflect that. J, indeed. I’ve updated the article to reflect that.

]]> By: J Coppedge http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-277 J Coppedge Mon, 09 Jul 2007 04:04:20 +0000 http://new-site.nutrun.com/?p=100#comment-277 One note to remember - if you are using S3 with EC2 to host your application there is no cost for data between the EC2 server instances and S3 service. One note to remember - if you are using S3 with EC2 to host your application there is no cost for data between the EC2 server instances and S3 service.

]]> By: Mark Murphy http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-276 Mark Murphy Sun, 08 Jul 2007 20:32:06 +0000 http://new-site.nutrun.com/?p=100#comment-276 On the issue of price, you could at least prototype using _why's ParkPlace, an S3 clone written in Ruby. http://code.whytheluckystiff.net/parkplace On the issue of price, you could at least prototype using _why’s ParkPlace, an S3 clone written in Ruby. http://code.whytheluckystiff.net/parkplace

]]> By: Peter Cooper http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-275 Peter Cooper Sun, 08 Jul 2007 19:57:30 +0000 http://new-site.nutrun.com/?p=100#comment-275 You could probably control some of the cost and speed issues by implementing it like a pstore (that is, a single file) that syncs every now and then, so no constant HTTP traffic back and forth. Would hurt concurrency though! You could probably control some of the cost and speed issues by implementing it like a pstore (that is, a single file) that syncs every now and then, so no constant HTTP traffic back and forth. Would hurt concurrency though!

]]> By: George Malamidis http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-274 George Malamidis Sat, 07 Jul 2007 14:21:02 +0000 http://new-site.nutrun.com/?p=100#comment-274 Thanks for the info. Amended the example accordingly. Thanks for the info. Amended the example accordingly.

]]> By: Ola Bini http://nutrun.com/weblog/amazon-s3-persistent-ruby-objects/comment-page-1/#comment-273 Ola Bini Sat, 07 Jul 2007 12:52:12 +0000 http://new-site.nutrun.com/?p=100#comment-273 Interesting approach. (You don't need to include YAML, btw. Everything gets a to_yaml method when you require 'yaml') Interesting approach.

(You don’t need to include YAML, btw. Everything gets a to_yaml method when you require ‘yaml’)

]]>