Hi Mike. Great piece! As someone who has really only worked with monoliths, I struggle to see the value of microservices over monoliths. On paper, I'm sold on the idea of the microservice architecture. But when the rubber hits the road, it seems like the complexities introduced by the microservice architecture, e.g., service discovery, security, and the introduction of an orchestrator like kubernetes, really over complicate the majority of applications.
Thanks for reading! I really appreciate it. Yeah, there are definitely pros and cons to each. I feel like in today's world, a lot of people try to sway towards the idea of "microservices for all!", but sometimes it's simply not needed.
I would say the biggest thing for me is pushing features and updates. It's nice that microservices allow you to do it piece by piece, vs a monolith you're kind of stuck updating it all. That's the biggest "pro" for me.
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.
Hi Mike. Great piece! As someone who has really only worked with monoliths, I struggle to see the value of microservices over monoliths. On paper, I'm sold on the idea of the microservice architecture. But when the rubber hits the road, it seems like the complexities introduced by the microservice architecture, e.g., service discovery, security, and the introduction of an orchestrator like kubernetes, really over complicate the majority of applications.
Hey Paul,
Thanks for reading! I really appreciate it. Yeah, there are definitely pros and cons to each. I feel like in today's world, a lot of people try to sway towards the idea of "microservices for all!", but sometimes it's simply not needed.
I would say the biggest thing for me is pushing features and updates. It's nice that microservices allow you to do it piece by piece, vs a monolith you're kind of stuck updating it all. That's the biggest "pro" for me.