2phase-commit | 易学教程

XA Two Phase Commit and execution in Prepare Phase?

阅读更多关于 XA Two Phase Commit and execution in Prepare Phase?

问题 I am trying to understand two-phase-commit and it is not clear to me when each local site executes its portion of the distributed transaction. Does that happen before the prepare messages are sent. That is does it happen before the two-phase-commit xa protocol is even run? Or does each site executes its portion of the distributed transaction after receiving the prepare message, meaning the prepare message itself also includes the transaction query to be executed? 回答1: Yes, execution happens

Why is 2-phase commit not suitable for a microservices architecture?

阅读更多关于 Why is 2-phase commit not suitable for a microservices architecture?

问题 I've read a post saying that: We can not implement traditional transaction system like 2 phase commit in micro-services in a distributed environment. I agree completely with this. But it would be great if someone here can explain the exact reason for this. What would be the issues I'm going to face if I'm implementing 2-phase commit with microservices? Thanks in advance 回答1: The main reason for avoiding 2-phase commit is, the transaction co-ordinator is a kind of dictator as it tells all

Two-phase commit (2PC) configuration with Atomikos

阅读更多关于 Two-phase commit (2PC) configuration with Atomikos

问题 I am creating a sample application to test two-phase commit (2PC). I have taken the code bits used here from the Internet. I am using Spring, Hibernate and Atomikos with MySQL as the backend. I am using two databases and deliberately making the call to the second database fail to check whether the first database call gets rolled back. Sadly it doesn't seem to work. Can some one point me to some links with some sample code? Following is my configuration: The Hibernate session factories: <bean

If I access UserTransaction does this mean that I use 2 phase commit or XA?

阅读更多关于 If I access UserTransaction does this mean that I use 2 phase commit or XA?

问题 UserTransaction ut=lookup.... ut.beginTransaction(); saveToFooDB(); statelessEjb.transactionSupportedMethod(); //saves something to the Foo DB saveToFooDB(); ut.commit(); If i was doing the above then my understanding is that it is not an XA transaction as it doesn't span across multiple resources (like DB plus JMS). Is my understanding correct? 回答1: Data source can be configured of two kinds: XA : these datasource can participate in distribute transactions Local : also called non-XA, they

How to wait during SELECT that pending INSERT commit?

阅读更多关于 How to wait during SELECT that pending INSERT commit?

问题 I'm using PostgreSQL 9.2 in a Windows environment. I'm in a 2PC (2 phase commit) environment using MSDTC. I have a client application, that starts a transaction at the SERIALIZABLE isolation level, inserts a new row of data in a table for a specific foreign key value (there is an index on the column), and vote for completion of the transaction (The transaction is PREPARED). The transaction will be COMMITED by the Transaction Coordinator. Immediatly after that, outside of a transaction, the

How to do 2 phase commit between two micro-services(Spring-boot)?

阅读更多关于 How to do 2 phase commit between two micro-services(Spring-boot)?

问题 I Have two mico-serives A and B where they connect to seperate database, From Mico-serives A i need to persist(save) objects of both A and B in same transtation how to achive this. I am using Spring micro-servies with netflix-oss.Please give suggestions on best way to do achive 2 phase commit. 回答1: you can not implement traditional transaction system in micro-services in a distributed environment. You should you Event Sourcing + CQRS technique and because they are atomic you will gain

Using both graph db and document db

阅读更多关于 Using both graph db and document db

问题 I'm considering a setup where I have entities stored both in a document db (e.g. CouchDB) and a graph db (e.g. Neo4j). The rationale is storing each entity information (data, blobs, values, complex internal structure) in the document db while storing the entity relations (parents, children, associated entities) in the graph db. Has anyone done / seen / been bitten by a setup like this? What kind of issues should I expect? First thing that come to mindaka the 2-phase commit. But backups are

Two-phase commit (2PC) configuration with Atomikos

阅读更多关于 Two-phase commit (2PC) configuration with Atomikos

I am creating a sample application to test two-phase commit (2PC). I have taken the code bits used here from the Internet. I am using Spring, Hibernate and Atomikos with MySQL as the backend. I am using two databases and deliberately making the call to the second database fail to check whether the first database call gets rolled back. Sadly it doesn't seem to work. Can some one point me to some links with some sample code? Following is my configuration: The Hibernate session factories: <bean id="sessionFactory1" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"> <property name

How to do 2 phase commit between two micro-services(Spring-boot)?

阅读更多关于 How to do 2 phase commit between two micro-services(Spring-boot)?

I Have two mico-serives A and B where they connect to seperate database, From Mico-serives A i need to persist(save) objects of both A and B in same transtation how to achive this. I am using Spring micro-servies with netflix-oss.Please give suggestions on best way to do achive 2 phase commit. you can not implement traditional transaction system in micro-services in a distributed environment. You should you Event Sourcing + CQRS technique and because they are atomic you will gain something like implementing transactions or 2PC in a monolithic system. Other possible way is transaction-log

Using both graph db and document db

阅读更多关于 Using both graph db and document db

I'm considering a setup where I have entities stored both in a document db (e.g. CouchDB) and a graph db (e.g. Neo4j). The rationale is storing each entity information (data, blobs, values, complex internal structure) in the document db while storing the entity relations (parents, children, associated entities) in the graph db. Has anyone done / seen / been bitten by a setup like this? What kind of issues should I expect? First thing that come to mindaka the 2-phase commit. But backups are problematic too here. You may check out the book " Seven DBs in Seven Weeks ". 8th chapter talks about