---
title: "Discussion on \"Building a notification orchestrator: a decision log\" | Hashnode"
description: "Discussion on \"Building a notification orchestrator: a decision log\". This isn’t a copy‑paste tutorial. It’s a behind‑the‑scenes look at why I chose a specific shape—hexagonal micro‑orchestrator on SNS → SQS—for a cross‑channel notification pipeline, and the trade‑offs I wrestled with along the way.\n\nProblem Statement\n..."
url: "https://hashnode.com/posts/building-a-notification-orchestrator-a-decision-log/68457b0b9798df00c5a120d7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building a notification orchestrator: a decision log](https://averageprogrammer.com/blog/building-a-notification-orchestrator-a-decision-log?utm_source=hashnode&utm_medium=feed)

This isn’t a copy‑paste tutorial. It’s a behind‑the‑scenes look at why I chose a specific shape—hexagonal micro‑orchestrator on SNS → SQS—for a cross‑channel notification pipeline, and the trade‑offs I wrestled with along the way. Problem Statement ...

Jun 8, 2025 · 3 min read · averageprogrammer.com  
Read the article

-   [#engineering](https://hashnode.com/tag/engineering)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#orchestration](https://hashnode.com/tag/orchestration)
-   [#aws](https://hashnode.com/tag/aws)
-   [#event-driven-architecture](https://hashnode.com/tag/event-driven-architecture)
-   [#technically](https://hashnode.com/tag/technically)

## Written by

[Carl Eubanks](https://hashnode.com/@averageprogrammer)

@averageprogrammer

  
[View profile](https://hashnode.com/@averageprogrammer)

1x engineer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.