Funky Gao

solve issues when display with terminal color

1

before this fix, the output was not aligned correctly

Wanted: who's using DDDplus

1

## Who is Using DDDplus Thanks sincerely for constantly using and supporting DDDplus. We will try our best to keep DDDplus better, and keep growing community. You can refer to...

[discuss] What do you want in DDDplus 1.2.0

8

The purpose of this issue is to discuss what you think should be added in DDDplus 1.2.0, such as features, bugfixes for known problems, and code refactoring optimizations.

Plugin Jar热更新的业务原子性

1

对于Partner Plugin Jar，一个Partner业务身份可能有几十个Extension，如何保证这些扩展点对一个请求要么全是新jar的，要么全是旧jar的？ 例子： 一个请求，针对某一个业务前台身份，有10个扩展点，现在这个请求执行了3个扩展点，由于热更新，后续的7个扩展点可能就变成了新的业务逻辑。This is the issue 绝大部分场景下，后面7个扩展点突然变成新的逻辑，是没有问题的。 但有些场景下，可能会有问题。 TODO 给出具体problematic scenarios

Plugin hot reload的压测情况

4

https://github.com/dddplus/dddplus-demo ```bash for i in `seq 1000`; do echo "reload isv plugin jar and submit isv order" curl localhost:9090/reload?plugin=isv curl -XPOST localhost:9090/order?type=isv sleep 5 done ```

MQ异步处理后，业务逻辑割裂，代码可读性降低

2

是否可以在DDDplus里解决它？ 复杂业务场景下，经常会使用MQ进行异步的处理。 自己发，自己收的情况很常见。 但业务逻辑被切断了：正在处理一个业务，然后就produce一个message；后面的逻辑会在message consumer处看到，可consumer在哪里？需要找配置文件或其他手段才能找到。 异步方式将本来紧凑的代码都分成两部分：上半场(produce message之前的逻辑)，下半场(message consumer里面的逻辑) 有点数据血缘的味道。 需要研发同学，可以在produce message(上半场)处不必切换快速定位下半场业务逻辑的实现。 #### References - [异步方案之回调的不完美](https://www.jianshu.com/p/3b3563bc62cd)

compatible with native java/scala consumer id registration format

2

in java/scala kafka implementation, the Timestamp of a consumer is string instead of int64

## Who is Using DDDplus Thanks sincerely for constantly using and supporting DDDplus. We will try our best to keep DDDplus better, and keep growing community. You can refer to...

The purpose of this issue is to discuss what you think should be added in DDDplus 1.2.0, such as features, bugfixes for known problems, and code refactoring optimizations.