[Seaside] Amazon EC2

[Bob Houston]

Yes, I agree.   A database hosted elsewhere might be the simplest  
solution.   Of course, an open-source object DB would be nice to  
use.  I'm curious if this might be an acceptable use for a GOODS  
database?  Is the GOODS "replication support" applicable here?  My  
thought is that we could use GOODS to run a primary server in our EC2  
instance, with a replicated server on a real host somewhere.  Or  
perhaps the other way around, with a real host running the primary  
server?   This way a real host machine will have a current copy of  
the data, and can be used to "seed" the EC2 instance at startup.   
Comments?

If GOODS is not the way to go, what other databases do you suggest.   
The goal is to have a local cache of the data in the EC2 instance  
(for performance), with a replica of the data on a real host (for  
persistence).


On Sep 6, 2006, at 5:39 PM, Avi Bryant wrote:

>
> On Sep 6, 2006, at 2:03 PM, Boris Popov wrote:
>
>> Indeed, see the FAQ entry over at http://tinyurl.com/k8knk
>>
>> "Q: What happens to my data when a system terminates?
>>
>> The data stored on a specific instance persists only as long as that
>> instance is alive. You have several options to persist your data:
>>
>>    1. Prior to terminating an instance, backup the data to persistent
>> storage, either over the Internet, or to Amazon S3.
>>    2. Run a redundant set of systems with replication of the data
>> between them.
>>
>> We recommend you should not rely on a single instance to provide
>> reliability for your data."
>
> Sure, so you need to be connecting to some database system hosted  
> elsewhere, or someone needs to build a database which can use S3 as  
> a backend...
>
> Avi
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>