Geek Answers Handbook

Service Oriented Architecture Communication Standards

In the past, I worked on creating a data processing application structured using a service-oriented architecture. I had a series of services that are managed from the main service, which will consistently access all services to process my data.

I came across something that I didn’t like about the fact that the services had to provide information about the status and errors in the master service, and I had to code everything from scratch.

My question is whether there are standards for interservice communications and management. I’m worried about things like message format, error recovery, and status reporting. I am going to rebuild SOA in the future, and I do not want to develop from scratch, but rather agree with a higher standard. I know that some of the answers to my question will be based on my business requirements, however I want to see if there is anything in this first one.

Thank,

Mj

+4
source share
1 answer

ACID transactions when organizing services

, , , / , -. , , , . , , ACID.

, , , - 2PC - 2- . - , , . .

- . 2PC. , , - , , - - . , , / . - ( ) , , .

, , , , , - , "" , CreateUser DeleteUser.

, - -, WS-Coordination, WS-AtomicTransaction WS-BusinessActivity , .

, . , ( , ):

  • - ( , , )

  • Recoverable Error - , , , . : . , .

  • - , , , - , , . . , .

, !

0

More articles:


All Articles