Software Architecture Patterns

It is a reusable solution to a recurring structural problem, such as how to split a system into services or how components communicate.

SOA typically shares an enterprise service bus and larger services; microservices use smaller, independently deployable services with lightweight communication and decentralised data.

When components must react to changes asynchronously, scale independently or integrate many producers and consumers; see the EDA hub.

The provider manages servers and scaling, and you pay per execution; it suits spiky or event-triggered workloads.

Yes. Many systems use microservices communicating through events and run some components as serverless functions.