One opinion that I have is that the CAP Theorem is fundamentally bad and just not useful. Whenever people use the CAP Theorem to justify design decisions, I think often they are either misinterpreting what CAP is actually saying, or stating the obvious in a way.
decentralization not cryptocurrencies
these cryptocurrencies are actually still extremely centralized, in the sense that if you want to make a Bitcoin transaction, you have to make it on the Bitcoin network — you have to use the network of Bitcoin, so everything is centralized on that particular network
相比较发送data，不如将相关的state snapshots进行发送，进行重建
event source部分
use whatever is the simplest
同一个event被不同的consumer进行消费，如何确保大家都消费，状态的同步更新？
Ideally, what you want is what we would call “causal consistency” across these different storage systems.
with a consistent point-in-time snapshot across both the search index and the cache and the database. 利用snapshots来保证，对外提供服务，一直是一个snapshots部分，而非真正的服务主体？
扩展的来讲，这块涉及到mcc，多版本一致性控制
hide details部分，同不同services对其操作的不一致性相矛盾，这样event sourcing的优势就体现出来了
You can get your passport number, then you can change it, and you need to prove that you changed it, and that you are the same person.
最终一致性部分，保证多久的一致性部分？而不在乎当时当地100%的一致