Comments by "" (@ContinuousDelivery) on ""People Get Microservices Wrong All The Time!" | Dave, Simon Brown u0026 Hannes Lowette On Microservices" video.

  1. Why is this technical decision a "manager's" call? I recognise that is often is, but why - it shouldn't be. Dev's need to take responsibility for the technical decision making.
    33
  2.  @britishjames9415  I agree with this, but also think that often we devs wait to be given permission, instead of taking the responsibility for our own work. This is human nature, certainly, to some extent, but we are also not taught how to do this, and that it should be expected of us. This is a problem of education, but also of the culture in our industry. My friend, Jeff Patton has a great phrase, "devs should be like doctors, not waiters". When you talk to a waiter you say "I'll have the steak, medium, with pepper sauce, and salad, can you hold the dressing on the salad". When you talk to a doctor you say "What's wrong with me doc, what do I need to do to get better?". We are a profession of problem solvers, and yet we aren't taught that that is what we are, and we often complain if someone else doesn't solve the problem for us "It would have worked if only the requirements were correct". So yes, we need to be allowed to take responsibility, but also we need to just take it - I have said this before, but it's no one else's job to give us permission to do a good job. We are the experts, we know better than other people what it takes to do good work, we need to exert that expertise, and when we do, this is in everyone's interest.
    11
  3. My watch is a Bulova - it is the model worn by the later Apollo Lunar Module pilots, and was a birthday present.
    6
  4. ...therefore microservices is a poor choice. Service orientation on the other hand is a great choice. Design the same way, design the same services, use the same distributed comms mechanisms if you want, but put them all together in version control and test them all together continuously, and then release them all together. It is WAY more efficient than microservices. If you don't need the teams-scalability that microservices delivers, don't pay the costs of it. This is not a message from the cathedral, read the definitions of microservices (https://microservices.io), and think about their implications. Now read the definitions of Continuous Integration and Continuous Delivery (https://en.wikipedia.org/wiki/Continuous_integration), use these rather than "folk impressions" of what they mean, and I think that you will come to the same conclusion as me.
    5
  5. Then I am afraid that you are wrong. DevOps comes from people with way more that 100,000 customers and sometime spending money at much higher rates that normally done with credit cards. There is a lot of nonsense talked about DevOps, like everything else, but at its heart it is simply saying that we need to align the goals of dev and ops. Not sure how this can be controversial. If you mean, as many people do, "Continuous Delivery" when you say "DevOps" then again, I would disagree. CD is the process at the roots of some of the biggest, most successful companies in the world, and is applied very effectively, in nearly every industry that you can think of. Tesla is a CD company, so is Amazon, so is Ericsson for example.
    3
  6. True dat!
    2
  7. Yes 😊
    1
  8. So then, they are "independently deployable" - right? Not sure what I am missing?
    1