Skip to content

Commit

Permalink
Remove dead links
Browse files Browse the repository at this point in the history
  • Loading branch information
chadlwilson committed Jul 16, 2023
1 parent ba3a70d commit e7adadb
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ summary_image: "/assets/images/blog/serverless-continuous-delivery/serverless-co
</figure>
<% end %>

At PipelineConf this year, I [spoke about my experiences](https://vimeo.com/channels/pipelineconf/209686484) with serverless architectures and how they play well with the patterns and practices of continuous delivery. This post explains what a serverless architecture is, their benefits and how they can enable continuous delivery.
At PipelineConf this year, I spoke about my experiences with serverless architectures and how they play well with the patterns and practices of continuous delivery. This post explains what a serverless architecture is, their benefits and how they can enable continuous delivery.

## What is serverless?

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Some of these issues [can be addressed](https://martinfowler.com/bliki/PhoenixSe

These tools help avoid configuration drift, the sort of one-off changes that go unnoticed and undocumented.

An important point to note is that these tools only apply the configuration that they are asked to. If you applied any additional configuration outside of what these tools are aware of, or if you forgot to un-apply or remove some configuration, you'd be out of luck. This what [Ranjib Dey](https://github.com/ranjib) calls the [Accumulator Anti-Pattern](https://server.dzone.com/articles/infrastructure-tooling-anti).
An important point to note is that these tools only apply the configuration that they are asked to. If you applied any additional configuration outside of what these tools are aware of, or if you forgot to un-apply or remove some configuration, you'd be out of luck. This what [Ranjib Dey](https://github.com/ranjib) calls the Accumulator Anti-Pattern.

A much better alternative is to tear down servers periodically and apply configuration changes every once in a while. This helps avoid and catch any configuration drift outside of configuration management tools. Eventually one can move to deploying new servers on every configuration change. This strategy is known as an [Immutable Server](https://martinfowler.com/bliki/ImmutableServer.html).

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -104,5 +104,5 @@ All you have to do is to configure the generated image as an external artifact.

So there you go. I hope you find it useful. If you have any questions, please feel free to comment and I'll answer from whatever I've learnt so far.

*This post was originally published on [Mohamed Najiullah's blog](https://mohamednajiullah.tech/configuring-google-container-registry-gcr-as-an-artifact-store-in-gocd-5453f8037e8c).
*This post was originally published on Mohamed Najiullah's blog*

Original file line number Diff line number Diff line change
Expand Up @@ -145,5 +145,5 @@ If you want the pod to have SSH access to a Git service, you can create a secret

So there you go. I hope you find it useful. If you have any questions, please feel free to comment and I’ll answer from whatever I’ve learnt so far.

*This article was originally posted on [Mohamed Najiullah's blog](https://mohamednajiullah.tech/configuring-go-agents-in-gocd-in-kubernetes-static-and-elastic-agents-c5dbf5f6a01d)*
*This article was originally posted on Mohamed Najiullah's blog*

0 comments on commit e7adadb

Please sign in to comment.