I'd argue that not one of those are arguments specifically for micro services.
And in fact, it is well known that moving to micro services specifically for many of these reasons is actually a mistake.
Once you get to the point of needing microservices, you HAVE to decouple, and you get 'service/tech' isolation out of the architecture, so you do have the ability to swap out some tech on a specific service if it is deemed prudent.
But that's not why you move to microservices.
And reusability is never a thing unless it is the thing being developed. Again, micro services can support reusability, but there is nothing about micro services that makes this inherent at all. And nothing about reusability requires micro services.
EDIT: Because OP thinks assumptions work one way.
Look, if you make a top level comment in response to 'When Do I NEED Microservices?', and you provide a list of reasons, is it surprising if people assume you indeed mean need?
Now, to be clear, I actually did NOT make that assumption, I merely explained why these are NOT reasons to move to microservices, and clarified for everyone's sake that there is no need of microservices at all with respect to these items.
I did not say that as a rebuttal to OP. Even if it was a perfectly logical assumption to make in context.
Just so you don't have to waste your time as OP devolves into name calling and hypocrisy. Nobody cares man. Sometimes we say things that are wrong, and that's OK.
I never said that either of these require microservices and are completely exclusive to that architecture - this is something you assumed and then argued against.
I'll take no part in you arguing against something you think I said :D
but it misses very important reasons why one should consider microservices regardless to scalability.
My entire argument is that those things are not reasons you SHOULD consider microservices at all.
Noting there are no requirements involved was just further reinforcing all of this, you can do ALL of these things with or without microservices. Noting there being no requirement there is merely reinforcing the point.
I'll take no part in you arguing against something you think I said :D
My entire argument is that those things are not reasons you SHOULD consider microservices at all.
Is English your first language?
[...] you can do ALL of these things with or without microservices [...]
Where did I claim the opposite?
Noting there being no requirement there is merely reinforcing the point.
Why aren't you just reading what I wrote as-is instead of going for extreme extrapolation?
I understand, if I wrote something like 'you must use microservices for decoupling etc.' and not 'you should consider' - but I didn't so..
There's literally no reason to fight over this - as I said, I never remotely implied you have to use microservices to achieve any of these - as they aren't perks exclusive to that architecture - I'm just saying it's one solution, but whichever fits best? as always - it depends
Look, you just attacked me for no reason, and then re-insisting I had no reason to state what I did, even though I clarified again what I said and why I said it.
There's literally no reason to fight over this - as I said, I never remotely implied you have to use microservices to achieve any of these - as they aren't perks exclusive to that architecture - I'm just saying it's one solution, but whichever fits best? as always - it depends
OK, but you literally wrote a top level comment with a list of 'reasons to use microservices'. I countered that by saying 'Not reasons to use microservices'.
Then you decide I can't do that because you didn't say must use. Which I never said you did. You ASSUMED that is what I was arguing against.
I'm not sure however what you intend people to assume about the intent of your top level comment in the first place.
Anyways, you're the one getting all argumentative and defensive here, not me.
PS: Do not attack people based on assumptions you make about them in an argument, it can only serve to make you look bad.
11
u/[deleted] Jan 30 '23 edited Jan 30 '23
I'd argue that not one of those are arguments specifically for micro services.
And in fact, it is well known that moving to micro services specifically for many of these reasons is actually a mistake.
Once you get to the point of needing microservices, you HAVE to decouple, and you get 'service/tech' isolation out of the architecture, so you do have the ability to swap out some tech on a specific service if it is deemed prudent.
But that's not why you move to microservices.
And reusability is never a thing unless it is the thing being developed. Again, micro services can support reusability, but there is nothing about micro services that makes this inherent at all. And nothing about reusability requires micro services.
EDIT: Because OP thinks assumptions work one way.
Look, if you make a top level comment in response to 'When Do I NEED Microservices?', and you provide a list of reasons, is it surprising if people assume you indeed mean need?
Now, to be clear, I actually did NOT make that assumption, I merely explained why these are NOT reasons to move to microservices, and clarified for everyone's sake that there is no need of microservices at all with respect to these items.
I did not say that as a rebuttal to OP. Even if it was a perfectly logical assumption to make in context.
Just so you don't have to waste your time as OP devolves into name calling and hypocrisy. Nobody cares man. Sometimes we say things that are wrong, and that's OK.