Fri Mar 30 19:22:20 HKT 2007
From
/weblog/database/transaction
Improve scalability via turn off transaction... do you think it will work?
http://martinfowler.com/bliki/Transactionless.html I think this Idempotency help a lot if we like to implement system in this way:
http://www.artima.com/intv/distribP.html or example is soft update
http://www.mckusick.com/softdep/ Follow up discussion -
http://www.artima.com/forums/flat.jsp?forum=276&thread=200350 Already get two comments from friends, there is the key points:
=== Rob
Not if everything works as intended. But if something goes wrong you might get an unexpected state in the database. Then you have to do more work in other places to deal with the fact that the database might be in a state that wasn't intended, but is theoretically possible because you didn't use transactions.
=== Rex
Rex: exactly the thing what i did in last year to boost up performance from 700 txn per second to more than 10K txn per second.
Carfield Yim: handle rollback yourself you mean?
Rex:
u've to understand what is a system before talking the details...
different application can apply different rollback.
online/batch different are different.
Rule 1. make your txn simple.
if it can't be simple, your design must have problem
u have to understand your capacity & limitation..... such article is meaningless if you have no actual requirement...
if client is requiring 500 txn, that's no pt to have it like that.
(google search)
(amazon search)