3 ms·

I work on a monolith and deploy 20+ times per day to production, sometimes 100+ times depending on the day. weird that you’d say benefit of microservices is tha

I work on a monolith and deploy 20+ times per day to production, sometimes 100+ times depending on the day. weird that you’d say benefit of microservices is that you can do 5 deployments daily to production, that would not make my top-100 list to use them

simianwords 9mo ago
how many developers work on your monolith?
- IshKebab 9mo ago
  It surely doesn't matter if you're using CI/CD?
  - simianwords 9mo ago
    Of course it does. Imagine you wrote code and someone is deploying it. You need to be there to monitor it and make sure nothing breaks. Unless you guard everything with a feature flag which is not effective all the time.
    - IshKebab 9mo ago
      Err yeah well don't add it to the merge queue on a Friday afternoon!
- bdangubic 9mo ago
  29
zmmmmm 9mo ago
From the way you state it, it sounds like you have sole control and discretion over the deployments. Which is kind of exactly the point. Suppose there was another person also with top level responsibilty telling you not to do that? It might be fine for your code, but they don't want their code doing that. My guess is 5 minutes later you'd have started a project to carve your code out from theirs so you could deploy it independently.
- bdangubic 9mo ago
  > you have sole control and discretion over the deployments. I do not have sole control, every member of the team does > Suppose there was another person also with top level responsibility telling you not to do that? Would quit in two seconds if I had to work in a place like this
  - zmmmmm 9mo ago
    well, that's kind of just a more extreme version of "5 minutes later you'd have started a project to carve your code out from theirs so you could deploy it independently" isn't it? For people without the luxury of resigning their job at a moment's notice being an option, this is the next best thing.
    - bdangubic 9mo ago
      > you could deploy it independently what exactly does this mean? you work on a team, team is responsible for the product. there is nothing "independent" about it. everyone does their job, everyone deploys to production. if you are at any place where "deploying to production" is an "event" then for sure I would advice either leave or if that is not an option work towards this goal. there should be no one on the team that can't "deploy to production" and there shouldn't really be anything "independent" thing going on in my opinion. I see a whole lot of discussion and struggles around this though...
      - zmmmmm 9mo ago
        I can believe in certain domains things can work this way, but we have way too many complex stakeholders and dependencies to have random deploys to production constantly happening without notice by anybody who feels like it. At very least there is comms, stakeholder signoff, etc. How would you have eg: customer support staff able to operate if the very button they are telling the customer to press disappears or changes its text during the call?

simianwords 9mo ago

how many developers work on your monolith?

IshKebab 9mo ago
It surely doesn't matter if you're using CI/CD?
- simianwords 9mo ago
  Of course it does. Imagine you wrote code and someone is deploying it. You need to be there to monitor it and make sure nothing breaks. Unless you guard everything with a feature flag which is not effective all the time.
  - IshKebab 9mo ago
    Err yeah well don't add it to the merge queue on a Friday afternoon!
bdangubic 9mo ago
29

zmmmmm 9mo ago

From the way you state it, it sounds like you have sole control and discretion over the deployments. Which is kind of exactly the point. Suppose there was another person also with top level responsibilty telling you not to do that? It might be fine for your code, but they don't want their code doing that. My guess is 5 minutes later you'd have started a project to carve your code out from theirs so you could deploy it independently.

bdangubic 9mo ago
> you have sole control and discretion over the deployments. I do not have sole control, every member of the team does > Suppose there was another person also with top level responsibility telling you not to do that? Would quit in two seconds if I had to work in a place like this
- zmmmmm 9mo ago
  well, that's kind of just a more extreme version of "5 minutes later you'd have started a project to carve your code out from theirs so you could deploy it independently" isn't it? For people without the luxury of resigning their job at a moment's notice being an option, this is the next best thing.
  - bdangubic 9mo ago
    > you could deploy it independently what exactly does this mean? you work on a team, team is responsible for the product. there is nothing "independent" about it. everyone does their job, everyone deploys to production. if you are at any place where "deploying to production" is an "event" then for sure I would advice either leave or if that is not an option work towards this goal. there should be no one on the team that can't "deploy to production" and there shouldn't really be anything "independent" thing going on in my opinion. I see a whole lot of discussion and struggles around this though...
    - zmmmmm 9mo ago
      I can believe in certain domains things can work this way, but we have way too many complex stakeholders and dependencies to have random deploys to production constantly happening without notice by anybody who feels like it. At very least there is comms, stakeholder signoff, etc. How would you have eg: customer support staff able to operate if the very button they are telling the customer to press disappears or changes its text during the call?