<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ryo Nakao</title>
    <link>https://nakabonne.dev/</link>
    <description>Recent content on Ryo Nakao</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Jul 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://nakabonne.dev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Write a time-series database engine from scratch</title>
      <link>https://nakabonne.dev/posts/write-tsdb-from-scratch/</link>
      <pubDate>Thu, 01 Jul 2021 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/write-tsdb-from-scratch/</guid>
      <description>This blog post walks you through how to implement a time-series database engine based on what I&amp;rsquo;ve learned from my experience of writing a lightweight one from scratch.</description>
    </item>
    
    <item>
      <title>Fixed/Variable-length encoding in Go</title>
      <link>https://nakabonne.dev/posts/binary-encoding-go/</link>
      <pubDate>Fri, 18 Jun 2021 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/binary-encoding-go/</guid>
      <description>This post covers how to use the standard encoding/binary package to encode binary according to a custom format, and how it works.</description>
    </item>
    
    <item>
      <title>Visualize Go process metrics in real-time</title>
      <link>https://nakabonne.dev/posts/gosivy/</link>
      <pubDate>Sun, 24 Jan 2021 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/gosivy/</guid>
      <description>One day, it became necessary to have a tool to easily observe resource consumption trends of a Go process. I&amp;rsquo;m aware that there are tons of APM tools out there; also, Go has enough profiling tools including pprof.</description>
    </item>
    
    <item>
      <title>Understanding how AES encryption works</title>
      <link>https://nakabonne.dev/posts/understanding-how-aes-encryption-works/</link>
      <pubDate>Sun, 20 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/understanding-how-aes-encryption-works/</guid>
      <description>I recently had the opportunity to encrypt/decrypt stuff using AES, but I didn&amp;rsquo;t know it inside out well. I couldn’t help but be curious about how it is working, and I realized my mind could only be satisfied by digging deeper into its implementation.</description>
    </item>
    
    <item>
      <title>An Introduction to Progressive Delivery</title>
      <link>https://nakabonne.dev/posts/an-introduction-to-progressive-delivery/</link>
      <pubDate>Sun, 14 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/an-introduction-to-progressive-delivery/</guid>
      <description>As reported by DORA&amp;rsquo;s The Accelerate State of DevOps Report, elite performers deploy code to production a bunch of times a day,</description>
    </item>
    
    <item>
      <title>Take a walk the Go AST</title>
      <link>https://nakabonne.dev/posts/take-a-walk-the-go-ast/</link>
      <pubDate>Tue, 31 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/take-a-walk-the-go-ast/</guid>
      <description>What do you refer to when you&amp;rsquo;re curious about the Go AST? A document? Source code? While reading the documentation helps you understand it in the abstract, you can&amp;rsquo;t see how APIs relate to each other, etc.</description>
    </item>
    
    <item>
      <title>Digging deeper into the analysis of Go-code</title>
      <link>https://nakabonne.dev/posts/digging-deeper-into-the-analysis-of-go-code/</link>
      <pubDate>Sun, 29 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/digging-deeper-into-the-analysis-of-go-code/</guid>
      <description>The analysis of source code at the syntactic level can help you with your coding in a variety of ways. For that, the text is almost always converted to AST first to make it easier to handle in most languages.</description>
    </item>
    
    <item>
      <title>Things That Could Drive Me Into a Nervous Breakdown</title>
      <link>https://nakabonne.dev/posts/things-that-could-drive-me-into-a-nervous-breakdown/</link>
      <pubDate>Tue, 04 Jun 2019 05:54:14 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/things-that-could-drive-me-into-a-nervous-breakdown/</guid>
      <description>Photo by Ric Rodrigues from Pexels
Nowadays, I have room in my heart for thinking about what could push me past my breaking point.</description>
    </item>
    
    <item>
      <title>Incredible reasons I make a recommendation to apply to GSoC despite never got accepted</title>
      <link>https://nakabonne.dev/posts/incredible-reasons-i-make-a-recommendation-to-apply-to-gsoc-despite-never-got-accepted/</link>
      <pubDate>Sat, 11 May 2019 02:19:59 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/incredible-reasons-i-make-a-recommendation-to-apply-to-gsoc-despite-never-got-accepted/</guid>
      <description>Unfortunately, as mentioned earlier I was not able to get into Google Summer of Code 2019.
 Despite things never worked out as my expect, I do not despaired at all.</description>
    </item>
    
    <item>
      <title>Depth of module</title>
      <link>https://nakabonne.dev/posts/depth-of-module/</link>
      <pubDate>Thu, 17 Jan 2019 11:33:43 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/depth-of-module/</guid>
      <description>Click here for Japanese version
This article summarizes the concept of deep module described in the book “A Philosophy of Software Design” written by Professor John Ousterhout at Stanford University, and is written with permission of him.</description>
    </item>
    
    <item>
      <title>Realization of distributed tracing by Envoy</title>
      <link>https://nakabonne.dev/posts/realization-of-distributed-tracing-by-envoy/</link>
      <pubDate>Tue, 18 Dec 2018 10:08:02 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/realization-of-distributed-tracing-by-envoy/</guid>
      <description>Necessity of distributed tracing Since distributed architecture such as Microservices are handled across multiple services, it’s difficult to keep track of communication between services.</description>
    </item>
    
    <item>
      <title>A choice to start small Service Mesh</title>
      <link>https://nakabonne.dev/posts/a-choice-to-start-small-service-mesh/</link>
      <pubDate>Sat, 24 Nov 2018 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/a-choice-to-start-small-service-mesh/</guid>
      <description>Now, the architecture called Service Mesh is attracting attention in the Microservice industry.
There are various products for realization, but I made a small control-plane called sxds.</description>
    </item>
    
    <item>
      <title>Go × Clean Architecture implementation pattern</title>
      <link>https://nakabonne.dev/posts/go-clean-architecture/</link>
      <pubDate>Fri, 05 Oct 2018 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/go-clean-architecture/</guid>
      <description>Click here for Japanese version
What is Clean Architecture? It could be thought an architecture pattern that dissociates interest by realizing:</description>
    </item>
    
    <item>
      <title>Why was gRPC born?</title>
      <link>https://nakabonne.dev/posts/why-was-grpc-born/</link>
      <pubDate>Thu, 04 Oct 2018 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/posts/why-was-grpc-born/</guid>
      <description>The term gRPC became very famous, and articles such as “Introducing gRPC in house” and “How to build gRPC server” can now overflow.</description>
    </item>
    
    <item>
      <title>About</title>
      <link>https://nakabonne.dev/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://nakabonne.dev/about/</guid>
      <description>Hi there! I&amp;rsquo;m Ryo Nakao.
I&amp;rsquo;m a software engineer, an OSS enthusiast.
I like peeling away at abstraction layers to get a better sense of what I&amp;rsquo;m working with by implementing actually.</description>
    </item>
    
  </channel>
</rss>
