5 ms·

> So far in the article, I’ve been using service-oriented and microservices as interchangeable terms. They are the same thing, I believe Micro services and SOA

by cygned 5y ago

> So far in the article, I’ve been using service-oriented and microservices as interchangeable terms. They are the same thing, I believe Micro services and SOA are actually different things, despite sharing similarities. > however microservices term does lead some to believe each service to be micro in size Yeah, the name is actually a bad one.

gtoprak 5y ago
> Micro services and SOA are actually different things, despite sharing similarities. Fair point. Looking back, I think I should've made it clearer, what I was trying to convey there was for the sake of this article I was using them as similar paradigms of design. However, as you've pointed out they are not the same thing.
slver 5y ago
Saying they're different, but not saying how (according to you) is honestly not very useful. Especially when no one defines these terms the same way, so it's not like I can go and find and compare definitions.
- IshKebab 5y ago
  It's as bad as REST.
  - deleted 5y ago
    [deleted]
ajsharp 5y ago
100%. One of the most important elements of executing SOA successfully is where you draw service boundaries. Microservices (as the name implies) encourages you to make your services very small, which often/usually has the effect of drawing very poor service boundaries. Finding the right service boundaries has everything to do with domain design and nothing to do with size.
jayd16 5y ago
>Micro services and SOA are actually different things, despite sharing similarities. What would you say the differences are? In my mind, its mostly SOA with the idea that there's no lower bounds on service size. I do agree that people mistake that meaning microservices have an upper bound in size.
BerislavLopac 5y ago
Microservices are (a form of) SOA; but SOA does not necessarily mean microservices. The term "microservices" is not as much bad as misunderstood (which, in a way, means that it is bad): it is commonly believed that it implies each service to be "micro" in the size of the codebase. In fact the "micro" refers to the responsibilities/functionalities a service is supposed to provide. Of course, that is more difficult to measure, as the service boundaries are often not obvious.

by cygned 5y ago

gtoprak 5y ago

> Micro services and SOA are actually different things, despite sharing similarities. Fair point. Looking back, I think I should've made it clearer, what I was trying to convey there was for the sake of this article I was using them as similar paradigms of design. However, as you've pointed out they are not the same thing.

slver 5y ago

Saying they're different, but not saying how (according to you) is honestly not very useful. Especially when no one defines these terms the same way, so it's not like I can go and find and compare definitions.

IshKebab 5y ago
It's as bad as REST.
- deleted 5y ago
  [deleted]

ajsharp 5y ago

100%. One of the most important elements of executing SOA successfully is where you draw service boundaries. Microservices (as the name implies) encourages you to make your services very small, which often/usually has the effect of drawing very poor service boundaries. Finding the right service boundaries has everything to do with domain design and nothing to do with size.

jayd16 5y ago

>Micro services and SOA are actually different things, despite sharing similarities. What would you say the differences are? In my mind, its mostly SOA with the idea that there's no lower bounds on service size. I do agree that people mistake that meaning microservices have an upper bound in size.

BerislavLopac 5y ago

Microservices are (a form of) SOA; but SOA does not necessarily mean microservices. The term "microservices" is not as much bad as misunderstood (which, in a way, means that it is bad): it is commonly believed that it implies each service to be "micro" in the size of the codebase. In fact the "micro" refers to the responsibilities/functionalities a service is supposed to provide. Of course, that is more difficult to measure, as the service boundaries are often not obvious.