4 Matching Annotations
  1. Dec 2020
    1. A typical microservice might have an application code pipeline, an infrastructure pipeline, an OS patching pipeline, a configuration/feature flags pipeline, and an operator tools pipeline.

      I really appreciate this split.

    2. These sources are deployed in individual pipelines with the same safety mechanisms (like automatic rollback) that we use for deploying application code.

      The tricky bit in rollbacks is dealing with stateful/expensive things. Imagine a change that requires a non-trivial database migration. In order to do a rollback, you'd have to rollback the migration as well. How can this be accomplished generally? What if a problem is detected only after a new column has new data in it? Do you throw out that data?

  2. Nov 2020
    1. The details of what goes into a policy vary for each service, depending on what actions the service makes available, what types of resources it contains, and so on.

      This means that some kinds of validation cannot be done on write. For example, I've been able to write Resource values that contain invalid characters.

  3. Sep 2020
    1. Friday, September 18, 1925. Arkham, Massachusetts. It is the end of a long and abnormally hot summer. The first hints of autumn beckon, but a heavy heat persists, relentless. A silent, unspoken anger grips the town. Tempers are short, and in the last week alone there have been numerous reports of townspeople coming to heated, violent blows with one another over simple misunderstandings.And now, a call from James Hankerson. He claims to have found a dismembered body in his barn.Blaming the weather would be too easy. There is something wrong with this town, and not a whole lot this old soothsayer can do to stop the slide. My auguries indicate a small group of investigators will soon take note of these strange happenings and set forth to make things right. I’ ll be watching their progress...but I won’ t be holding my breath.