From 9bd31cb9b797960d2d66498fc7b9092238d69314 Mon Sep 17 00:00:00 2001 From: Mahdi Date: Sun, 6 Oct 2024 16:54:47 +0800 Subject: [PATCH] added my post --- content/_data/authors/azarboon.adoc | 6 +++++ ...4-content-security-policy-grant copy.adoc} | 0 ...-10-06-serverless-ci-cd-best-practice.adoc | 22 +++++++++++++++++++ 3 files changed, 28 insertions(+) create mode 100644 content/_data/authors/azarboon.adoc rename content/blog/2024/10/04/{2024-10-04-content-security-policy-grant.adoc => 2024-10-04-content-security-policy-grant copy.adoc} (100%) create mode 100644 content/blog/2024/10/04/2024-10-06-serverless-ci-cd-best-practice.adoc diff --git a/content/_data/authors/azarboon.adoc b/content/_data/authors/azarboon.adoc new file mode 100644 index 000000000000..c2a78267324a --- /dev/null +++ b/content/_data/authors/azarboon.adoc @@ -0,0 +1,6 @@ +--- +name: "Mahdi Azarboon" +twitter: m_azarboon +github: azarboon +linkedin: azarboon +--- \ No newline at end of file diff --git a/content/blog/2024/10/04/2024-10-04-content-security-policy-grant.adoc b/content/blog/2024/10/04/2024-10-04-content-security-policy-grant copy.adoc similarity index 100% rename from content/blog/2024/10/04/2024-10-04-content-security-policy-grant.adoc rename to content/blog/2024/10/04/2024-10-04-content-security-policy-grant copy.adoc diff --git a/content/blog/2024/10/04/2024-10-06-serverless-ci-cd-best-practice.adoc b/content/blog/2024/10/04/2024-10-06-serverless-ci-cd-best-practice.adoc new file mode 100644 index 000000000000..904c91cb6fe7 --- /dev/null +++ b/content/blog/2024/10/04/2024-10-06-serverless-ci-cd-best-practice.adoc @@ -0,0 +1,22 @@ +--- +:layout: post +:title: "Serverless CI/CD Best Practice" +:tags: +- serverless +- aws +- azure +- cloud +description: > + Tips and best practice for making CI/CD for serverless application +--- +Serverless is an overloaded term. Its meaning has stretched overtime. One link:https://ben11kehoe.medium.com/the-meaning-lessness-of-serverless-cc004936dee5/[shouldn't fixate] on a strict definition of serverless nor on any specific technology. Instead, one should focus on how to leverage serverless for their own business problems. + +One of the main capabilities of serverless is higher agility and shorter time-to-market. However, it usually requires automation and CI/CD pipelines. You can use Jenkins to automate your entire serverless environment. As a best practice, make sure that each of followings have their own repository and deployment pipeline: + +* Ephemeral environment and all its associated ephemeral resources such as AWS Lambda, Fargate, etc. This ensures that they can be deployed and rolled-back at the same time making it easier to spin-up and discard the ephemeral environment. +* Shared resources with long spin-up time e.g. AWS RDS cluster. This way, your ephemeral environments can use the same resource which makes their deployments faster and cheaper. +* Shared infrastructure resources such as virtual private network and subnet, also known as landing zones. Usually these resources are managed by a separate platform team. + +I’ve specifically named AWS services but this best practice apply to other cloud vendors, too. + +You can check link:https://theburningmonk.com/2023/02/how-to-handle-serverful-resources-when-using-ephemeral-environments/[this] and link:https://theburningmonk.com/2023/01/this-is-why-you-should-keep-stateful-and-stateless-resources-together/[this] posts for further information.