反对 ESB、BPM 和 SOAP 等复杂的通讯机制
比较关键
反对 ESB、BPM 和 SOAP 等复杂的通讯机制
比较关键
soa和微服务的区别: https://www.cnblogs.com/xuwc/p/13989081.html
Practically addressing a common problem: working distributed TXs without a 2-phase commit in the SOA world.
How often have we not seen an SOA initiative slowed down by conflicts between service providers and service consumers on what constitutes a good service interface? On the one side a mobile developer just wants it to be simple for their particular app, on the other side the backend team wants everyone to use the same standardized service and data model.
SOA: A stable interface for all consumers
API: Particular API for particular needs