blocks|key|93587|text|最好的设计是具有独立的服务:每个服务只在其自己的事务中执行其工作，而您的工作流程预计单个服务会出现故障。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|93588|如果您真的只需要在调用所有服务时都没有错误地提交，那么您应该创建一个更高级别的服务，在外部事务中执行这些调用。|93589|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The best design is having isolated services: each service just do its work within its own transaction and your workflow expects failures on the single service.

If you really need to commit only if all the services are called without errors you should create an higher level service that perform those calls inside an external transaction.

blocks|key|93602|text|在前面答案的基础上，分布式事务是解决方案。在我看来，你不想构建自己的机制来跟踪全局事务状态，相反，你想使用某种产品--有几种。我写了一篇关于用Java应用服务器解决这个问题的长篇博客文章：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|93603|http://blog.maxant.co.uk/pebble/2015/08/04/1438716480000.html|offset|length|93604|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1P|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Building on top of previous answers, distributed transactions are the solution. In my opinion you don't want to build your own mechanisms for tracking global transactional state, rather you want to use some kind of product - there are several out there. I have written a lengthy blog article about solving this issue with a Java application server:

<a href="http://blog.maxant.co.uk/pebble/2015/08/04/1438716480000.html" rel="nofollow">http://blog.maxant.co.uk/pebble/2015/08/04/1438716480000.html</a>

blocks|key|4599769|text|两阶段提交可以是option.Coordinator向cohorts.Cohorts发送提交请求消息，发送回ok.After，然后协调器向cohorts.If发送提交消息，如果发生故障，协调器向队列发送回滚消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4599770|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

two-phase commit can be option.Coordinator send commit request message to cohorts.Cohorts send back ok.After then coordinator sends commit message to cohorts.If any failure happpens coordinator sends rollback messages to cohorts.

blocks|key|4599801|text|您可以使用工作流引擎(如JBPM、Activiti)来编排逻辑并处理其中的事务故障或补偿性事务，以实现数据完整性。这与您在具有ESB、BPMN和Web服务的SOA架构中使用的情况类似|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4599802|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can use a workflow engine(like JBPM,Activiti) to orchestrate the logic and handle transaction failures or compensatory transactions in it to achieve data integrity. This is the similar case you use in SOA architecture with ESB,BPMN and Web services

I have read some articles about microservices architecture, but no one takes the topic of transaction. All that they says that this is hard to do it. Maybe someone can describe how to handle this?

But not from domain side, but from technology side. Lets say that we have business case where we need to invoke two different services and both of them make some changes on database. But how to rollback if some error occurs on the second one?

Who knows some libraries or design patter for this problem?

Transactions in microservices

微服务架构

数据完整性

数据库

服务器

Java

我读过一些关于微服务架构的文章，但没有人讨论事务。他们都说这很难做到。也许有人能描述一下如何处理这件事？但不是从领域方面，而是从技术方面。假设我们有一个业务案例，我们需要调用两个不同的服务，并且这两个服务都对数据库进行了一些更改。但是如果第二个发生错误，该如何回滚呢？谁知道针对这个问题的一些库或设计模式？

问微服务中的事务
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问微服务中的事务EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问微服务中的事务
EN