<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Communication &amp; API Design on An observer's log</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/</link><description>Recent content in Communication &amp; API Design on An observer's log</description><generator>Hugo</generator><language>en</language><atom:link href="https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/index.xml" rel="self" type="application/rss+xml"/><item><title>API Gateway</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/api-gateway/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/api-gateway/</guid><description>&lt;p&gt;🔴 P0 &amp;mdash; &lt;em&gt;appears in nearly every system design; the single entry point pattern&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Backend for Frontend (BFF)</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/backend-for-frontend/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/backend-for-frontend/</guid><description>&lt;p&gt;🟠 P1 &amp;mdash; &lt;em&gt;solves the &amp;ldquo;one API doesn&amp;rsquo;t fit all clients&amp;rdquo; problem&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Web-gRPC Proxy</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/web-grpc-proxy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/web-grpc-proxy/</guid><description>&lt;p&gt;🟠 P1 &amp;mdash; &lt;em&gt;decoupling internal gRPC from external REST via a stateless proxy&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Strangler Fig (API Migration)</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/strangler-fig/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/strangler-fig/</guid><description>&lt;p&gt;🟡 P2 &amp;mdash; &lt;em&gt;Martin Fowler&amp;rsquo;s pattern for incremental migration from monolith to microservices&lt;/em&gt;&lt;/p&gt;</description></item><item><title>API Versioning Strategies</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/api-versioning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/api-versioning/</guid><description>&lt;p&gt;🟠 P1 &amp;mdash; &lt;em&gt;how you evolve public APIs without breaking consumers&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Sync vs Async Communication</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/sync-vs-async/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/sync-vs-async/</guid><description>&lt;p&gt;🔴 P0 &amp;mdash; &lt;em&gt;the most fundamental inter-service communication decision&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Message Queue Patterns</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/message-queue-patterns/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/message-queue-patterns/</guid><description>&lt;p&gt;🔴 P0 &amp;mdash; &lt;em&gt;queues are the backbone of async architectures&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Choreography vs Orchestration</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/choreography-vs-orchestration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/choreography-vs-orchestration/</guid><description>&lt;p&gt;🔴 P0 &amp;mdash; &lt;em&gt;staff-level framing question: how do multi-service workflows coordinate?&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Outbox Pattern</title><link>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/outbox-pattern/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://blog.rtshkmr.com/reference/archi/patterns/communication-and-apis/outbox-pattern/</guid><description>&lt;p&gt;🟠 P1 &amp;mdash; &lt;em&gt;solves the dual-write problem; critical for exactly-once in event-driven systems&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>