<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Serverless on Route179</title>
    <link>https://route179.dev/tags/serverless/</link>
    <description>Recent content in Serverless on Route179</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>2026 Sheng Chen</copyright>
    <lastBuildDate>Sat, 20 Jun 2020 20:06:42 +0000</lastBuildDate>
    <atom:link href="https://route179.dev/tags/serverless/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Build a Serverless CI/CD pipeline on AWS with Fargate, CodePipeline and Terraform</title>
      <link>https://route179.dev/2020/06/20/build-a-serverless-ci-cd-pipeline-on-aws-with-fargate-codepipeline-and-terraform/</link>
      <pubDate>Sat, 20 Jun 2020 20:06:42 +0000</pubDate>
      <guid>https://route179.dev/2020/06/20/build-a-serverless-ci-cd-pipeline-on-aws-with-fargate-codepipeline-and-terraform/</guid>
      <description>&lt;p&gt;This blog provides an example for deploying a CI/CD pipeline on AWS utilising the serverless container platform Fargate and the fully managed CodePipeline service. We’ll also use Terraform to automate the process for building the entire AWS environment, as shown in the below diagram.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://route179.dev/2020/06/20/build-a-serverless-ci-cd-pipeline-on-aws-with-fargate-codepipeline-and-terraform/cicd-fargate.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Specifically, we’ll be creating the following AWS resources:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;1x demo VPC including public/private subnets, NAT gateway and security groups etc&lt;/li&gt;
&lt;li&gt;1x ALB for providing LB services to a target group of 2x Fargate container tasks&lt;/li&gt;
&lt;li&gt;1x ECS cluster with a Fargate service definition (running our demo app)&lt;/li&gt;
&lt;li&gt;1x CodePipeline definition, which builds the demo app from &lt;a href=&#34;https://github.com/sc13912/fargate-demo-app.git&#34;&gt;GitHub Repo&lt;/a&gt; (with a webhook trigger) and deploys it to the same Fargate service&lt;/li&gt;
&lt;li&gt;1x ECR repository for hosting pipeline build images&lt;/li&gt;
&lt;li&gt;2x S3 Buckets as build &amp;amp; artifact cache&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt; – for this demo, I’m using these Terraform modules found on GitHub:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cloud Native DevOps on GCP Series Ep3 – Use Terraform to launch a Serverless CI/CD pipeline with Cloud Run, GCR and Cloud Build</title>
      <link>https://route179.dev/2020/06/13/use-terraform-to-launch-a-serverless-ci-cd-pipeline-with-cloud-run-gcr-and-cloud-build/</link>
      <pubDate>Sat, 13 Jun 2020 09:53:41 +0000</pubDate>
      <guid>https://route179.dev/2020/06/13/use-terraform-to-launch-a-serverless-ci-cd-pipeline-with-cloud-run-gcr-and-cloud-build/</guid>
      <description>&lt;p&gt;This is the third episode of our **Cloud Native DevOps on GCP **series. In the previous chapters, we have achieved the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://route179.wordpress.com/2020/06/09/build-a-gke-cluster-with-terraform/&#34;&gt;&lt;strong&gt;Built a GKE Cluster with Terraform&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://route179.wordpress.com/2020/06/09/create-a-ci-cd-pipeline-with-gke-gcr-and-cloud-build/&#34;&gt;**Created a CI/CD pipeline with GKE, GCR and Cloud Build **&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This time, we will take a step further and go completely serverless by deploying the same Node app onto the Google Cloud Run platform. Cloud Run is built from an open source project named &lt;a href=&#34;https://knative.dev/&#34;&gt;Knative&lt;/a&gt;, which is a serverless framework developed based on the industry proven Kubernetes architecture. Whilst Knative is developed with the same event-driven concept (like other serverless solutions), it also offers great flexibility and multi-cloud portability at a container level.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
