<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/vendor/feed/atom.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
                        <id>https://phptoptens.com/authors/adriana-eka-prayudha/feed</id>
                                <link href="https://phptoptens.com/authors/adriana-eka-prayudha/feed" rel="self"></link>
                                <title><![CDATA[Artisan Weekly — Author Feed]]></title>
                    
                                <subtitle>Featured links for a given author across Artisan Weekly editions.</subtitle>
                                                    <updated>2026-05-21T15:15:26+01:00</updated>
                        <entry>
            <title><![CDATA[Service Layer vs Action Pattern vs Jobs in Laravel]]></title>
            <link rel="alternate" href="https://medium.com/@radenadri/service-layer-vs-action-pattern-vs-jobs-in-laravel-4f748bd2dfb7" />
            <id>https://medium.com/@radenadri/service-layer-vs-action-pattern-vs-jobs-in-laravel-4f748bd2dfb7</id>
            <author>
                <name><![CDATA[Adriana Eka Prayudha]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[It's very easy to start your application off and throw everything into the controllers and before you know it you have super large controllers that are messy to work with and difficult to change. Maybe its time to think about structuring your code In this post Adriana walks us through Service Layers, Action Patterns and using Laravel Jobs to help better structure your code.]]>
            </summary>
                                    <updated>2026-05-21T15:15:26+01:00</updated>
        </entry>
    </feed>
