<?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>rego on John Hooks</title>
    <link>https://badlyenginee.red/categories/rego/</link>
    <description>Recent content in rego on John Hooks</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 31 Jan 2024 20:34:07 -0400</lastBuildDate><atom:link href="https://badlyenginee.red/categories/rego/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rego &amp; Go</title>
      <link>https://badlyenginee.red/posts/2024-01-31-go-rego/</link>
      <pubDate>Wed, 31 Jan 2024 20:34:07 -0400</pubDate>
      
      <guid>https://badlyenginee.red/posts/2024-01-31-go-rego/</guid>
      <description>Rego is a declarative policy language (also a logic language) that is used in OPA. It&amp;rsquo;s a general purpose language that works in many scenarios that aren&amp;rsquo;t necessarily just for policies.
One pattern I&amp;rsquo;ve recently come to like is using Rego inside of my Go project if the business logic becomes more complicated while leveraging the power of Go&amp;rsquo;s HTTP libraries. We can either embed our Rego or dynamically load it in if we decide we need to easily make changes.</description>
    </item>
    
  </channel>
</rss>
