Is it logical to use a common caching server in microservices?

Question

Programming

Good morning! There is a question about building a framework for a small SAAS service, and I want to break all of its parts into microservices. But the performance will suffer when transferring data, a well-known fact ... And the idea appeared to make a common caching server for everyone, so that if possible they would take information from it, and not make a request to another service. Does such an approach have the right to life? Or should each MS have its own isolated cache? Or is this solved by a message manager like RabbitMQ?