(Including event registration) SOFA Weekly | Picks of the Week [5/13 - 5/17]

SOFA WEEKLY | weekly specials, weekly essence screening Q & A

Open source synchronization progress, interactive welcome message

SOFAStack (Scalable Open Financial Architecture Stack) is a gold suit ant self-developed financial level distributed architecture, including the various components needed to build the original class cloud financial architecture students , including micro-services development framework, RPC framework, service registry, distributed regular tasks, limiting / blown framework, dynamic configuration push, distributed link tracking, metrics monitors measure, highly available distributed message queuing, distributed transaction framework, distributed database proxy layer and other components, but also out of temper in the financial scene best practices.

SOFA documents:  https://www.sofastack.tech/

SOFA: https://github.com/sofastack

  Each week Recommended Reading   

• (Including event registration) ants gold dress open source machine learning tools SQLFlow, exclusive interpretation of the technical architecture

• Continued technology - Open | SOFAStack enable independent Group
  

  Reader Q & A refined week  

Welcome to leave a message to the public to ask questions or interact with our number in the group

We will focus on the problem by screening 

Form "SOFA WEEKLY" reply

1、@ Cheng Chun root  question:

Seata only when a local transaction can be used? TC connection is not only a method of local control logic in the transaction.

A: The current design must have a TC, you only do local transactions with Seata will also interact with the TC.

@GlobalLock This is not local affairs?

A: This is a local transaction optimization, in order to allow local non-transactional read the intermediate values ​​distributed transaction operations, to solve the isolation problem of local and distributed transactions.

2, @ Long Heng  question:

相关阅读：分布式事务 Seata TCC 模式深度解析 | SOFAChannel#4 直播整理

之前 TCC 的视频里面有讲到加钱的场景，实际加钱的操作是在 Commit 的时候做的。请问如果这步失败了，我应该让 Commit 继续走完，还是直接抛异常？如果是抛异常的话 Seata 会继续重试 Commit，还是转而去调用 Rollback？

A：如果已经确定是 Commit 了，那就会持续调用 Commit，直至成功。

不知道我理解对不对，Commit 里面如果是遇到非业务逻辑错误，比如数据库连不上，就让他抛异常，让框架不断重试直到成功。但如果是业务逻辑错误，比如账号已经被删了，只能让 Commit先执行完了，因为重试再多也没意义了。

A：是的。

   每周 SOFA 进展  

本周发布详情如下：

1、发布 spring-cloud-sofastack-samples：

spring-cloud-sofastack-samples 是基于 SOFA 和 SpringCloud 构建的一套微服务系统，希望通过此案例工程，提供一个完整的基于 SOFA 和 SpringCloud 体系构建的基础的工程模型，帮助更好的理解和使用 SOFA 开源生态提供的一系列基础框架和组件。

项目地址：

https://github.com/sofastack/spring-cloud-sofastack-samples

项目文档：

https://github.com/sofastack/spring-cloud-sofastack-samples/wiki

2、发布 SOFATracer 3.0.5 版本，主要变更如下：

i. 兼容 openfeign 9.x 版本

详细参考发布报告：

https://github.com/sofastack/sofa-tracer/releases/tag/v3.0.5

  SOFA 活动推荐  

SOFA Meetup # 2 Shanghai Station "Using SOFAStack quickly build micro-services" registration in progress ❤ ~

May 26, SOFAStack open source core members of the collective action. This issue we will focus on the actual scene of each floor were resolved architecture.

Detailed Seata distributed transaction, the integration of Case and Spring Cloud ecology, use SOFAStack quickly build micro service Demo practical operation, more recent open source "Let AI like SQL simple - SQLFlow Demo" the first show, and look forward with you there or be square ~

| Registration

Click "read the original" you can register.

| Events Details

See times Tweet introduction.