<?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>rafaelbecker.dev</title>
    <link>https://rafaelbecker.dev/</link>
    <description>Recent content on rafaelbecker.dev</description>
    <generator>Hugo</generator>
    <language>pt-br</language>
    <lastBuildDate>Tue, 10 Nov 2026 22:31:34 -0300</lastBuildDate>
    <atom:link href="https://rafaelbecker.dev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Comparando coleções com value objects no TypeScript</title>
      <link>https://rafaelbecker.dev/posts/2026-11-10-comparando-colecoes-com-value-objects-no-typescript/</link>
      <pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://rafaelbecker.dev/posts/2026-11-10-comparando-colecoes-com-value-objects-no-typescript/</guid>
      <description>&lt;p&gt;No &lt;a href=&#34;https://rafaelbecker.dev/posts/2026-11-09-colecoes-como-classes-no-typescript/&#34;&gt;post anterior&lt;/a&gt;, troquei as interfaces que
representavam a resposta de uma API por uma classe &lt;code&gt;Collection&lt;/code&gt;, que carrega os itens e os comportamentos sobre eles.
Agora, essa coleção precisou resolver um problema novo.&lt;/p&gt;
&lt;p&gt;Em um processo de migração, eu recebia os contatos de uma pessoa a partir de uma origem externa e precisava descobrir
quais desses contatos ainda não existiam no cadastro dela. Só esses deveriam seguir para a importação.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Retornando coleções como classes no TypeScript</title>
      <link>https://rafaelbecker.dev/posts/2026-11-09-colecoes-como-classes-no-typescript/</link>
      <pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://rafaelbecker.dev/posts/2026-11-09-colecoes-como-classes-no-typescript/</guid>
      <description>&lt;p&gt;Um cenário comum em projetos TypeScript é consumir uma API REST que devolve uma coleção de recursos, possivelmente
paginada, no formato JSON. Como exemplo, um endpoint de consulta de pessoas:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;GET /api/pessoas
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Que responde com um envelope contendo o status da requisição e, dentro de &lt;code&gt;data&lt;/code&gt;, a página com os itens e as
informações de paginação:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-json&#34; data-lang=&#34;json&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;p&#34;&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;  &lt;span class=&#34;nt&#34;&gt;&amp;#34;status&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;s2&#34;&gt;&amp;#34;success&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;  &lt;span class=&#34;nt&#34;&gt;&amp;#34;data&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;p&#34;&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;nt&#34;&gt;&amp;#34;items&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;p&#34;&gt;[&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;      &lt;span class=&#34;p&#34;&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;        &lt;span class=&#34;nt&#34;&gt;&amp;#34;nome&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;s2&#34;&gt;&amp;#34;Pessoa 1&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;        &lt;span class=&#34;nt&#34;&gt;&amp;#34;email&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;s2&#34;&gt;&amp;#34;pessoa1@mail.com&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;        &lt;span class=&#34;nt&#34;&gt;&amp;#34;criado_em&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;s2&#34;&gt;&amp;#34;2026-11-02T10:00:00Z&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;      &lt;span class=&#34;p&#34;&gt;},&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;      &lt;span class=&#34;p&#34;&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;        &lt;span class=&#34;nt&#34;&gt;&amp;#34;nome&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;s2&#34;&gt;&amp;#34;Pessoa 2&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;        &lt;span class=&#34;nt&#34;&gt;&amp;#34;email&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;s2&#34;&gt;&amp;#34;pessoa2@mail.com&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;        &lt;span class=&#34;nt&#34;&gt;&amp;#34;criado_em&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;s2&#34;&gt;&amp;#34;2026-10-28T15:30:00Z&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;      &lt;span class=&#34;p&#34;&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;p&#34;&gt;],&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;nt&#34;&gt;&amp;#34;limit&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;mi&#34;&gt;10&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;nt&#34;&gt;&amp;#34;total&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;mi&#34;&gt;2&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;nt&#34;&gt;&amp;#34;has_more&amp;#34;&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt; &lt;span class=&#34;kc&#34;&gt;false&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;  &lt;span class=&#34;p&#34;&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;p&#34;&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id=&#34;o-caminho-mais-comum-interfaces&#34;&gt;O caminho mais comum: interfaces&lt;/h2&gt;
&lt;p&gt;O que mais se vê por aí é criar uma &lt;code&gt;interface&lt;/code&gt; que representa essa estrutura. Com generics dá para desacoplar as
partes: uma interface para o envelope, com o &lt;code&gt;status&lt;/code&gt; e o &lt;code&gt;data&lt;/code&gt;, e outra para a página, com os campos de paginação e
os &lt;code&gt;items&lt;/code&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploy na AWS sem credenciais fixas com GitHub OIDC</title>
      <link>https://rafaelbecker.dev/posts/2026-11-08-deploy-na-aws-sem-credenciais-com-github-oidc/</link>
      <pubDate>Sun, 08 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://rafaelbecker.dev/posts/2026-11-08-deploy-na-aws-sem-credenciais-com-github-oidc/</guid>
      <description>&lt;p&gt;Este site é publicado por um workflow do GitHub Actions. A cada push na branch &lt;code&gt;master&lt;/code&gt;, o workflow gera o site com o
Hugo, sincroniza os arquivos com um bucket S3 e invalida o cache da distribuição do CloudFront.&lt;/p&gt;
&lt;p&gt;Para falar com a AWS, o workflow usava um usuário IAM com uma access key guardada nos secrets do repositório:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;- &lt;span class=&#34;nt&#34;&gt;name&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt;&lt;span class=&#34;w&#34;&gt; &lt;/span&gt;&lt;span class=&#34;l&#34;&gt;Upload S3&lt;/span&gt;&lt;span class=&#34;w&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;w&#34;&gt;  &lt;/span&gt;&lt;span class=&#34;nt&#34;&gt;run&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt;&lt;span class=&#34;w&#34;&gt; &lt;/span&gt;&lt;span class=&#34;l&#34;&gt;aws s3 sync public s3://rafaelbecker.dev --delete&lt;/span&gt;&lt;span class=&#34;w&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;w&#34;&gt;  &lt;/span&gt;&lt;span class=&#34;nt&#34;&gt;env&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt;&lt;span class=&#34;w&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;w&#34;&gt;    &lt;/span&gt;&lt;span class=&#34;nt&#34;&gt;AWS_ACCESS_KEY_ID&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt;&lt;span class=&#34;w&#34;&gt; &lt;/span&gt;&lt;span class=&#34;l&#34;&gt;${{ secrets.AWS_ACCESS_KEY_ID }}&lt;/span&gt;&lt;span class=&#34;w&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;w&#34;&gt;    &lt;/span&gt;&lt;span class=&#34;nt&#34;&gt;AWS_SECRET_ACCESS_KEY&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt;&lt;span class=&#34;w&#34;&gt; &lt;/span&gt;&lt;span class=&#34;l&#34;&gt;${{ secrets.AWS_SECRET_ACCESS_KEY }}&lt;/span&gt;&lt;span class=&#34;w&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;w&#34;&gt;    &lt;/span&gt;&lt;span class=&#34;nt&#34;&gt;AWS_DEFAULT_REGION&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;:&lt;/span&gt;&lt;span class=&#34;w&#34;&gt; &lt;/span&gt;&lt;span class=&#34;l&#34;&gt;${{ secrets.AWS_DEFAULT_REGION }}&lt;/span&gt;&lt;span class=&#34;w&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Funciona, mas a chave é de longa duração. Ela vale até alguém lembrar de rotacioná-la, e se vazar, por um log, por uma
action de terceiros comprometida ou por qualquer outro caminho, dá acesso à conta até ser revogada.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Redirecionando portas com socat</title>
      <link>https://rafaelbecker.dev/posts/2026-11-07-redirecionando-portas-com-socat/</link>
      <pubDate>Sat, 07 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://rafaelbecker.dev/posts/2026-11-07-redirecionando-portas-com-socat/</guid>
      <description>&lt;p&gt;No dia a dia de desenvolvimento, procuro manter meus ambientes de trabalho isolados em containers Docker, tanto para
executar os projetos quanto para desenvolvê-los com recursos como o Dev Containers.&lt;/p&gt;
&lt;p&gt;Em um desses projetos, a aplicação precisa acessar uma base PostgreSQL que roda em uma instância EC2, sem acesso
público. Para chegar até ela, uso o &lt;strong&gt;AWS Systems Manager Session Manager&lt;/strong&gt;: com o &lt;code&gt;aws ssm&lt;/code&gt; e o documento
&lt;code&gt;AWS-StartPortForwardingSession&lt;/code&gt;, abro um túnel até a instância e mapeio uma porta remota para uma porta local.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GRANTs para vários schemas com bash</title>
      <link>https://rafaelbecker.dev/posts/2026-11-05-grants-para-varios-schemas-com-bash/</link>
      <pubDate>Thu, 05 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://rafaelbecker.dev/posts/2026-11-05-grants-para-varios-schemas-com-bash/</guid>
      <description>&lt;p&gt;Em uma base PostgreSQL com uma dezena de schemas, criados para isolar os módulos da aplicação, precisei conceder a um
usuário &lt;code&gt;app&lt;/code&gt; acesso a todos eles.&lt;/p&gt;
&lt;p&gt;No PostgreSQL, para que um usuário acesse os objetos de uma base de dados, é preciso conceder a ele os privilégios
diretamente ou atribuir uma role que já tenha esses privilégios. Para um único schema, como o &lt;code&gt;public&lt;/code&gt;, com o usuário
lendo e escrevendo nas tabelas, usando as sequences e criando triggers, as instruções seriam algo assim:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Docker Engine no WSL, sem Docker Desktop</title>
      <link>https://rafaelbecker.dev/posts/2026-11-01-docker-engine-no-wsl-sem-docker-desktop/</link>
      <pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://rafaelbecker.dev/posts/2026-11-01-docker-engine-no-wsl-sem-docker-desktop/</guid>
      <description>&lt;p&gt;No Windows, o caminho mais comum para usar containers é instalar o Docker Desktop. Ele cria e gerencia uma distro WSL
própria, expõe o comando &lt;code&gt;docker&lt;/code&gt; no Windows e entrega uma interface gráfica para acompanhar containers e imagens.&lt;/p&gt;
&lt;p&gt;No meu ambiente de desenvolvimento, optei por outro caminho: instalar o Docker Engine diretamente em uma distro WSL,
como o Ubuntu, e deixar o Docker Desktop de fora.&lt;/p&gt;
&lt;h2 id=&#34;por-que-não-o-docker-desktop&#34;&gt;Por que não o Docker Desktop&lt;/h2&gt;
&lt;p&gt;Não foram poucas as vezes em que tive problemas com o Docker Desktop, e eles se repetiam em três frentes:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bloqueando o event loop no Node.js</title>
      <link>https://rafaelbecker.dev/posts/2024-30-03-bloqueando-o-event-loop-no-nodejs/</link>
      <pubDate>Sat, 30 Mar 2024 00:00:00 +0000</pubDate>
      <guid>https://rafaelbecker.dev/posts/2024-30-03-bloqueando-o-event-loop-no-nodejs/</guid>
      <description>&lt;p&gt;Uma das características que mais me fascinam no Node.js é a sua estrutura assíncrona e não bloqueante, implementada por
meio do &lt;strong&gt;event loop&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Todo o código JavaScript de uma aplicação Node.js roda em uma única thread. O event loop é quem decide o que essa thread
executa a seguir: atender uma nova requisição, continuar uma escrita em disco, disparar um timer. Enquanto um trecho de
código está rodando, nada mais é atendido.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Renovando chaves e subchaves GPG</title>
      <link>https://rafaelbecker.dev/posts/2024-28-03-renovando-chaves-e-subchaves-gpg/</link>
      <pubDate>Thu, 28 Mar 2024 00:00:00 +0000</pubDate>
      <guid>https://rafaelbecker.dev/posts/2024-28-03-renovando-chaves-e-subchaves-gpg/</guid>
      <description>&lt;p&gt;Plataformas de hospedagem git, como GitHub e GitLab, permitem assinar commits com uma chave GPG. A assinatura é uma
forma adicional de verificar a integridade do commit e a autenticidade de quem o fez, e é assim que assino os meus.&lt;/p&gt;
&lt;p&gt;Para essa chave, sigo a boa prática de definir uma data de expiração. Assim, se ela for exposta, deixa de ser útil
depois de um tempo. A contrapartida é que, de tempos em tempos, preciso renová-la antes que expire, para não ter
problemas na hora de fazer os commits.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
