We move to microsevice architecture to improve our web performance, Is that make sense?

No.

It would make more sense to drop the bloated and useless crap that you are using.

It does, with enough growth and usage the monolith can only absorb so much before falling over.

You can scale horizontally all you want but then you have a monolithic expense to go with it 😅

Depends. If you have nice architect that can build your infastructre beautifully with proper load balancing and scaling, yes you can increase performance. It may cost more money with resources. But there is two great factors in performance: dev and language. If your team doesn't know shit about writing efficient code, your apps performance will suffer greatly. If you develop with interpreted languages like php, node, python you may use much more resources to handle heavy load. So micro service architecture is nothing magical that speed ups your app. You cant expect increase in performance if you just divide your code base into smaller projects and using same server resources.

Microservice architecture has the goal to create a cluster of many small applications. Small to be replaceable - to minimalize the effect of technical debt / aging software.

Instead of refactoring stuff, rewrite it.

The cost is an overhead of communication between the applications.

As @hack pointed out, the question is now wether you incorporate that factor in your design decisions for the applications and the hardware / network.

Non blocking requests through async / threading, utilizing e.g. message queues for communication, properly setting up the loadbalancers (e.g. by assuring basic stuff like keepalive works / TLS caches / ...), reducing overhead by proper design of API endpoints (like in SQL, sending 2 MB of text instead of the necessary 1 KB is bad idea TM), evaluating alternative protocols (e.g. GRPC) et cetera et cetera et cetera.

So no. It's not a magical silver bullet.

Quite the opposite, in the wrong hands it's a sure way to create a slowtastic hell. :) (Microservices consisting of a cluster of monolithic applications are a thing and it's terrifying).

@IntrusionCM "Microservices consisting of a cluster of monolithic applications are a thing and it's terrifying", did you mean distributed monolith :)

No. Generaly you wouldn't ask if you really needed that approach. Tradeoff isn't worth it in most cases.

@BimaAdi yeah... Whatever you want to call that monstrosity. XD

microservices is meant to scale the people, not the performance.