Posted by Balazs Wellisch on 01/08/06 02:39

> Surely /each box/ doesn't need /its own/ database. If the objective is to
> allow some failure to be brushed-off then two databases with replication
> should do the trick when you need both DBs to be u/s before the system
> fails. Also you would operate normally on a single DB with the other in
> standby - as you'd be operating presumably with your main DB.

That is an option. However, I was thinking that from a maintenance
standpoint it would be easier to clone a system completely. That way I would
have a bunch of inexpensive, hot pluggable machines. This would give me
infinite scalability for a small initial investment and minimal
configuration to deal with as the number of systems increases. The database
is not going to be huge. Otherwise, you're right, it would probably make
more sense to go with your suggested setup of two separate databases.

> Q: What happens if I log into your site twice from my Tabbed browser.
> Might I operate as the same session but hitting different servers?[1] If
> so what exploit could I use to load a trolley on both screens, buy on one
> and decide not to buy on the other and have the cancel overwrite the buy
> but not before the goods were authorised for dispatch. [Not a 'you mustn't
> do it!, but a GLB-ism]
>
> [1] Even if by hacking the browser (but more likely by cutting and pasting
> ?SID=123456 from one tab to the other) - could be worth a lot of money.

This is more of an issue of security that I would have to deal with no
matter what. I think with URL based session ids turned off, session finger
prints and other security measures this problem can be eliminated.

Thanks for your advice.
Balazs

[Back to original message]