Agreed with your perspective. Microservices are very attractive on paper but it also comes with a cost. If you have more than 3 services per developers I think you'll start to see some new pains emerging (testing, monitoring, restoring a new stack, managing dependencies, feature flags...).
I would recommend not diving too far too fast, moving a few isolated components out of the monolith (auth or audit logs can be good candidates) will help understand the new practices to adopt.
There are great benefits to embracing Microservices and I'm a huge proponent of it. Just make sure you go at your own pace, it took Netflix years to get to the level of maturity they have.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Agreed with your perspective. Microservices are very attractive on paper but it also comes with a cost. If you have more than 3 services per developers I think you'll start to see some new pains emerging (testing, monitoring, restoring a new stack, managing dependencies, feature flags...).
I would recommend not diving too far too fast, moving a few isolated components out of the monolith (auth or audit logs can be good candidates) will help understand the new practices to adopt.
There are great benefits to embracing Microservices and I'm a huge proponent of it. Just make sure you go at your own pace, it took Netflix years to get to the level of maturity they have.