Reputation: 11
I've read a lot of articles about monolith vs SOA vs microservices, but I'm still a bit confused about their differences.
For example, If I have an application that gathers the data of multiple services within the company via REST, handles them and then sends them to the frontend, is it using SOA architecture or is it still a monolith?
Can a monolith have multiple services as its data sources?
Upvotes: 1
Views: 149
Reputation: 22679
Let's look at the problem from deployment and elasticity perspectives.
Upvotes: 1
Reputation: 867
Monolith, as the name implies (mono) - usually refers to an architecture where there is one single component. From the little you described - sounds like there are several services (=components), each one with its own responsibility, so sounds like it's not a monolith.
Regarding microservices vs. SOA - indeed in first glance these 2 approaches sound very similar, but when you look into it, there are a few key differences, mostly in terms of the services' scope - in microservices the services are very granular, each one of them has a single purpose. In contrast, in SOA the granularity of the services can vary.
Of course there are more differences, I'd recommend to read this article in DZone (which I recommend in general for architecture topics).
Upvotes: 0