<?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>Protobuf on ZachFi</title>
    <link>https://zach.fi/tags/protobuf/</link>
    <description>Recent content in Protobuf on ZachFi</description>
    <image>
      <title>ZachFi</title>
      <url>https://zach.fi/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://zach.fi/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.148.2</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Apr 2021 10:53:57 -0600</lastBuildDate>
    <atom:link href="https://zach.fi/tags/protobuf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Database Schema Generation with Protobuf</title>
      <link>https://zach.fi/posts/ldap_schema_generation/</link>
      <pubDate>Sat, 10 Apr 2021 10:53:57 -0600</pubDate>
      <guid>https://zach.fi/posts/ldap_schema_generation/</guid>
      <description>&lt;p&gt;As I look to reduce the number of touch points that are required to make a
change to my personal system, I&amp;rsquo;m always thinking about how to reduce
complexity and leverage existing tooling. In this way, we can continue to
leverage an existing foundation to build out further abstractions. One such
lever I have worked on over the last year was using my gRPC protobuf definitions
to generate LDAP schema files that could be loaded into the server to match the
objects that I&amp;rsquo;d be working with in Go.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
