询问有关服务器、图像和MT模式的问题

1, server abstraction into a service, but brought the consumption of rpc, why give up embedded in the application? // 1、server抽象成服务，但是带来了rpc的消耗，为什么放弃 嵌入在应用呢？ Can you tell the pros and cons of the selection? // 能否告知选型的利弊？

2, on the beforImage and afterImage, the framework in the implementation of the actual implementation of the update, select for update [previously according to the update conditions, the next time according to the primary key]. This should be strictly required in the sql generated for the business. Otherwise it is easy to bring the problem of deadlock. I hope that the later documents will be more abundant. // 2、关于beforImage和afterImage，框架 在执行真正执行update时，先后都 select for update【前一次根据更新条件，后一次根据主键】。 这样在对业务生成的sql上面应该是需要有严格的要求的吧。否则很容易带来死锁的问题吧。希望后期文档能更丰富一点

// 3, now open source is AT mode, MT mode is temporarily not supported, when will open source? // 3、现在开源的是AT模式，MT模式暂时不支持，啥时候会开源呀？

//

原提问者GitHub用户xuyang0902