Microservices that are especially small or fine-grained are called nanoservices. A nanoservices pattern is really an anti-pattern.

In the case of nanoservices, overheads such as communication and maintenance activities outweigh its utility. Nanoservices should be avoided. An example of a nanoservices (anti-) pattern would be creating a separate service for each database table and exposing its CRUD operation using events or a REST API.