Problems with database separation in microservice architecture

Microservice architecture is often a service with a separate database
So basic public data such as user account information used to be queried by SQL association, but now it can only be called through API. Will this reduce performance and increase unreliability? Sex???
What’s a good solution???

Reply content:

Microservice architecture is often a service with a separate database
So basic public data such as user account information used to be queried by SQL association, but now it can only be called through API. Will this reduce performance and increase unreliability? Sex???
What’s a good solution???

Performance is solved by caching
The reliability of the account application server itself is solved by clustering, because the status is in the database, so clustering is easy
Account storage is solved by clustering of the database itself

These three are also the same things to consider for other microservices