4 ms·

Can your "facade" "isolate" interns making change in your service as well so that the whole service which powers the system doesn't go down. Microservices can.

ahtihn 3y ago
You let interns push to production without code review?
- prakhar897 3y ago
  Totally missed the point. Even with Code reviews, Unit/Integration Testing, Automated CI/CD and more can a person broke the prod. One intern was told to deploy the app and I guess he made a mistake and updated k8 configs which deleted all the pods. Tell me how code reviews are supposed to catch it. If you think "why not restrict config actions" etc, it's because the dev can go there and tweak those actions too. And each step added means less velocity of development. It's a game of cat and mouse. With isolation, you can limit the blast radius and loss of revenue.
  - sapiogram 3y ago
    > Automated CI/CD [...] > One intern was told to deploy the app and I guess he made a mistake and updated k8 configs which deleted all the pods. Tell me how code reviews are supposed to catch it. These sound contradictory to me. Part of having automated CI/CD, is not having to manually deal with k8s to do a regular deploy.
  - ahtihn 3y ago
    > One intern was told to deploy the app and I guess he made a mistake and updated k8 configs which deleted all the pods. Tell me how code reviews are supposed to catch it. So you don’t have a staging environment to check config changes before deploying to prod? Or you don't put k8s manifests (or helm charts or whatever)in source control and just update prod through CLI? And you let interns do it alone? Your problem isn't interns, it's a terrible deployment processs with weak controls. Even senior engineers are going to break prod regularly in conditions like that.
josephg 3y ago
Elixir can. I’m not in any hurry to use it, but I suspect there’s a lot we still have to learn from its design.
ivanhoe 3y ago
If that happens it's an organizational problem (lack of mentoring, code reviews, access control), not an architectural problem...
ninkendo 3y ago
I don’t understand how micro services prevent a system from “going down”. I pushed an infinite loop to the auth service, oops. Now nothing works. How did micro services prevent this?
qaq 3y ago
Sure with proper CI/CD in place which you need regardless of app being a monolith or a set of micorservices. It's also infinitely simpler to setup proper CI/CD for a monolith.

ahtihn 3y ago

You let interns push to production without code review?

prakhar897 3y ago
Totally missed the point. Even with Code reviews, Unit/Integration Testing, Automated CI/CD and more can a person broke the prod. One intern was told to deploy the app and I guess he made a mistake and updated k8 configs which deleted all the pods. Tell me how code reviews are supposed to catch it. If you think "why not restrict config actions" etc, it's because the dev can go there and tweak those actions too. And each step added means less velocity of development. It's a game of cat and mouse. With isolation, you can limit the blast radius and loss of revenue.
- sapiogram 3y ago
  > Automated CI/CD [...] > One intern was told to deploy the app and I guess he made a mistake and updated k8 configs which deleted all the pods. Tell me how code reviews are supposed to catch it. These sound contradictory to me. Part of having automated CI/CD, is not having to manually deal with k8s to do a regular deploy.
- ahtihn 3y ago
  > One intern was told to deploy the app and I guess he made a mistake and updated k8 configs which deleted all the pods. Tell me how code reviews are supposed to catch it. So you don’t have a staging environment to check config changes before deploying to prod? Or you don't put k8s manifests (or helm charts or whatever)in source control and just update prod through CLI? And you let interns do it alone? Your problem isn't interns, it's a terrible deployment processs with weak controls. Even senior engineers are going to break prod regularly in conditions like that.

josephg 3y ago

Elixir can. I’m not in any hurry to use it, but I suspect there’s a lot we still have to learn from its design.

ivanhoe 3y ago

If that happens it's an organizational problem (lack of mentoring, code reviews, access control), not an architectural problem...

ninkendo 3y ago

I don’t understand how micro services prevent a system from “going down”. I pushed an infinite loop to the auth service, oops. Now nothing works. How did micro services prevent this?

qaq 3y ago

Sure with proper CI/CD in place which you need regardless of app being a monolith or a set of micorservices. It's also infinitely simpler to setup proper CI/CD for a monolith.