Transactios in FBN

[Steve]

Hi All,
I'm Working on part 2 of the exam and I'm trying to think how to handle the transactions among multiple systems. For example what will happen if the credit card processing succeeded by the TransMaster API but there was an error in our system ?

Should this be explained in the arichitecture at all?

Thanks,
Steve

[Theodore Casser]

Hiya, Steve.

First, you might want to take a gander at the rules here for the naming policy. Just before one of the sheriffs says something to you.

But, to help answer your question - it's certainly one thing you can consider. The goal of the project is to design the system to fulfill the requirements for the cases laid out to you. Given how I wrote mine, I think you're putting too much thought into it, though. It certainly could be something you consider - and I'd comment on it in your design notes - but I don't know if it's something you need to really consider for the project.

[Steve]

Theodore,

Thanks for the suggession!

Steve

[Albert Maurucier]

Steve

Transaction model is one the most important parameter you should take in mind to meet performance and scalability requirements. Use transactions (and keep them short),only when NEEDED, document carefully your choices.

Regards
Albert
SCJP, SCWCD,SCBCD, ICED, SCEA, CCNA.

[Steve]

Albert,

Do you know in general how to do a two phase commit over a http communication? If the transactions are to be performed between databases, we can use JTA. Or if the systems support JMS, the handling of transactions between systems can be easy. But not sure how to invoke an XML-RPC call with a transaction...?

As far as this assignment is concerned, it looks like it is enough if we expalin available options (?)

Thanks,

Steve

[Albert Maurucier]

Steve,

I don't understand why you need a 2PC transaction, is there anything you need to write in the external system? Your request is read only ! the external system reply is "authorized" or "rejected", if authorized you process the sell else you display an authorization failure window (and send email) labeled "authorization rejected".If there is any network failure, you catch it and display an error window.
I don't see any need for a transaction.I think that transactions are needed only when you have conncurrent updates....
If you have an internal error after a successful credit card processing, your system should be able to handle it with any "retry mechanism" or other stuff.The system should be "robust", robustness is an important architectural characteristic.

Regards

Albert
[ October 03, 2005: Message edited by: Albert Maurucier ]

[Steve]

Albert,

Cool thanks for the clarification!

Thanks,

Steve
[ October 03, 2005: Message edited by: Steve ]