<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Pattern - Tag - Arkadiusz Plich - tech blog</title>
        <link>http://plich.me/tags/pattern/</link>
        <description>Pattern - Tag - Arkadiusz Plich - tech blog</description>
        <generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>Arkadiusz@Plich.me (Arkadiusz Plich)</managingEditor>
            <webMaster>Arkadiusz@Plich.me (Arkadiusz Plich)</webMaster><lastBuildDate>Sun, 29 Oct 2023 13:10:00 &#43;0200</lastBuildDate><atom:link href="http://plich.me/tags/pattern/" rel="self" type="application/rss+xml" /><item>
    <title>Parallel pattern</title>
    <link>http://plich.me/posts/5/parallel_run_pattern/</link>
    <pubDate>Sun, 29 Oct 2023 13:10:00 &#43;0200</pubDate><author>
        <name>Arkadiusz Plich</name>
    </author><guid>http://plich.me/posts/5/parallel_run_pattern/</guid>
    <description><![CDATA[<p>Sam Newman, in his book <a href="https://www.amazon.com/Monolith-Microservices-Evolutionary-Patterns-Transform/dp/1492047848" target="_blank" rel="noopener noreferrer">Monolith to microservices: Evolutionary Patterns to Transform your Monolith</a> walking through patterns designed to separating functionality from the monolith into microservices, described the pattern which even though might be hard to use and implement but could be very helpful if you are trying to migrate very risky piece of code to new service. This pattern is called the Parallel Run pattern, and today&rsquo;s post will be about it.</p>]]></description>
</item><item>
    <title>Branch of abstraction pattern</title>
    <link>http://plich.me/posts/4/branch_of_abstraction_pattern/</link>
    <pubDate>Sat, 21 Oct 2023 21:30:00 &#43;0200</pubDate><author>
        <name>Arkadiusz Plich</name>
    </author><guid>http://plich.me/posts/4/branch_of_abstraction_pattern/</guid>
    <description><![CDATA[<p>A few days ago, <a href="https://plich.me/posts/3/strangler_fig_pattern/" target="_blank" rel="noopener noreferrer">I wrote a post about the Strangler Fig pattern</a> designed to securely exclude some functionalities from one system to another. I mentioned that when you have a use case where you are changing calls within one system, you must alter all calls and redirect them to your new code.</p>]]></description>
</item><item>
    <title>Strangler fig pattern</title>
    <link>http://plich.me/posts/3/strangler_fig_pattern/</link>
    <pubDate>Thu, 19 Oct 2023 19:00:00 &#43;0200</pubDate><author>
        <name>Arkadiusz Plich</name>
    </author><guid>http://plich.me/posts/3/strangler_fig_pattern/</guid>
    <description><![CDATA[<p>While reading <a href="https://www.amazon.com/Building-Microservices-Designing-Fine-Grained-Systems/dp/B0BX5LC8HB" target="_blank" rel="noopener noreferrer">Building Microservices: Designing Fine-Grained Systems</a> a few weeks ago and <a href="https://www.amazon.com/Monolith-Microservices-Evolutionary-Patterns-Transform-ebook/dp/B081TKSSNN" target="_blank" rel="noopener noreferrer">Monolith to Microservices: Evolutionary Patterns To Transform Your Monolith</a> by Sam Newman I came across an interesting pattern called Strangler fig that is designed to help exclude some system functionalities, e.g. to the new module or new app. A few simple steps can save time and stress, so I think it is worth exploring.</p>]]></description>
</item></channel>
</rss>
