<?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>Architecture on FreePeak Labs</title>
    <link>https://freepeak.github.io/categories/architecture/</link>
    <description>Recent content in Architecture on FreePeak Labs</description>
    <image>
      <title>FreePeak Labs</title>
      <url>https://FreePeak.github.io/images/freepeak-labs-cover.png</url>
      <link>https://FreePeak.github.io/images/freepeak-labs-cover.png</link>
    </image>
    <generator>Hugo -- 0.167.0</generator>
    <language>en</language>
    <lastBuildDate>Tue, 27 Jan 2026 10:00:00 +0700</lastBuildDate>
    <atom:link href="https://freepeak.github.io/categories/architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HSM: The Physical Fortress for Digital Secrets</title>
      <link>https://freepeak.github.io/posts/hsm-concept-definition/</link>
      <pubDate>Tue, 27 Jan 2026 10:00:00 +0700</pubDate>
      <guid>https://freepeak.github.io/posts/hsm-concept-definition/</guid>
      <description>An HSM is not just faster crypto hardware. It is a physical fortress where a private key is born, survives, and destroys itself if tampered with. A deep dive into FIPS 140-2, True Random Number Generators (TRNG) and side-channel attacks.</description>
    </item>
    <item>
      <title>HSM and the 3-of-5 Signing Ritual: Turning Code Signing From a Script Into a Process</title>
      <link>https://freepeak.github.io/posts/hsm-3-tren-5-ky-so-firmware-yubihsm2/</link>
      <pubDate>Wed, 21 Jan 2026 10:00:00 +0700</pubDate>
      <guid>https://freepeak.github.io/posts/hsm-3-tren-5-ky-so-firmware-yubihsm2/</guid>
      <description>A pragmatic look at putting an HSM into a firmware signing system: choosing a model, the key lifecycle, and why 3-of-5 cuts risk without slowing releases down.</description>
    </item>
    <item>
      <title>Architecture and Best Practices: Running Kong Open Source as an API Gateway on GKE</title>
      <link>https://freepeak.github.io/posts/kong-opensource-k8s-gcp/</link>
      <pubDate>Mon, 19 Jan 2026 10:00:00 +0700</pubDate>
      <guid>https://freepeak.github.io/posts/kong-opensource-k8s-gcp/</guid>
      <description>A deep dive into the architecture and best practices for deploying Kong Open Source as an API gateway and ingress controller on Google Kubernetes Engine (GKE).</description>
    </item>
    <item>
      <title>Kong DB-less on AWS EKS: Per-Tenant Rate Limiting, and Why ALB Ingress Is Not Enough</title>
      <link>https://freepeak.github.io/posts/kong-eks-aws-rate-limit-tenant/</link>
      <pubDate>Mon, 19 Jan 2026 10:00:00 +0700</pubDate>
      <guid>https://freepeak.github.io/posts/kong-eks-aws-rate-limit-tenant/</guid>
      <description>A pragmatic look at running Kong DB-less on AWS EKS for per-tenant rate limiting: why ALB Ingress, WAF and Lambda quickly turn into duct tape, plus the best practices for running Kong lean, safe and easy to scale.</description>
    </item>
    <item>
      <title>Lock In VPC CIDR Early: A Small Decision That Prevents Tearing It All Down Later</title>
      <link>https://freepeak.github.io/posts/chot-vpc-cidr-tu-som/</link>
      <pubDate>Mon, 19 Jan 2026 10:00:00 +0700</pubDate>
      <guid>https://freepeak.github.io/posts/chot-vpc-cidr-tu-som/</guid>
      <description>Why choosing a VPC CIDR early matters: real-world experience on how CIDR decisions shape AWS infrastructure growth, and how to govern CIDR effectively with Terragrunt.</description>
    </item>
  </channel>
</rss>
