5 ms·

Lots of shallow dismissals in the comments for this and it seems to be a trend every time microservices come up. "N Microservices for $BUSINESS_DOMAIN ? Crazy!

Lots of shallow dismissals in the comments for this and it seems to be a trend every time microservices come up. "N Microservices for $BUSINESS_DOMAIN ? Crazy!" Can't we just taka it on good faith that the engineers who do these blog posts have at least a modicum of competence and therefore their solution has _some_ merit (that is worth discussing) rather than just "Micro-services bad" dismissals? <sideshow bob>Yes I realise this can also be taken as a shallow dismissal of the shallow dismissals</sideshow bob>

deleted 7y ago
[deleted]
altmind 7y ago
>> Can't we just taka it on good faith that the engineers who do these blog posts have at least a modicum of competence and therefore their solution has some merit On a technical resource, no. In a technical article, technical points need to be explained. Decisions need to be checked. Unless your argument is "it cannot be bad because it must have been checked by many people", we are totally in the position to provide any sort of constructive feedback.
- rurounijones 7y ago
  If you want to give constructive feedback then have at it. My comments were aimed at the shallow dismissals at the level to which I gave an example (and examples of which can be found in the comments on this post). If a response to these articles is along the lines of "OMG they are using microservices, BAD!" then that is not constructive or useful unless you are trying to invoke Cunningham's Law (Or whatever the one was about getting help on a linux mailing list by saying something cannot be done).
  - deleted 7y ago
    [deleted]
kortilla 7y ago
No, it’s a blog post about running a cutting edge technology in production. Whether or not fundamental decisions were made correctly is vey much in play.
- rurounijones 7y ago
  The blog post is about "Running Istio in production". Not "Why we chose to run istio in production" so I don't think "they shouldn't be running istio in production" it is in scope. _However_ if you want to have a constructive discussion about if isio is even the right choice here then have at it if you think there is enough info to go into that. (Personally I don't think there is enough info in the blog post to have that discussion... since that is not the point of the blog). Again, my comment was mainly aimed at the shallow 1-sentence dismissal comments that crop up on these posts.
  - kortilla 7y ago
    Of course it’s in scope, it’s an unproven technology that’s still quite immature. It’s the same as the “Hadoop tips” posts back in the day where people would rightfully point out that Hadoop was a bad choice for the sample problem.

deleted 7y ago

[deleted]

altmind 7y ago

>> Can't we just taka it on good faith that the engineers who do these blog posts have at least a modicum of competence and therefore their solution has some merit On a technical resource, no. In a technical article, technical points need to be explained. Decisions need to be checked. Unless your argument is "it cannot be bad because it must have been checked by many people", we are totally in the position to provide any sort of constructive feedback.

rurounijones 7y ago
If you want to give constructive feedback then have at it. My comments were aimed at the shallow dismissals at the level to which I gave an example (and examples of which can be found in the comments on this post). If a response to these articles is along the lines of "OMG they are using microservices, BAD!" then that is not constructive or useful unless you are trying to invoke Cunningham's Law (Or whatever the one was about getting help on a linux mailing list by saying something cannot be done).
- deleted 7y ago
  [deleted]

kortilla 7y ago

No, it’s a blog post about running a cutting edge technology in production. Whether or not fundamental decisions were made correctly is vey much in play.

rurounijones 7y ago
The blog post is about "Running Istio in production". Not "Why we chose to run istio in production" so I don't think "they shouldn't be running istio in production" it is in scope. _However_ if you want to have a constructive discussion about if isio is even the right choice here then have at it if you think there is enough info to go into that. (Personally I don't think there is enough info in the blog post to have that discussion... since that is not the point of the blog). Again, my comment was mainly aimed at the shallow 1-sentence dismissal comments that crop up on these posts.
- kortilla 7y ago
  Of course it’s in scope, it’s an unproven technology that’s still quite immature. It’s the same as the “Hadoop tips” posts back in the day where people would rightfully point out that Hadoop was a bad choice for the sample problem.