On 10/3/07, Rogelio Serrano <[EMAIL PROTECTED]> wrote:
..
> so whats so bad about stateless protocols? i prefer them actually.
> specially over the internet. you can do distributed transactions over
> over them and stay sane.
I have a simple question regarding your distributed transactions.
- You have a server cluster, each machines is capable of executing a
business process transaction.
- You have a request dispatcher, which sends requests to any one of
the machines, depending on load and a variety of other parameters
- You need to process say 1 million transactions per second
- Now you issue a request ("transfer $1 billion dollars from account 1
to account 2"), send it to Machine #5, this process requires a lot of
back-end activity (which must complete as one transaction)
- Halfway through the business process, half of your machines die
(someone tripped over the power cord to the rack) including the one
which was doing the $1 billion transaction
What do you do?
What if a specific machine dies?
What if you start running out of capacity, can you add machines to the
cluster in an application-transparent and zero-hands way?
Finally, can you do this in 10MB of code?
Such a product exists. I know of nothing that even comes within a mile
of it in the Open Source world.
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
