If they would be architectures, then for each of them we would be able to draw a diagram. For each architecture - its own diagram. But if we do that, we'll get the same diagram as for SOA. Because they all are just different packaging option for SOA. Calling them "architectures" misleading and causes a lot of harm. In particular, it prevents many from making rational choice of the architecture for particular task. Instead all of them building microservices - fragile decentralized network of loosely coupled services, one of the hardest to do right variants of the distributed systems.
If they would be architectures, then for each of them we would be able to draw a diagram. For each architecture - its own diagram. But if we do that, we'll get the same diagram as for SOA. Because they all are just different packaging option for SOA. Calling them "architectures" misleading and causes a lot of harm. In particular, it prevents many from making rational choice of the architecture for particular task. Instead all of them building microservices - fragile decentralized network of loosely coupled services, one of the hardest to do right variants of the distributed systems.
yea, that makes sense. I updated the post, thanks for the feedback