Terminology: why are containers called microservices?

Question

Service Oriented Architecture

When reading various literature and articles on the topic of microservice architecture and docker, I got confused with terminologies.

As I understand it, a microservice is a regular service that solves one small task. A microservice can consist of either a single container or multiple containers (if containers are used).

If I'm wrong, please correct me.

In many articles, they write that a container is a microservice.
Is a separate container (like pure nginx) really a microservice?

Answer 1

No, a container can contain both a monolith and a group of services, but this is "not accepted in a decent society."
Containerization challenge - runtime repeatability and isolation
Microservices challenge - contract access isolation and independent development/deployment cycle

Answer 2

A microservice is an element of architecture.
The container is its implementation.
In 90% of cases, a microservice is implemented through a container, and in 80% of cases, a container implements a microservice. Therefore, among the people, these concepts have merged (like statistics and statistical data).

Answer 3

As I understand it, a microservice is a regular service that solves one small task. A microservice can consist of either a single container or multiple containers (if containers are used).

Yes,
just the terminology is a little misleading, they usually say not a microservice, but a microservice architecture, that is, such a service architecture in which the service consists of many independent nodes that you can independently develop and deploy, without the need for changes in other nodes. how many nodes themselves and their size is no longer so important.