Reddit reviews Release It!: Design and Deploy Production-Ready Software

I don't believe Microservice-to-Microservice communication is an antipattern. It is a common practice. The only way to avoid it in many cases is to make a monolith. Having services talk to one another does have a cost, so you need to do it sparingly and cautiously. It adds latency, and couples the services such that if one goes down, so does the other, so use appropriate patterns for resiliency. You definitely want to avoid deep chains of calls (Service A calls B that calls C that calls D...etc) as the latency will grow and the risk of failure multiplies with each new dependent call in the chain.

Often, you can reduce the number of service-service calls by consolidating services. The word "micro" in microservices often leads people to build services that are too small and this introduces even more service-service calls. These "nano-services" are indeed an antipattern.