hehe, the resume thing was a joke.
But, yes, I agree, not all monolithic-microservice hybrid, especially if they are 'planned' to be monolithic-microservice hybrid.
Though in my experience, I find many people jump fully into microservices simply because "Netflix" and every dev influencer/bloggers says to do it but then run into to two(of many) fundamental problems:
The organizations devops cannot support it (as you mentioned)
There is no real business need. Thus no justification on the increase spending. I think this is a major factor often glossed over due to the 'proper approach at all costs' for clicks approach taken by many dev influencers.
and leads to ad-hoc substations and all sorts of other shenanigans and the original intent of converting to a microservice architecture is lost.
Really? Because I have already seen job offers that demand 10+ years of experience with microservices... :)
Planning is difficult. The world of IT changes rapidly, how to plan for things no one could even foresee? Only open-to-extension, modular, and loosely coupled architecture can help.
Exactly, need to be cool, need to do something just because the sharks from Silicon Valley do. This will barely bring any success.
Understanding is the key. Solve a problem you actually have.
Microservices have their use-cases and benefits. But they are no silver bullet.
Thanks for your comments!
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.
hehe, the resume thing was a joke.
But, yes, I agree, not all monolithic-microservice hybrid, especially if they are 'planned' to be monolithic-microservice hybrid.
Though in my experience, I find many people jump fully into microservices simply because "Netflix" and every dev influencer/bloggers says to do it but then run into to two(of many) fundamental problems:
and leads to ad-hoc substations and all sorts of other shenanigans and the original intent of converting to a microservice architecture is lost.
Really? Because I have already seen job offers that demand 10+ years of experience with microservices... :)
Planning is difficult. The world of IT changes rapidly, how to plan for things no one could even foresee? Only open-to-extension, modular, and loosely coupled architecture can help.
Exactly, need to be cool, need to do something just because the sharks from Silicon Valley do. This will barely bring any success.
Understanding is the key. Solve a problem you actually have.
Microservices have their use-cases and benefits. But they are no silver bullet.
Thanks for your comments!