If anything is trendier than microservices, that is bashing microservices.
Before this comment pool spirals into that, I'll just leave this: It all depends on your project.
Did you have a bad time with microservices? Maybe the implementation was wrong. Maybe the project doesn't fit the model. Heck, maybe the project would STILL be screwed under a monolithic approach. There are so many variables to what classifies a success/failure in the microservice world (like most other things in software development, actually).
What's important is to not have a polarising opinion: "microservices suck", "microservices should be used for everything". Analyse your requirements. Imagine your professional project a few years down the line. Educate yourself on the subject (there are books on the subject!). Make. Sure. It. Fits.
I've personally had successes and losses with microservices, just like I had successes and losses with other architectural styles.
I've taken a middle of the road approach often I've often seen recommended. First build a monolith then split it apart logically when it makes sense. Not really 'micro' but my application with 6 medium components is easier than with one monolith, and easier than 20 micro.
Of course if I go to an interview I'll say I built microservices because it's a buzzword/checkbox.
The thing with microservices is that each one comes with a real cost, an amount of friction that gets contributed to your overall process flow. At some point, this frictive energy becomes intense enough that it jeopardizes the project.
I think "microservices" is a sane architectural pattern for some applications. The problem is that people polarize into one extreme or the other, and many attempts at a microservice implementation that I see would more rightly be classified "nanonservices"; things are broken up, almost at random, into tiny, disjunct, co-dependent pieces. This is a total nightmare scenario, and a monolith would undoubtedly be better.
Before this comment pool spirals into that, I'll just leave this: It all depends on your project.
Did you have a bad time with microservices? Maybe the implementation was wrong. Maybe the project doesn't fit the model. Heck, maybe the project would STILL be screwed under a monolithic approach. There are so many variables to what classifies a success/failure in the microservice world (like most other things in software development, actually).
What's important is to not have a polarising opinion: "microservices suck", "microservices should be used for everything". Analyse your requirements. Imagine your professional project a few years down the line. Educate yourself on the subject (there are books on the subject!). Make. Sure. It. Fits.
I've personally had successes and losses with microservices, just like I had successes and losses with other architectural styles.