<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Services on Brian Faust</title><link>https://vacua.dev/tags/services/</link><description>Recent content in Services on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://vacua.dev/tags/services/rss.xml" rel="self" type="application/rss+xml"/><item><title>The Strangler Pattern Still Needs an Exit Plan</title><link>https://vacua.dev/thoughts/the-strangler-pattern-still-needs-an-exit-plan/</link><pubDate>Fri, 01 Nov 2019 00:00:00 +0000</pubDate><guid>https://vacua.dev/thoughts/the-strangler-pattern-still-needs-an-exit-plan/</guid><description>&lt;p&gt;A replacement proof of concept imported one provider&amp;rsquo;s postal data into
PostgreSQL and served one existing JSON-RPC search method from a Go binary. A
checked-in request and response fixture preserved field names, nulls, empty
strings, ordering, and identifier shape. Import failure left the last committed
dataset intact.&lt;/p&gt;
&lt;p&gt;The slice deliberately excluded every other provider, the other RPC methods,
queues, schedulers, authentication, caching, operational interfaces, and
traffic cutover.&lt;/p&gt;
&lt;p&gt;That is a good proof of one vertical path. It is not a plan for retiring the
system around it.&lt;/p&gt;</description></item></channel></rss>