Comments on: Amazon S3 and Cardbox http://cardbox.wordpress.com/2006/07/11/amazon-s3-and-cardbox-2/ Designing, building, selling and supporting a leading End User Database Sat, 22 Mar 2008 01:20:32 +0000 http://wordpress.com/ hourly 1 By: New Amazon service agreement « Cardbox http://cardbox.wordpress.com/2006/07/11/amazon-s3-and-cardbox-2/#comment-2954 New Amazon service agreement « Cardbox Tue, 03 Jul 2007 13:16:15 +0000 https://cardbox.wordpress.com/2006/07/11/amazon-s3-and-cardbox-2/#comment-2954 [...] its predecessor, which we criticised in detail in the S3 in Business article. Using the “backup to S3” features of Cardbox now seems legally as well as technically [...] [...] its predecessor, which we criticised in detail in the S3 in Business article. Using the “backup to S3” features of Cardbox now seems legally as well as technically [...]

]]> By: cardbox http://cardbox.wordpress.com/2006/07/11/amazon-s3-and-cardbox-2/#comment-863 cardbox Wed, 06 Dec 2006 08:14:02 +0000 https://cardbox.wordpress.com/2006/07/11/amazon-s3-and-cardbox-2/#comment-863 There were already some backup mechanisms in place but nothing directly analogous. I'd say the whole thing took a week: 1. Developing a "backup while still working" function for backing up to the local hard disk. (This was derived from the "download while still working" function that already existed). 2. Developing the scheduler to make the backup happen at user-selected times and intervals. 3. Developing the user interface for scheduler specifications. (This was the most complex part of the project). 4. Adapting (1) to back up to S3 instead of the hard disk. All the ingredients were already there: "back in small chunks while working", from (1); and the whole business of asynchronous TCP/IP communications, because serving data requests, the main function of the Cardbox Server, already works like that. There were already some backup mechanisms in place but nothing directly analogous. I’d say the whole thing took a week:

1. Developing a “backup while still working” function for backing up to the local hard disk. (This was derived from the “download while still working” function that already existed).
2. Developing the scheduler to make the backup happen at user-selected times and intervals.
3. Developing the user interface for scheduler specifications. (This was the most complex part of the project).
4. Adapting (1) to back up to S3 instead of the hard disk. All the ingredients were already there: “back in small chunks while working”, from (1); and the whole business of asynchronous TCP/IP communications, because serving data requests, the main function of the Cardbox Server, already works like that.

]]> By: Damien Stevens http://cardbox.wordpress.com/2006/07/11/amazon-s3-and-cardbox-2/#comment-860 Damien Stevens Tue, 05 Dec 2006 19:37:11 +0000 https://cardbox.wordpress.com/2006/07/11/amazon-s3-and-cardbox-2/#comment-860 How long did it take you to develop the backup for Cardbox? Did you already have a backup system in place before using S3? How long did it take you to develop the backup for Cardbox? Did you already have a backup system in place before using S3?

]]>