3 ms·

Counterpoint: anyone who suggests the number of microservices should correlate to the number of developers should be fired instantly.

• marcosdumay 5y ago
  Wait, what? Are you suggesting that the number of developers does not place a maximum cap on the complexity of your infrastructure? Because if what you are saying is that nobody should ever get near that cap, so it should be theoretical only, that still supports a correlation.
  • natpalmer1776 5y ago
    Six full time developers who wrote 15 microservices that each do one thing well should not be fired. The burden of microservices lies in the underlying infrastructure required to host them. So, assuming we have a competent infrastructure engineer, devops engineer, security engineer, site-reliability engineer, and a handful of other hats being done well... your six developers can write and maintain far more than 15 microservices assuming that each service has a clearly defined single-objective scope. Because infrastructure complexity <> Software development complexity.
  • Chris2048 5y ago
    How does "number of microservices" correlate to "complexity of your infrastructure"? I'd also note that the OP had no concept of time in it - it didn't include a timeframe, so we aren't capped by developer man/work-hours. If we are talking instantaneous support, there is no telling how this correlates - one complex microservice may be too complex for many devs, or many microservices simple enough o be supported by just one. If we are talking about about either development hours, or code-familiarity, then I'm not sure how we are capped - are we going to limit the number of LoC a dev can write, repos they commit too etc, as well?
    • marcosdumay 5y ago
      > I'd also note that the OP had no concept of time in it Oh, ok. Point taken. This alone invalidates everything I wrote.