[PH95VuimJjqBqy]

SOA is a specific architecture, not a generic pattern name.

It implies things such as an ESB, etc. microservice is a distinct architecture.

[jen20]

Microservices is what you get when you couple the four views explained in the "4+1 architectural view model" paper. Nothing more, nothing less. It's a bad idea, typically.

[miroljub]

You can do SOA without an ESB. You don't have to use ESB everywhere to have SOA architecture.

[PH95VuimJjqBqy]

That's true but SOA without an ESB is a very small solution. As that solution grows an ESB will be created whether or not the team thinks of it as an ESB.

[miroljub]

When you need an ESB, you can add one to the mix, but it still doesn't mean that you should use it for everything, even if it's not needed.

[PH95VuimJjqBqy]

I agree with that, I'm just pointing out that ESB is a mainstay of SOA but not microservices. The idea that SOA and microservices is the same is a common misconception borne from the idea that SOA is a generic pattern rather than a specific architectural philosophy.

[pjmlp]

Thankfully there are ESB like solutions for microservices. /s