<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hexagonal-Architecture on Home</title>
    <link>https://blog.rafaelfernandez.dev/tags/hexagonal-architecture/</link>
    <description>Recent content in Hexagonal-Architecture on Home</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Rafael Fernandez</copyright>
    <lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.rafaelfernandez.dev/tags/hexagonal-architecture/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>criteria4s 4. Your domain has no database</title>
      <link>https://blog.rafaelfernandez.dev/posts/criteria4s-4-your-domain-has-no-database/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/criteria4s-4-your-domain-has-no-database/</guid>
      <description>How to use T &amp;lt;: CriteriaTag as a hexagonal port so your domain layer never imports a dialect. The database becomes a deployment decision.</description>
      
    </item>
    
    <item>
      <title>criteria4s. Your domain has no database</title>
      <link>https://blog.rafaelfernandez.dev/posts/criteria4s-4-your-domain-has-no-database/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/criteria4s-4-your-domain-has-no-database/</guid>
      <description>How to use T &amp;lt;: CriteriaTag as a hexagonal port so your domain layer never imports a dialect. The database becomes a deployment decision.</description>
      
    </item>
    
    <item>
      <title>Tagless Final is denotational semantics in disguise</title>
      <link>https://blog.rafaelfernandez.dev/posts/tagless-final-is-denotational-semantics/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/tagless-final-is-denotational-semantics/</guid>
      <description>Every trait in your hexagonal architecture is a tagless-final algebra. Every impl is an interpreter. You have been writing denotational semantics without knowing it. We trace the connection from Kiselyov&amp;rsquo;s paper through Scala&amp;rsquo;s Cats-Effect to Rust&amp;rsquo;s port traits, and show why the pattern that academics call &amp;lsquo;finally tagless&amp;rsquo; is the same pattern that practitioners call &amp;lsquo;dependency injection.&amp;rsquo;</description>
      
    </item>
    
    <item>
      <title>Todo TUI in Rust 5. Event polling, the edit vertical slice, and closing</title>
      <link>https://blog.rafaelfernandez.dev/posts/todo-tui-rust-5-event-polling-edit-vertical-slice/</link>
      <pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/todo-tui-rust-5-event-polling-edit-vertical-slice/</guid>
      <description>The rat serves the last course. We fix input lag with non-blocking event polling, add the edit feature as a full vertical slice from application layer to TUI, watch the state machine grow from 3 to 4 variants with compiler-guided safety, and close with the key takeaways from the entire migration.</description>
      
    </item>
    
    <item>
      <title>Todo TUI in Rust 3. Events, terminal safety, and the migration moment of truth</title>
      <link>https://blog.rafaelfernandez.dev/posts/todo-tui-rust-3-events-terminal-safety-migration/</link>
      <pubDate>Sat, 21 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/todo-tui-rust-3-events-terminal-safety-migration/</guid>
      <description>The rat wires up the ears. We implement mode-specific event handlers with crossterm, redesign the key mapping to use a toggle instead of separate keys, solve the terminal restore problem with a capture-cleanup-return pattern, and run cargo test to discover that zero lines changed outside the adapter.</description>
      
    </item>
    
    <item>
      <title>Todo TUI in Rust 1. Scaffolding the TUI adapter and designing the state machine</title>
      <link>https://blog.rafaelfernandez.dev/posts/todo-tui-rust-1-scaffolding-tui-adapter-state-machine/</link>
      <pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/todo-tui-rust-1-scaffolding-tui-adapter-state-machine/</guid>
      <description>We start a new series by migrating the CLI adapter to a ratatui TUI. We set up the new dependencies, design the module structure under adapters/tui/, model the interaction modes as an enum to make invalid states unrepresentable, and solve the ownership puzzle of cloning a repository in a persistent session.</description>
      
    </item>
    
    <item>
      <title>Traits are grammars too: a small design lesson that kept nagging at me</title>
      <link>https://blog.rafaelfernandez.dev/posts/traits-are-grammars-too-from-contract-design-to-formal-syntax/</link>
      <pubDate>Wed, 28 Jan 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/traits-are-grammars-too-from-contract-design-to-formal-syntax/</guid>
      <description>While revisiting the TaskRepository trait from the Todo CLI series, I realized I was doing more than drawing an architectural boundary. I was also defining what could be said across that boundary, which is much closer to grammar than I first admitted.</description>
      
    </item>
    
    <item>
      <title>Todo CLI in Rust 5. Next step moving from CLI to a TUI with ratatui</title>
      <link>https://blog.rafaelfernandez.dev/posts/todo-cli-rust-5-cli-to-tui-with-ratatui/</link>
      <pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/todo-cli-rust-5-cli-to-tui-with-ratatui/</guid>
      <description>We close the series by exploring what it means to migrate from CLI to TUI with ratatui: how the interaction model changes, what frictions Rust introduces with ownership and &amp;amp;mut in a persistent event loop, and why hexagonal architecture absorbs the change without surgery.</description>
      
    </item>
    
    <item>
      <title>Todo CLI in Rust 4. Building the CLI with clap: typed parsing, subcommands and dual output</title>
      <link>https://blog.rafaelfernandez.dev/posts/todo-cli-rust-4-building-cli-with-clap/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/todo-cli-rust-4-building-cli-with-clap/</guid>
      <description>We design the CLI layer with clap derive, typed argument parsing with ValueEnum and FromStr for UUIDs, subcommands as enums, global &amp;ndash;output flag for dual table/json output, and errors propagated through layers down to stderr.</description>
      
    </item>
    
    <item>
      <title>Todo CLI in Rust 3.1. Testing strategy and explicit technical debt</title>
      <link>https://blog.rafaelfernandez.dev/posts/todo-cli-rust-3-1-testing-strategy-technical-debt/</link>
      <pubDate>Sun, 18 Jan 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/todo-cli-rust-3-1-testing-strategy-technical-debt/</guid>
      <description>We analyze the repository&amp;rsquo;s testing strategy: behavior-driven tests for each adapter, isolation with tempdir, why there are no shared tests, and the technical debt we decided to document instead of hide.</description>
      
    </item>
    
    <item>
      <title>Todo CLI in Rust 3. JSON persistence, contract vs implementation</title>
      <link>https://blog.rafaelfernandez.dev/posts/todo-cli-rust-3-json-persistence-contract-vs-implementation/</link>
      <pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/todo-cli-rust-3-json-persistence-contract-vs-implementation/</guid>
      <description>Third part of the series: we define the persistence contract with a generic trait, implement two adapters (in-memory and JSON to disk), and delve into the difference between interface and implementation as the axis of hexagonal architecture.</description>
      
    </item>
    
  </channel>
</rss>
