[Seaside] saving an image while serving

Nevin Pratt nevin at bountifulbaby.com
Sun Apr 17 22:02:53 UTC 2011


Nevin


> Nevin,
>
> without giving away any confidential information can you elaborate a little on 
> how you do things? That might be a good scenario for people to know not to 
> care about persistence and scalibility to early.
> I have problems digest what you are saying. Thinking of a single image it can 
> only work if you can have the complete model in memory without problems. Or do 
> you do domain partionioning? It would be interesting to know your approach.

You are thinking about it too hard.

Just an image.  Nothing fancy.  Everything in memory.  No problem.  Really.


> Second I would like to know how you replay data after a crash. A plain image 
> approach wouldn't help because there is no persitence at all and the data 
> would be lost. Do you replay from another server/system or do you store 
> anything outside the image for error recovery?
>
>

Again, you are thinking about it too hard.

The "plain image approach" works just fine.

> and the data would be lost. 

So what.  Grab yesterday's image.  Put the data back in since yesterday.

Just an image.  Nothing fancy.  Everything in memory.  No problem.  Really.

Nevin



More information about the seaside mailing list