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.
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.
Especially when no one defines these terms the same way, so it's not like I can go and find and compare definitions.
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.
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.