3 ms·

Believe me, I know that microservices suck for almost anything, because of the added software and infrastructure management complexity. And so it is with most

Believe me, I know that microservices suck for almost anything, because of the added software and infrastructure management complexity. And so it is with most other hyped technologies. The complexity and loss of control is very rarely worth it. I'm not a dogmatist, but have seriously tried many different approaches. And that's why I do mostly C (well, not for web applications, which I try to avoid as well :>) with only very simple data structures, and I love it, and it works, and it's maintainable, modular, and very performant. Although I know that C has flaws - I have been trying to find ways to improve (and failed so far).

crdoconnor 9y ago
>Believe me, I know that microservices suck for almost anything woosh They work really well in large organizational environments where inter-team coordination costs are very high and language flexibility is valuable. Where these benefits outweigh the additional infrastructure headaches it works very well. I've likewise worked in environments where they were a terrible idea (e.g. startup team of six). Like you, I used to be dogmatically anti-microservice. I was wrong.
- jstimpfle 9y ago
  Yes - that may be, so I'm sorry for omitting the context that I don't work in large teams where you can throw lots of money and developers at problems. (I think that's a sad state of affairs, though). Again, I'm not dogmatic, but have actually tried it, and I know (and have described in my comment) the problems they bring.
ahmedalsudani 9y ago
It seems to me that you are young and just starting your career. It’s ok to only want to do certain kinds of work (for example C code that runs close to the metal and that is performant and easy to reason about). Other people in the world though enjoy doing different kinds of work and going about it in different ways. My advice to you is to be humble and watch people as if they had something to teach you. Whether they are doing scrum, waterfall, using this or that language or architecture, there’s always a ton of things you can learn by watching how someone works. If you pay closer attention, you will see value in what other people are doing and be able to benefit from what they have discovered.
- deleted 9y ago
  [deleted]

crdoconnor 9y ago

>Believe me, I know that microservices suck for almost anything woosh They work really well in large organizational environments where inter-team coordination costs are very high and language flexibility is valuable. Where these benefits outweigh the additional infrastructure headaches it works very well. I've likewise worked in environments where they were a terrible idea (e.g. startup team of six). Like you, I used to be dogmatically anti-microservice. I was wrong.

jstimpfle 9y ago
Yes - that may be, so I'm sorry for omitting the context that I don't work in large teams where you can throw lots of money and developers at problems. (I think that's a sad state of affairs, though). Again, I'm not dogmatic, but have actually tried it, and I know (and have described in my comment) the problems they bring.

ahmedalsudani 9y ago

It seems to me that you are young and just starting your career. It’s ok to only want to do certain kinds of work (for example C code that runs close to the metal and that is performant and easy to reason about). Other people in the world though enjoy doing different kinds of work and going about it in different ways. My advice to you is to be humble and watch people as if they had something to teach you. Whether they are doing scrum, waterfall, using this or that language or architecture, there’s always a ton of things you can learn by watching how someone works. If you pay closer attention, you will see value in what other people are doing and be able to benefit from what they have discovered.

deleted 9y ago
[deleted]