<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Serverless on Sander Knape</title>
    <link>https://sanderknape.com/tags/serverless/</link>
    <description>Recent content in Serverless on Sander Knape</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 15 Dec 2020 17:38:12 +0200</lastBuildDate>
    <atom:link href="https://sanderknape.com/tags/serverless/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Serverless Payment Workflow using AWS Lambda and the AWS CDK</title>
      <link>https://sanderknape.com/2020/12/serverless-payment-workflow-lambda-cdk/</link>
      <pubDate>Tue, 15 Dec 2020 17:38:12 +0200</pubDate>
      <guid>https://sanderknape.com/2020/12/serverless-payment-workflow-lambda-cdk/</guid>
      <description>&lt;p&gt;Serverless technology is getting more popular by the day. More and more people are starting to experiment with it and learn for which use cases it can add value. In this blog post I share an example of what a fully Serverless workflow can achieve.&lt;/p&gt;&#xA;&lt;p&gt;For a while now I&amp;rsquo;ve been curious how one would implement a payment workflow on a website. I was aware that platforms like &lt;a href=&#34;https://stripe.com/&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Stripe&lt;/a&gt;, &lt;a href=&#34;https://www.adyen.com/&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Adyen&lt;/a&gt; and &lt;a href=&#34;https://www.mollie.com/&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Mollie&lt;/a&gt; exist, but I never knew how much work would be required to set up a fully functioning workflow. I therefore decided to give it a try using nothing but Serverless technology.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building a static serverless website using S3 and CloudFront</title>
      <link>https://sanderknape.com/2020/02/building-a-static-serverless-website-using-s3-cloudfront/</link>
      <pubDate>Wed, 12 Feb 2020 19:25:02 +0200</pubDate>
      <guid>https://sanderknape.com/2020/02/building-a-static-serverless-website-using-s3-cloudfront/</guid>
      <description>&lt;p&gt;Hosting static websites is great. As they only contain static assets to be downloaded by the visitor&amp;rsquo;s browser - think HTML, CSS, Javascript, Fonts, images - no server-side code such as Java or PHP needs to be run. They&amp;rsquo;re therefore typically faster to load than dynamic websites, they have a smaller attack surface, and are easier to cache for even better performance.&lt;/p&gt;&#xA;&lt;p&gt;That is why some time ago I moved this blog from a Wordpress installation hosted on EC2 to a static website. As I was already in AWS, and I knew that S3 + CloudFront was a popular choice for hosting static websites, I decided to host my blog in S3 with CloudFront in front of it as the CDN.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building serverless applications with the AWS CDK - and testing them locally</title>
      <link>https://sanderknape.com/2019/05/building-serverless-applications-aws-cdk/</link>
      <pubDate>Fri, 31 May 2019 16:35:02 +0200</pubDate>
      <guid>https://sanderknape.com/2019/05/building-serverless-applications-aws-cdk/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/awslabs/aws-cdk&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;AWS Cloud Development Kit&lt;/a&gt; (AWS CDK) is a new framework for defining Infrastructure as Code (IaC) by AWS. It allows you to write IaC in a set of different languages. At the moment the following languages are supported: Javascript, Typescript, Python, Java, .NET. Support for other languages is coming.&lt;/p&gt;&#xA;&lt;p&gt;Of course, other methods like CloudFormation and Terraform already exist to write IaC. Using these tools you write declarative code in YAML, JSON or the Hashicorp Configuration Language (HCL) in a mostly declarative state. These tools will also support some basic operators such as if-statements and for-loops. Especially HCL has many of these capabilities with the latest &lt;a href=&#34;https://www.hashicorp.com/blog/announcing-terraform-0-12&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;0.12.0 release&lt;/a&gt;. However, it will always be different from using a &amp;ldquo;real&amp;rdquo; programming language. And it requires you to use a new tool, instead of using a language you already know.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The hidden challenges of Serverless: from VM to function</title>
      <link>https://sanderknape.com/2018/08/hidden-challenges-serverless-vm-function/</link>
      <pubDate>Thu, 02 Aug 2018 12:29:02 +0200</pubDate>
      <guid>https://sanderknape.com/2018/08/hidden-challenges-serverless-vm-function/</guid>
      <description>&lt;p&gt;Serverless is a relatively new term. It&amp;rsquo;s a software development paradigm where the entire concept of a &amp;ldquo;server&amp;rdquo; is abstracted away from the development process. You essentially only use managed services that handle scaling, and you pay only for what you use. You no longer need to think about operating systems, security patches, scaling configuration and more. All this is handled for you behind the scenes. The most well-known example is AWS Lambda, though as we will see in this blog post, serverless is much more than that.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Comparing AWS SAM with the Serverless framework</title>
      <link>https://sanderknape.com/2018/02/comparing-aws-sam-with-serverless-framework/</link>
      <pubDate>Thu, 22 Feb 2018 20:39:02 +0200</pubDate>
      <guid>https://sanderknape.com/2018/02/comparing-aws-sam-with-serverless-framework/</guid>
      <description>&lt;p&gt;Serverless applications are everywhere these days. Having been introduced some years ago with the introduction of AWS Lambda, today serverless is much more then Function as a Service (FaaS). AWS is even starting to use the term in their products: at AWS re:Invent 2017 &amp;ldquo;Aurora Serverless&amp;rdquo; was introduced, a fully managed RDMS database.&lt;/p&gt;&#xA;&lt;p&gt;How do you build such applications? Given that you properly like the Infrastructure as Code mindset as much as I do, the question is how to properly specify serverless applications provisioned in AWS in code. Two main options are out there: the Serverless Framework and AWS SAM. Both frameworks allow you to make it easier to build serverless applications.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Creating a serverless API using AWS API Gateway and DynamoDB</title>
      <link>https://sanderknape.com/2017/10/creating-a-serverless-api-using-aws-api-gateway-and-dynamodb/</link>
      <pubDate>Sat, 14 Oct 2017 14:54:02 +0200</pubDate>
      <guid>https://sanderknape.com/2017/10/creating-a-serverless-api-using-aws-api-gateway-and-dynamodb/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://aws.amazon.com/api-gateway/&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;AWS API Gateway&lt;/a&gt; is a managed service from Amazon Web Services that allows you to easily create an API endpoint. An incoming request can either be forwarded to an HTTP endpoint, can invoke a Lambda function, or connect to an AWS service. Arguably, the Lambda integration is most commonly used as it allows you to invoke a piece of code without managing a server or operating system (thus, combined with API Gateway, creating a serverless api). A common use case is to store and retrieve data to/from a database.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using pre-signed URLs to upload a file to a private S3 bucket</title>
      <link>https://sanderknape.com/2017/08/using-pre-signed-urls-upload-file-private-s3-bucket/</link>
      <pubDate>Tue, 08 Aug 2017 18:12:02 +0200</pubDate>
      <guid>https://sanderknape.com/2017/08/using-pre-signed-urls-upload-file-private-s3-bucket/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve written about serverless architectures before (&lt;a href=&#34;https://sanderknape.com/2017/05/building-a-serverless-website-in-aws/&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;a serverless website in S3&lt;/a&gt; and &lt;a href=&#34;https://sanderknape.com/2017/02/dynamic-image-generation-with-aws-api-gateway-and-lambda/&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;dynamic image generation with Lambda&lt;/a&gt;). I strongly believe in this notion as it minimizes required maintenance and makes the initial setup much easier. Of course, there is no silver bullet for every problem but use cases definitely exist where a serverless architecture makes a lot of sense.&lt;/p&gt;&#xA;&lt;p&gt;One such use case for serverless is a small piece of functionality that you just need to run. &lt;em&gt;Somewhere&lt;/em&gt;. You want to care as little as possible about this &lt;em&gt;somewhere&lt;/em&gt; because the functionality is so small that pretty much any work you put into the &lt;em&gt;somewhere&lt;/em&gt; is more than the time you spend on the actual functionality.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building a serverless website in AWS</title>
      <link>https://sanderknape.com/2017/05/building-a-serverless-website-in-aws/</link>
      <pubDate>Mon, 01 May 2017 19:25:02 +0200</pubDate>
      <guid>https://sanderknape.com/2017/05/building-a-serverless-website-in-aws/</guid>
      <description>&lt;p&gt;Maintaining a web server for your website is not ideal. It&amp;rsquo;s tedious, takes a lot of time if done properly and distracts from what you really want to do: sell a product, share information, e.t.c. The more time and money you spend on the platform, the less is available to spend on the website and your core business. Unless you&amp;rsquo;re a hosting company of course, but then this blog post isn&amp;rsquo;t really for you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic image generation with AWS API Gateway and Lambda</title>
      <link>https://sanderknape.com/2017/02/dynamic-image-generation-with-aws-api-gateway-and-lambda/</link>
      <pubDate>Tue, 21 Feb 2017 20:49:02 +0200</pubDate>
      <guid>https://sanderknape.com/2017/02/dynamic-image-generation-with-aws-api-gateway-and-lambda/</guid>
      <description>&lt;p&gt;The combination of API Gateway and Lambda is very powerful. It allows you to build some complex functionalities without maintaining any virtual machines yourself. Lambda can be hooked up to many other (AWS) Services including DynamoDB, Kinesis and S3. This paradigm, better known as &lt;em&gt;serverless&lt;/em&gt;, is truly upcoming for years now and its certainly time to jump on the bandwagon if you haven&amp;rsquo;t done so already.&lt;/p&gt;&#xA;&lt;p&gt;One of the better-known use cases of AWS Lambda is the &lt;a href=&#34;http://docs.aws.amazon.com/lambda/latest/dg/with-s3-example.html&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;generation of thumbnail images&lt;/a&gt; as images are inserted into S3. In this blog post we will go one step further and generate images based on the URL and return the image as a binary through API Gateway. The number of possibilities this unlocks are pretty much countless, including the generation of charts, bar codes, dynamic icons and much more.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
