3 ms·

“we have 100 people so require 20 microservices”. More like 3 people requiring 13 microservices

by rqtwteye 4y ago

Spivak 4y ago
I'm convinced that micro-service hell happens when the primary app calcifies and becomes too difficult to modify.
- kqr 4y ago
  What are the specific decisions along this course of events? I guess nobody says "Our primary app has calcified and become too difficult to modify. Let's make microservice hell!" But what do people say that leads down that road, in your experience?
  - justinclift 4y ago
    Pretty sure this would be fairly common: Welcome to your new job as Architect for our software! What are some of the main bullet points you have in mind for our next major release... ?
- rqtwteye 4y ago
  Micro service hell happens with new apps that are designed from scratch.
- deleted 4y ago
  [deleted]
- osigurdson 4y ago
  Micro-services are currently on trend so hard to argue with unless you are a founder. Maybe the best thing to do for the industry in general is go absolutely nuts with microservices. Factor projects so every method is a separate service / lambda. If anyone complains, use the single responsibility principal to snuff out all opposition. Once we've explored this to its logical conclusion the pendulum will swing back to something more logical. Of course, it will swing too far and the cool kids will only want to work on monoliths even when it doesn't make sense (kind of like what is happening now with SQL maximalism).
  - zo1 4y ago
    I got tired of arguing against microservices just like I got tired of arguing against SPAs and multi-repos. And at least with one of them, the pendulum has already started swinging back. The cool-kids (aka "javascript hipster devs") have re-discovered the concept of a monorepo and are pushing for it hard, making it seem like some sort of new concept with fancy tooling. It'd be funny if it wasn't so caricatured and a sad state of our industry.
    - osigurdson 4y ago
      >> re-discovered the concept of a monorepo Monorepo and monolith are somewhat orthogonal. The desire to use a monorepo likely stems from wanting to emulate Google.
  - take-10 3y ago
    [flagged]

“we have 100 people so require 20 microservices”. More like 3 people requiring 13 microservices

Spivak 4y ago

I'm convinced that micro-service hell happens when the primary app calcifies and becomes too difficult to modify.

kqr 4y ago
What are the specific decisions along this course of events? I guess nobody says "Our primary app has calcified and become too difficult to modify. Let's make microservice hell!" But what do people say that leads down that road, in your experience?
- justinclift 4y ago
  Pretty sure this would be fairly common: Welcome to your new job as Architect for our software! What are some of the main bullet points you have in mind for our next major release... ?
rqtwteye 4y ago
Micro service hell happens with new apps that are designed from scratch.
deleted 4y ago
[deleted]
osigurdson 4y ago
Micro-services are currently on trend so hard to argue with unless you are a founder. Maybe the best thing to do for the industry in general is go absolutely nuts with microservices. Factor projects so every method is a separate service / lambda. If anyone complains, use the single responsibility principal to snuff out all opposition. Once we've explored this to its logical conclusion the pendulum will swing back to something more logical. Of course, it will swing too far and the cool kids will only want to work on monoliths even when it doesn't make sense (kind of like what is happening now with SQL maximalism).
- zo1 4y ago
  I got tired of arguing against microservices just like I got tired of arguing against SPAs and multi-repos. And at least with one of them, the pendulum has already started swinging back. The cool-kids (aka "javascript hipster devs") have re-discovered the concept of a monorepo and are pushing for it hard, making it seem like some sort of new concept with fancy tooling. It'd be funny if it wasn't so caricatured and a sad state of our industry.
  - osigurdson 4y ago
    >> re-discovered the concept of a monorepo Monorepo and monolith are somewhat orthogonal. The desire to use a monorepo likely stems from wanting to emulate Google.
- take-10 3y ago
  [flagged]