[geezerjay]

> I'm not disagreeing but the reason SOA is more complex is that it does a whole lot more than "REST" microservices. It encompasses standardized protocols for transactions, faults, asynchronous services, auth, and more, in addition to payload typing and state.

"REST" microservices also do that, but they aren't bound to quasi-proprietary protocols and tooling.

[tannhaeuser]

How does "REST" handle coordinated transaction rollback/compensation over multiple heterogenous service calls? How is SOAP, XML, WS-*, AMQP proprietary?

[geezerjay]

> How does "REST" handle coordinated transaction rollback/compensation over multiple heterogenous service calls?

By "REST" I assume you're referring to non-SOA distributed systems which might happen to use REST or RPC-over-HTTP interfaces, and not the architecture style.

Assuming that, "REST" handles all those features by integrating services that support coordinated transaction rollback/compensation over multiple heterogenous service calls.

> How is SOAP, XML, WS-*, AMQP proprietary?

If you read what I said you'll notice that I explicitly said "quasi-proprietary protocols and tooling".

[tannhaeuser]

I fail to see how your post answers anything.