<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rizal Yogi Pratama on Medium]]></title>
        <description><![CDATA[Stories by Rizal Yogi Pratama on Medium]]></description>
        <link>https://medium.com/@rzlyp?source=rss-b3f2d80a4eb5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3jY5dLE9YYuowN1jurKM9Q.jpeg</url>
            <title>Stories by Rizal Yogi Pratama on Medium</title>
            <link>https://medium.com/@rzlyp?source=rss-b3f2d80a4eb5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:34:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rzlyp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I Moved From a Breaking Big Ball of Mud to a Modular Monolith That Actually Scales]]></title>
            <link>https://medium.com/@rzlyp/how-i-moved-from-a-breaking-big-ball-of-mud-to-a-modular-monolith-that-actually-scales-45aba327b652?source=rss-b3f2d80a4eb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/45aba327b652</guid>
            <dc:creator><![CDATA[Rizal Yogi Pratama]]></dc:creator>
            <pubDate>Wed, 01 Jul 2026 02:29:55 GMT</pubDate>
            <atom:updated>2026-07-01T02:29:55.145Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aWMYZ_Pnq4S5fengB4ugNQ.png" /></figure><p><em>After 7+ years building backend systems, I learned that architecture problems rarely show up as “architecture problems.” They show up as production incidents at 3 a.m.</em></p><h3>The 3 A.M. Wake-Up Call I Won’t Forget</h3><p>“Production is down.”</p><p>That message landed on my phone like it always does — short, calm, and somehow terrifying.</p><p>I already knew what happened before opening my laptop.</p><p>A few days earlier, a “small” change had gone in. Just a simple update to the code. Nothing risky on paper. But in reality, it silently broke the many flows.</p><p>No one noticed immediately. Because nothing was obviously connected.</p><p>And that was the problem.</p><p>That was the moment I stopped calling it “technical debt.”</p><p>It was just entropy.</p><h3>When “It Works” Slowly Turns Into “We’re Afraid to Touch It”</h3><p>Every growing backend system starts the same way.</p><p>Simple structure. Clear logic. Fast iteration.</p><p>Then reality kicks in:</p><ul><li>Features ship faster than architecture evolves</li><li>Temporary workarounds become permanent</li><li>Business logic spreads across random services and files</li><li>Everything becomes “somewhere in the codebase”</li></ul><p>At some point, the system becomes what people politely call a <em>Big Ball of Mud</em>.</p><p>And the worst part isn’t the mess itself.</p><p>It’s the fear.</p><p>Developers stop making clean changes because every change feels like it might break something unrelated.</p><p>That’s when I knew we had a deeper problem than code quality.</p><p>We had a structural problem.</p><h3>The Microservices Phase (and the Illusion of Control)</h3><p>Like many teams, our first “serious” reaction was microservices.</p><p>It felt like the correct engineering response:</p><ul><li>Split responsibilities</li><li>Isolate services</li><li>Decouple everything</li><li>Scale independently</li></ul><p>So we did exactly that.</p><p>We broke a single system into multiple services, each with its own repository, deployment pipeline, and database boundaries.</p><p>On paper, it looked like progress.</p><p>In practice, it introduced a different kind of complexity:</p><ul><li>One feature required changes across multiple services</li><li>Debugging required jumping across logs and systems</li><li>Deployment coordination became a daily ritual</li><li>Small changes became operationally expensive</li></ul><p>We didn’t reduce complexity.</p><p>We redistributed it.</p><p>And worse, we increased the cost of coordination.</p><p>At that point, I realized something uncomfortable:</p><p>We didn’t need a distributed system.</p><p>We needed better boundaries inside a single system.</p><h3>Rediscovering the Modular Monolith</h3><p>The solution wasn’t new. It just wasn’t trendy.</p><p>A <strong>Modular Monolith</strong>.</p><p>One application. One deployment unit. One runtime.</p><p>But internally structured like a system of independent modules — each owning its own domain, logic, and rules.</p><p>The mental shift for me was simple:</p><p>Instead of splitting <em>deployment</em>, we split <em>responsibility</em>.</p><p>I started thinking in terms of “stations in a kitchen” rather than “separate restaurants.”</p><ul><li>Each station has a clear purpose</li><li>Each station owns its workflow</li><li>Stations don’t interfere with each other</li><li>But everything still works in one kitchen</li></ul><p>That’s what a modular monolith should feel like.</p><h3>How I Implemented It in Practice</h3><p>When I started building my current app — <strong>Skereal.online</strong>, an AI platform for fashion designers, I made a deliberate decision:</p><p>No microservices at the start. Only a modular monolith with strict boundaries.</p><p>The structure ended up like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*aWMYZ_Pnq4S5fengB4ugNQ.png" /></figure><pre>Each module is completely self-contained.</pre><p>Not just folders — actual ownership boundaries.</p><p>For example:</p><ul><li>auth only handles identity and session logic</li><li>project owns design creation and AI workflows</li><li>promotion generates marketing assets</li><li>trend handles external fashion intelligence</li><li>queue manages async AI jobs via Redis workers</li></ul><p>No module is allowed to casually reach into another module’s internals.</p><h3>The Rule That Makes Everything Work</h3><p>The entire system relies on one rule:</p><blockquote><strong><em>Modules can only interact through a defined public interface (“front door”).</em></strong></blockquote><p>Every module exposes only what it explicitly chooses to expose.</p><p>Nothing more.</p><p>So instead of this:</p><blockquote><em>“Let me just reach into that service and grab the data”</em></blockquote><p>We enforce:</p><blockquote><em>“Ask the module through its API contract”</em></blockquote><p>This sounds small, but it changes everything.</p><p>Because now:</p><ul><li>Internal refactors stay internal</li><li>Modules can evolve independently</li><li>Dependencies are visible and intentional</li><li>Breaking changes are immediately obvious</li></ul><p>Most importantly, the system becomes predictable again.</p><h3>What It Feels Like to Ship Features Now</h3><p>A recent example: I added a “Favorites” feature.</p><p>In a traditional monolith or messy system, this usually means:</p><ul><li>Searching across multiple files</li><li>Wiring logic into unrelated domains</li><li>Risking side effects everywhere</li></ul><p>In the modular monolith:</p><ol><li>I created a new module: favorites/</li><li>Implemented its logic in isolation</li><li>Connected it through the app entry point</li></ol><p>That’s it.</p><p>No cross-module surgery. No cascading risk. No fear of breaking checkout or authentication.</p><p>The result isn’t just cleaner code.</p><p>It’s faster decision-making.</p><h3>Async Work Without Microservices</h3><p>One common misconception is that background processing requires separate services.</p><p>In my case, it doesn’t.</p><p>The queue module handles everything async:</p><ul><li>AI image generation requests</li><li>Worker processing</li><li>Job state tracking</li><li>Redis-backed task execution</li></ul><p>All inside the same system.</p><p>No separate deployment pipeline. No service sprawl.</p><p>Just a clear boundary around asynchronous behavior.</p><h3>“But Will It Scale?”</h3><p>This is the question that always comes up.</p><p>And the honest answer is:</p><p>Most systems don’t fail because they couldn’t scale.</p><p>They fail because they couldn’t evolve.</p><p>A modular monolith gives you:</p><ul><li>Clean internal boundaries</li><li>Low operational overhead</li><li>Fast iteration speed</li><li>Easier debugging</li><li>Simpler deployments</li></ul><p>And when the time actually comes to scale?</p><p>You already have the exact boundaries needed to extract services cleanly.</p><p>Microservices become a <em>refactor</em>, not a rescue mission.</p><h3>What I’d Tell My Younger Self</h3><p>If I could go back to the early days of building systems, I wouldn’t say:</p><blockquote><em>“Use microservices early.”</em></blockquote><p>I also wouldn’t say:</p><blockquote><em>“Just keep everything in one codebase.”</em></blockquote><p>I’d say something more precise:</p><blockquote><em>“Build a monolith, but design it like a system of independent modules from day one.”</em></blockquote><p>Because the real skill isn’t splitting systems apart.</p><p>It’s designing them so they don’t fall apart in the first place.</p><h3>Closing Thought</h3><p>After years of scaling backend systems, I’ve learned this:</p><p>Architecture is not about sophistication.</p><p>It’s about reducing uncertainty for the people working inside the system.</p><p>For me, the modular monolith wasn’t just an architecture choice.</p><p>It was a way to make engineering feel safe again.</p><p>If this resonates, I’ll probably write next about how I structure internal module APIs and event boundaries without over-engineering them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45aba327b652" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Running a Multi-Tenant SaaS for 7 Years Taught Me]]></title>
            <link>https://medium.com/@rzlyp/what-running-a-multi-tenant-saas-for-7-years-taught-me-1816c048e9e6?source=rss-b3f2d80a4eb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1816c048e9e6</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[tech-lead]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Rizal Yogi Pratama]]></dc:creator>
            <pubDate>Thu, 07 May 2026 13:49:04 GMT</pubDate>
            <atom:updated>2026-05-07T14:04:15.275Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U0tCtvkLIB4yIzGVuMIgeg.png" /></figure><p>Seven years ago, I thought building software was mostly about writing good code.</p><p>I was wrong.</p><p>Running a multi-tenant SaaS for years teaches you something very different:</p><blockquote><em>Software engineering is mostly about managing complexity, trade-offs, and people under pressure.</em></blockquote><p>Especially when the system never stops growing.</p><p>When we started, things felt simple.</p><p>One application.<br>A few tenants.<br>Small traffic.<br>Manageable infrastructure.</p><p>Then reality happened.</p><p>More customers.<br>More custom requests.<br>More edge cases.<br>More deployments.<br>More pressure to move faster.</p><p>And suddenly, decisions that once felt harmless became long-term architectural baggage.</p><h3>Multi-Tenant Sounds Efficient… Until It Isn’t</h3><p>From the outside, multi-tenant architecture sounds beautiful:</p><ul><li>shared infrastructure</li><li>centralized deployments</li><li>easier maintenance</li><li>lower operational cost</li></ul><p>And yes, those benefits are real.</p><p>But over time, new challenges appear:</p><ul><li>tenant-specific behavior</li><li>conflicting requirements</li><li>scaling issues</li><li>deployment risks</li><li>data isolation concerns</li><li>debugging complexity</li></ul><p>The hardest part is this:</p><blockquote><em>Every “small custom request” slowly pushes the platform away from standardization.</em></blockquote><p>And once that happens, complexity grows exponentially.</p><h3>Legacy Systems Don’t Break Overnight</h3><p>People love talking about “bad legacy code.”</p><p>But after years maintaining production systems, I learned something important:</p><blockquote><em>Most legacy systems were reasonable decisions at the time they were created.</em></blockquote><p>The real problem is accumulation.</p><p>Small shortcuts.<br>Temporary fixes.<br>Urgent business requests.<br>Unfinished refactors.</p><p>Individually? Fine.<br>Combined over years? Dangerous.</p><p>And in SaaS environments, you rarely get the luxury to stop everything and rewrite properly.</p><p>Because customers still expect:</p><ul><li>uptime</li><li>new features</li><li>bug fixes</li><li>stability</li></ul><p>All at the same time.</p><h3>Infrastructure Eventually Becomes the Product</h3><p>At some point, I realized engineering wasn’t just about features anymore.</p><p>Infrastructure became critical:</p><ul><li>CI/CD pipelines</li><li>deployment reliability</li><li>queue systems</li><li>Redis optimization</li><li>database performance</li><li>AWS cost management</li><li>monitoring</li><li>disaster recovery</li></ul><p>A feature means nothing if:</p><ul><li>deployments fail</li><li>queues stop processing</li><li>DNS breaks</li><li>CPU usage spikes</li><li>scaling becomes unstable</li></ul><p>One of the biggest lessons for me:</p><blockquote><em>Stability is a feature.</em></blockquote><p>And users absolutely notice when it’s missing.</p><h3>Communication Scales Slower Than Systems</h3><p>As the platform grew, the technical problems became easier than the organizational ones.</p><p>More engineers meant:</p><ul><li>more alignment needed</li><li>more communication gaps</li><li>more ownership confusion</li><li>more dependency management</li></ul><p>A system can scale horizontally.</p><p>Human understanding cannot.</p><p>That’s why engineering leadership becomes critical in long-running SaaS products.</p><p>Not just technical leadership.<br>Operational leadership.<br>Communication leadership.</p><h3>Technical Debt Is Not Always Bad</h3><p>This one took me years to accept.</p><p>Engineers often treat technical debt like failure.</p><p>But in real businesses, technical debt is sometimes survival.</p><p>The key difference is:</p><ul><li>intentional debt vs careless debt</li></ul><p>Intentional debt:</p><ul><li>documented</li><li>understood</li><li>temporary</li><li>tied to business value</li></ul><p>Careless debt:</p><ul><li>ignored</li><li>hidden</li><li>unmanaged</li></ul><p>After years in production systems, I stopped asking:</p><blockquote><em>“Can we make this perfect?”</em></blockquote><p>And started asking:</p><blockquote><em>“Can we make this sustainable?”</em></blockquote><p>That mindset changes everything.</p><h3>Burnout Happens Quietly</h3><p>Nobody talks enough about this part.</p><p>Long-running SaaS systems create invisible mental pressure:</p><ul><li>constant incidents</li><li>production anxiety</li><li>deployment stress</li><li>endless context switching</li></ul><p>Especially in leadership positions.</p><p>Because even when you’re offline…<br>part of your brain never fully disconnects from the system.</p><p>I’ve learned that sustainability matters not only for infrastructure, but also for engineers.</p><h3>The Biggest Lesson</h3><p>After 7 years, the biggest thing I learned is this:</p><blockquote><em>Building software is easy compared to maintaining software responsibly over time.</em></blockquote><p>Anyone can build version 1.</p><p>The real challenge is:</p><ul><li>keeping systems stable</li><li>helping teams evolve</li><li>surviving organizational changes</li><li>scaling without collapsing</li><li>making decisions under uncertainty</li></ul><p>That’s where real engineering begins.</p><p>And honestly?</p><p>Despite all the stress, incidents, mistakes, and complexity…</p><p>I still love building systems.</p><p>Just with a very different perspective now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1816c048e9e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being a Tech Lead in an Unstable Company]]></title>
            <link>https://medium.com/@rzlyp/being-a-tech-lead-in-an-unstable-company-7571173bf919?source=rss-b3f2d80a4eb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7571173bf919</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech-leadership]]></category>
            <dc:creator><![CDATA[Rizal Yogi Pratama]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 03:37:33 GMT</pubDate>
            <atom:updated>2026-05-07T04:37:04.706Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Being a Tech Lead in an Growth Company</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*kFzHIuMrqMtQN4WE" /></figure><p>Not every Tech Lead story is about scale, growth, and success.</p><p>Sometimes, it’s about survival.</p><p>I’ve been in situations where the company wasn’t stable — unclear direction, shifting priorities, sudden changes in leadership, or even financial uncertainty.</p><p>And let me tell you: being a Tech Lead in that environment is a completely different game.</p><p><strong>You’re Not Just Leading Tech Anymore</strong></p><p>In a stable company, your focus is clear:</p><ul><li>Build scalable systems</li><li>Improve performance</li><li>Deliver features</li></ul><p>In an unstable company, your role expands:</p><ul><li>Protect the team from chaos</li><li>Translate unclear business decisions into something executable</li><li>Decide what <em>not</em> to build</li></ul><p>You become a buffer.</p><p><strong>Priorities Change… Constantly</strong></p><p>One week you’re optimizing infrastructure.<br>Next week, everything is about cost-cutting.<br>Then suddenly, a “high-priority” feature appears out of nowhere.</p><p>The hardest part isn’t the work — it’s the <strong>lack of consistency</strong>.</p><p>As a Tech Lead, you have to:</p><ul><li>Re-align the team again and again</li><li>Keep everyone focused despite shifting goals</li><li>Prevent burnout from endless context switching</li></ul><p><strong>Morale Becomes Your Responsibility</strong></p><p>When uncertainty hits, people start asking:</p><ul><li>“Is this company going to survive?”</li><li>“Should I start looking elsewhere?”</li><li>“Does anything we build even matter?”</li></ul><p>And here’s the truth:<br>You won’t always have the answers.</p><p>But your team will look at you anyway.</p><p>Your job is not to fake confidence — but to provide <strong>clarity where you can, and honesty where you can’t</strong>.</p><p><strong>You Make More Trade-offs Than Ever</strong></p><p>In unstable conditions:</p><ul><li>You choose speed over perfection</li><li>You accept technical debt (knowingly)</li><li>You prioritize impact over elegance</li></ul><p>This is where experience matters.</p><p>Anyone can design a “perfect system” on paper.<br>But in reality, sometimes the best decision is the one that keeps the business alive.</p><p><strong>Leadership Gets Tested Here</strong></p><p>It’s easy to look like a good leader when everything is working.</p><p>Real leadership shows when:</p><ul><li>Decisions are unclear</li><li>Pressure is high</li><li>Outcomes are uncertain</li></ul><p>You’ll be forced to:</p><ul><li>Push back on unrealistic expectations</li><li>Say “no” more often</li><li>Make decisions with incomplete information</li></ul><p>And sometimes… you’ll get it wrong.</p><p>That’s part of it.</p><p><strong>What I’ve Learned</strong></p><ol><li><strong>Clarity is more valuable than certainty</strong><br>Even if things are unclear, give your team direction.</li><li><strong>Protect your team’s energy</strong><br>Chaos outside shouldn’t become chaos inside.</li><li><strong>Don’t blindly follow bad decisions</strong><br>Push back when needed — respectfully, but firmly.</li><li><strong>Know when to invest vs. when to survive</strong><br>Not every problem needs a long-term solution.</li><li><strong>Take care of yourself too</strong><br>Leading in instability is exhausting.</li></ol><p>Being a Tech Lead in an unstable company isn’t glamorous.</p><p>It’s messy, stressful, and sometimes frustrating.</p><p>But it will teach you more about leadership than any “perfect” environment ever could.</p><p>And if you can navigate this well — <br>you won’t just become a better engineer.</p><p>You’ll become a real leader.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7571173bf919" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day in My Life as a Tech Lead (Who Still Loves Getting His Hands Dirty)]]></title>
            <link>https://medium.com/@rzlyp/a-day-in-my-life-as-a-tech-lead-who-still-loves-getting-his-hands-dirty-0c36a54e7807?source=rss-b3f2d80a4eb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c36a54e7807</guid>
            <category><![CDATA[tech-lead]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Rizal Yogi Pratama]]></dc:creator>
            <pubDate>Wed, 15 Apr 2026 03:17:47 GMT</pubDate>
            <atom:updated>2026-04-15T03:17:47.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hkMhxPegPjk5SnO3PBajcw.png" /></figure><p>Being a Tech Lead isn’t just about architecture diagrams, sprint planning, or sitting in endless meetings. At least, that’s not how I do it.</p><p>After 6 years working on the same product — growing from an engineer into a Tech Lead — I’ve learned that this role is less about “being the smartest person in the room” and more about making sure the room works.</p><p>Here’s what a typical day looks like for me.</p><p><strong>Morning: Align Before You Build</strong></p><p>My day usually starts by checking overnight updates — deployments, alerts, Slack notifications, and sometimes unexpected issues (because of course 😄).</p><p>Then comes alignment:</p><ul><li>Reviewing what the team is working on</li><li>Making sure priorities still make sense</li><li>Checking if anyone is blocked</li></ul><p>At this level, problems are rarely “just technical.” Sometimes it’s unclear requirements. Sometimes it’s miscommunication. Sometimes it’s just someone stuck but not speaking up.</p><p>My job here is simple: remove friction.</p><p><strong>Midday: Context Switching Is the Real Skill</strong></p><p>By noon, I’ve already switched roles multiple times:</p><ul><li>Reviewing backend code (Laravel legacy is still alive 👀)</li><li>Discussing frontend decisions (Nuxt, Qwik)</li><li>Looking into infrastructure (AWS, Nginx, CI/CD pipelines)</li><li>Helping debug issues that somehow only happen in production</li></ul><p>People think Tech Leads “don’t code anymore.”</p><p>That’s not true.</p><p>I just code differently now. Less feature work, more problem-solving. Less building from scratch, more unblocking others.</p><p><strong>Afternoon: People &gt; Code</strong></p><p>This is the part many engineers underestimate.</p><p>Managing 10+ people across backend, frontend, and product means:</p><ul><li>Making sure leads are aligned</li><li>Giving direction without micromanaging</li><li>Translating business needs into technical decisions</li></ul><p>Sometimes I need to push back on bad ideas.<br>Sometimes I need to admit I was wrong.<br>Sometimes I need to support someone who’s struggling.</p><p>Technical skills got me here. People skills are what actually make me effective.</p><p><strong>Evening: When Real Work Happens</strong></p><p>Ironically, deeper work often happens after hours:</p><ul><li>Thinking about system design improvements</li><li>Planning infrastructure changes</li><li>Evaluating long-term risks in our stack</li></ul><p>Not because I have to — but because it’s the only time without interruptions.</p><p>Also… this is when I still get to enjoy building things. And I never want to lose that.</p><p><strong>What I’ve Learned So Far</strong></p><ol><li><strong>Being right is less important than being effective</strong><br>A perfect solution that no one understands is useless.</li><li><strong>Forcing decisions creates long-term damage</strong><br>Especially if you don’t understand the people or the system.</li><li><strong>Blaming teams is easy. Fixing systems is harder. Do the harder thing.</strong></li><li><strong>You don’t scale by doing more. You scale by enabling others.</strong></li><li><strong>Stay technical. Always.</strong><br>The moment you lose touch with the system, your decisions become guesses.</li></ol><p>Being a Tech Lead is messy. It’s not clean architecture diagrams or perfect sprints.</p><p>It’s trade-offs, people, pressure, and constant learning.</p><p>And honestly?<br>That’s what makes it fun.</p><p>If you’re growing into a Tech Lead role, don’t try to “look like a leader.”</p><p>Focus on making things work — systems, teams, and outcomes.</p><p>The title will follow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c36a54e7807" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microservice, Apaan tuh ?]]></title>
            <link>https://medium.com/codelabs-unikom/microservices-apaan-tuh-b9f5d56e8848?source=rss-b3f2d80a4eb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9f5d56e8848</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[microservice-architecture]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Rizal Yogi Pratama]]></dc:creator>
            <pubDate>Thu, 11 Jan 2018 07:07:30 GMT</pubDate>
            <atom:updated>2018-01-11T08:25:12.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xu1Ge_Cew0DHdSU6ETcpLQ.png" /><figcaption>Monolith &amp; Microservices (source image : <a href="http://www.weave.work/">www.weave.work</a>)</figcaption></figure><p>Jadi hari ini saya akan membagikan tentang apa sih Microservices itu ?</p><p>Kalo kata developer jaman now, kalo gak kenal microservices itu gak gaul ! Loh kok gak gaul? kenapa min??</p><p>Alasannya sederhana karena lagi hitz bingitz hehe, selain itu microservices juga dapat membantu deveoper dalam membuat aplikasi yang high performance, scalable, reliable dan secure.</p><p>Sebelum masuk ke ranah Microservices itu sendiri, saya akan membahas software arsitektur zaman OLD dan masih digunakan sampai saat ini , yaps itu adalah Monolitik Arsitektur.</p><h3><strong>Apa Itu Monolitik Arsitektur?</strong></h3><p>Seperti namanya “Mono” berarti satu , monolitik arsitektur merupakan sebuah arsitektur dimana dalam pembuatan aplikasi. semua komponen menjadi satu kesatuan.</p><p>btw satu kesatuan gimana yaa ?</p><p>Dalam hal ini satu kesatuan berarti menyatukan antara front-end dan backend dalam satu aplikasi yang sama.</p><p>Sebagai contoh yaitu aplikasi enterprise</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CpAuNzz0UMvlGvtG_fpOlQ.png" /></figure><p>Aplikasi Enterprise dibangun dalam tiga bagian: database , client-side, dan server-side. Dimana Server-side akan menangani request HTTP kemudian menjalankan beberapa logika sesuai dengan domain, kemudian mengambil dan memperbarui data dari database, dan mengurim data tersebut ke sisi client-side.</p><p>Nah itulah yang disebut dengan Monolitik, dan ada beberapa penyalah gunaan arsitektur ini yaitu <strong>MENULIS QUERY LANGSUNG DI CLIENT-SIDENYA , </strong>hayooo ngaku siapa yang pernah atau justru sering hehe</p><p><strong>Lalu kekurangan aplikasi monolitik itu apa sih?</strong></p><ol><li>Ketika aplikasi menjadi besar (banyak yang akses) peforma akan menurun (kecuali punya banyak duit buat bayar server yang lebih bagus LOL)</li><li>Ketika akan merubah teknologi pada aplikasi maka akan merubah secara keselutuhan aplikasi.</li><li>Jika terjadi error pada salah satu fungsi maka akan mempengaruhi keselutuhan aplikasi.</li></ol><p><strong>Kelebihan</strong></p><ol><li>Mudah dibangun</li><li>Mudah di uji</li><li>Mudah di deploy ke server atau cloud</li></ol><h3><strong>Lalu, Apa sih Microservice Itu?</strong></h3><p>Microservices berarti membagi aplikasi menjadi layanan yang lebih kecil dan saling terhubung tidak seperti aplikasi monolitik. Setiap microservice merupakan aplikasi kecil yang memiliki arsitektur heksagonal sendiri yang terdiri dari logika beserta berbagai adapternya (bahasa pemrograman, dll).</p><p>Pola arsitektur Microservice secara signifikan mempengaruhi hubungan antara aplikasi dan database. Alih-alih berbagi skema database tunggal dengan services lainnya, masing-masing services memiliki skema database tersendiri. Di satu sisi, pendekatan ini bertentangan dengan gagasan model data enterprise-wide. Selain itu, sering kali menghasilkan duplikasi beberapa data. Namun, memiliki skema database per service sangat penting jika ingin mendapatkan keuntungan dari layanan microservice. Masing-masing service memiliki database sendiri. Selain itu, services dapat menggunakan jenis database dan bahasa pemrograman yang paling sesuai dengan kebutuhannya.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*LWc55_UCWZAZr7Vke6fweg.png" /><figcaption>Contoh Arsitektur Microservices</figcaption></figure><p>Jadi intinya microservice yaitu membagi service ke bagian yang lebih kecil dimana service — service tersebut saling berhungan satu sama lain.Selain itu, dalam setiap services yang dibuat bisa menggunakan teknologi yang berbebeda.</p><p>Sedangkan untuk implementasi ke web, android, iOS dll tidak bisa secara langsung. Dimana kita harus membuat terlebih dahulu yang namanya API Gateway. API Gateway memiliki tugas seperti load balancing, caching, access controll , API metering, dan monitoring.</p><p><strong>Kelebihan Microservice</strong></p><ol><li>Aplikasi scalabale, secure dan reliable</li><li>Setiap service berdiri sendiri</li><li>Maintence-nya lebih mudah</li><li>Tidak ada hambatan dalam menggunakan teknologi baru</li><li>Setiap tim developer dapat mengembangkan setiap services-nya tanpa ada mengganngu services yang lain</li></ol><p><strong>Kekurangan</strong></p><ol><li>Ketika satu entity pada database berubah maka setiap entity yang sama di setiap database service harus diubah</li><li>Untuk beberapa kasus , sulit untuk menerapkan perubahan services jadi perlu perancangan yang matang.</li><li>Deployment yang kompleks, perlu konfigurasi untuk menjalankan setiap services karena memiliki runtime yang berbebda, tidak seperti aplikasi monolitik tinggal upload , deploy dan beres.</li><li>Perlu automation yang tinggi dalam melakukan deployment.</li></ol><p>Setiap arsitektur memiliki kelebihan dan kekurangan masing — masing, sepeti halnya kita manusia :)</p><p>Sekian yang bisa saya bagikan, jika ada pertanyaan, sanggahan atau kesalahan silahkan tulis komentar anda di kolom komentar. Soalnya saya juga sedang belajar :).</p><p>~Happy Coding</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9f5d56e8848" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codelabs-unikom/microservices-apaan-tuh-b9f5d56e8848">Microservice, Apaan tuh ?</a> was originally published in <a href="https://medium.com/codelabs-unikom">UNIKOM Codelabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Authentication Menggunakan GO dan Mysql Part #2]]></title>
            <link>https://medium.com/codelabs-unikom/simple-authentication-menggunakan-go-dan-mysql-part-2-e9c41379d880?source=rss-b3f2d80a4eb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9c41379d880</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[golang]]></category>
            <dc:creator><![CDATA[Rizal Yogi Pratama]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 12:21:53 GMT</pubDate>
            <atom:updated>2018-01-08T14:28:49.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*DTDy7DlbXOZLXhYfvMFV5w.png" /></figure><p>Yo what’s up guys , jika kalin masuk ke tutorial part berarti kalian udah beres ya di <a href="https://medium.com/codelabs-unikom/simple-login-menggunakan-go-dan-mysql-part-1-41396844813">part#1 </a>, kali ini disini akan membahas tentang login itu sendiri menggunakan bahasa GO dan database Mysql dengan melanjutkan project yang sebelumnya, jadi jangan dihapus ya yang sebelumnya :).</p><h3><strong>Library yang dibutuhkan</strong></h3><ol><li>Bcrypt</li><li>Session</li></ol><p>Tapi jangan khawatir karena semua library tersebut telah kita install di <a href="https://medium.com/codelabs-unikom/simple-login-menggunakan-go-dan-mysql-part-1-41396844813">tutorial part 1</a> .</p><p>Yap kita lanjut lagi, pada tutorial kali ini yang akan kita buat yaitu</p><ol><li>Membuat View Login</li><li>Membuat Membuat Fungsi Login dan Session</li><li>Membuat Halaman Home</li><li>Membuat Fungsi Home</li><li>Membuat Fungsi Logout</li></ol><p>Seperti biasa tidak perlu berbasa basi, langsung saja masuk ke sesi tutorial dimulai dari step 1.</p><h3><strong>Membuat Halaman Login</strong></h3><p>Untuk membuat halaman login sekarang kalian buka file login.html dan masukkan kode dibawah ini</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2bdd9ce34ab82fc16babf41cda4dd74a/href">https://medium.com/media/2bdd9ce34ab82fc16babf41cda4dd74a/href</a></iframe><h3><strong>Membuat Fungsi Login</strong></h3><p>Yaps pada section kali ini kita akan membuat fungsi login dan ikuti kode dibawah ini.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6929a6a4fe83145812550ed4a5ed1b57/href">https://medium.com/media/6929a6a4fe83145812550ed4a5ed1b57/href</a></iframe><p>Pada kode diatas langkah yang dilakukan pertama kali yaitu pengecekan session, yap fungsi <strong>session.Start(w,r)</strong> digunakan untuk memulai session di server kita, kemudian kita akan mengecek adapah ada session username atau tidak, jika ada maka akan redirect ke halaman <strong>“/”</strong> atau home.</p><p>Sedangkan jika session tidak ada maka akan ada validasi lagi , apakah method yang digunakan untuk memanggil fungsi login merupakan method POST ? jika tidak maka akan memanggil halaman login.html yang telah kita buat sebelumnya.</p><p>Lalu jika mehod merupakan POST maka kita akan mengambil value username dan password dari form input dan menyimpannya di sebuah variabel.</p><p>Kemudian pada variabel <strong>users </strong>, kita akan mengambil data pengguna berdasarkan username yang dimasukkan.</p><p>Kemudian pada fungsi bcrypt.CompareHashAndPassword, disini kita akan mebandingkan password yang ada di database dengan password yang dimasukkan, dan tentu saja password tersebut sudah di-encrypt.</p><p>Setelah melakukan pengecekan , maka apabila password sama dengan password yang dimasukkan, maka fungsi <strong>bcrypt </strong>akan membalikkan nilai nil, begitu sebaliknya. Ketika password dan username benar maka username dan nama pengguna akan dimasukkan ke dalam session dan kemudian akan dialihkan ke halaman home, namun jika password salah maka akan dialihkan ke halaman Login.</p><h3><strong>Membuat Halaman Home</strong></h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/639412faf4b22e6c70b364ea248dba1a/href">https://medium.com/media/639412faf4b22e6c70b364ea248dba1a/href</a></iframe><p>Pada kode {{ .username}} digunakan untuk manampilkan variabel yang dikirimkan melalui fungsi home yang akan kita buat nanti.</p><h3><strong>Membuat Fungsi Home</strong></h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b115331aab4b29352540298f1869b35b/href">https://medium.com/media/b115331aab4b29352540298f1869b35b/href</a></iframe><p>Seperti biasa, setiap kali kita mau menggunakan session maka selalu awali dengan memanggil fungsi <strong>sessions.Start</strong>. Setelah memanggil fungsi sessions maka akan dilakukan validasi terlebih dahulu apakah session tersedia atau tidak, jika tidak maka akan dialihkan ke halaman login.</p><p>Namun, jika <strong>session </strong>tersedia maka kita akan langsung memanggil halaman home.html dengan mengirimkan data berupa username yang diambil dari session dengan message <strong>“Welcome to the Go !”</strong>.</p><p>Kemudian seperti biasa, selalu gunakan function handler untuk mngetahui jika terjadi error, setelah itu kita jalankan fungsi untuk memanggil halaman home.html .</p><h3><strong>Membuat Fungsi Logout</strong></h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d589b8f883fc3691de4b423e019b7aa9/href">https://medium.com/media/d589b8f883fc3691de4b423e019b7aa9/href</a></iframe><p>Yaps, pada fungsi diatas akan kita gunakan untuk menghapus sessions pada server dengan menggunakan fungsi <strong>sessions.Clear() </strong>dan <strong>sessions.Destroy() </strong>yang kemudian akan dialihkan ke halaman login.</p><p>Yaah selesai sudah tutorial kali ini , sekarang kalian jalankan project dan coba apakah berhasil atau tidak.</p><p>Jika ada pertanyaan komen aja yaa :), code lengkap ada di <a href="https://github.com/rzlyp/simple-login-go-mysql"><strong>Github</strong></a><strong> </strong>!</p><p>Terima Kasih sudah mengikuti tutorial kali ini</p><p>~ Happy Coding</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9c41379d880" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codelabs-unikom/simple-authentication-menggunakan-go-dan-mysql-part-2-e9c41379d880">Simple Authentication Menggunakan GO dan Mysql Part #2</a> was originally published in <a href="https://medium.com/codelabs-unikom">UNIKOM Codelabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Authentication Menggunakan GO dan Mysql Part #1]]></title>
            <link>https://medium.com/codelabs-unikom/simple-login-menggunakan-go-dan-mysql-part-1-41396844813?source=rss-b3f2d80a4eb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/41396844813</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[backend-development]]></category>
            <dc:creator><![CDATA[Rizal Yogi Pratama]]></dc:creator>
            <pubDate>Wed, 03 Jan 2018 10:25:40 GMT</pubDate>
            <atom:updated>2018-01-08T12:25:10.902Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*DTDy7DlbXOZLXhYfvMFV5w.png" /></figure><p>Yo what’s up guys? masih semangatkah buat ngoding ?</p><p>Kali ini saya akan membagikan sebuah tutorial mengenai Authentication/Login sederhana menggunakan Golang dan Mysql.</p><p>Sekilas tentang Golang, Golang merupakan sebuah bahasa pemrograman dengan bahasa dasarnya yaitu bahasa C, Golang Sendiri dibuat oleh perusahaan raksasa yaitu Google.</p><p>Oke Langsung Cekidot, btw jangan lupa install Go terlebih dahulu jika kalian belum install :)</p><p>Seperti judul artikel kali ini, pertama kalian buat sebuah Database dengan nama <strong>go_db </strong>dan membuat table bernama<strong> users </strong>atau kalian bisa melakukan copy-paste dari kode di bawah ini</p><pre>CREATE TABLE `users` (<br>  `id` int(11) NOT NULL AUTO_INCREMENT,<br>  `username` varchar(50) DEFAULT NULL,<br>  `first_name` varchar(200) NOT NULL,<br>  `last_name` varchar(200) NOT NULL,<br>  `password` varchar(120) DEFAULT NULL<br>) ENGINE=InnoDB DEFAULT CHARSET=latin1;</pre><p>Langkah selanjutnya yaitu langsung menuju ke project sederhana yang akan kita buat dan ikuti langkah-langkah di bawah ini ..</p><ol><li><strong>Buat struktur project sesuai dengan gambar di bawah ini</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*ZV3bYp1CSG9yHC7dXTXekg.png" /><figcaption>Struktur Project</figcaption></figure><p><strong>2. Buat halaman register pada file register.html</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5137bc01a980908cbd8c59b4f8d05ad5/href">https://medium.com/media/5137bc01a980908cbd8c59b4f8d05ad5/href</a></iframe><p><strong>3. Install library terlebih dahulu dan jalan perintah di bawah ini mengguna cmd satu per satu</strong></p><pre>go get database/sql<br><br>go get golang.org/x/crypto/bcrypt<br><br>go get github.com/go-sql-driver/mysql<br>go get github.com/kataras/go-sessions</pre><p><strong>4. Sekarang kalian buka file main.go dan kita akan melakukan setting up project</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/350cebd70e1e71fffb21cc61fdabc15e/href">https://medium.com/media/350cebd70e1e71fffb21cc61fdabc15e/href</a></iframe><p>Penjelasan kode di atas yaitu , kita melakukan import library yang dibutuhkan terlebih dahulu, kemudian kita melakukan inisialisai variabel untuk fungsi <strong>database </strong>dan <strong>error </strong>yang akan kita gunakan nanti.</p><p>Kemudian dilanjutkan dengan membuat model yang berisi ID, Username, FirstName, LastName dan Password.</p><p>Terakhir kita membuat fungsi <strong>connect_db </strong>dimana fumgsi ini digunakan untuk menghubungkan project kita ke mysql dengan username <strong>“root”</strong> pada alamat local yaitu <strong>127.0.0.1</strong> dan menggunkan database <strong>go_db </strong>dan dilanjutkan dengan error handle seperti yang tertera pada kode di atas</p><p><strong>5. Membuat routes, fungsi utama</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6a332eea0487de6a4a972bfb606951dd/href">https://medium.com/media/6a332eea0487de6a4a972bfb606951dd/href</a></iframe><p>Kode diatas merupakan lanjutan dari kode sebelumnya, dimana ada fungsi <strong>routes </strong>dan fungsi <strong>main</strong>. Pada fungsi routes <strong>http.handleFunc</strong> digunakan untuk membuat alamat url <strong>“/register”</strong> dengan memanggil fungsi <strong>register </strong>yang akan kita buat nanti.</p><p>fungsi main merupakan fungsi utama yang akan dijalankan saat program dijalankan dimana fungsi tersebut berisi <strong>connect_db</strong>, <strong>routes </strong>dan listen port dari program yang akan dijalankan pada port <strong>8000.</strong></p><p><strong>6. Membuat Fungsi QueryUser</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c809b1cbd7031beb673899e49c378800/href">https://medium.com/media/c809b1cbd7031beb673899e49c378800/href</a></iframe><p>Fungsi diatas akan kita gunakan untuk mengambil data pengguna berdasarkan username.</p><p><strong>7. Membuat fungsi register</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c96859cf82da8327139bf0d7846ac5a2/href">https://medium.com/media/c96859cf82da8327139bf0d7846ac5a2/href</a></iframe><p>Kode di atas adalah lanjutan dari kode sebelumnya, penjelasan kodenya yaitu ,</p><p>Dimulai dari kondisi <strong>r.Method != “POST”</strong> , dimana kode ini digunakan untuk melakukan validasi apabila method yang digunakan bukan <strong>POST </strong>maka akan menampilkan halaman registrasi yang ada pada folder <strong>views/register.html </strong>sedangkan jika method post maka data username, first_nama, last_name dan password dari form input akan di ambil dan disimpan pada suatu variabel.</p><p>Kemudian kita mengecek data berdasarkan username yang dikirimkan melalui form, apakah data tersebut ada atau tidak, jika tidak ada maka akan lanjut ke proses penyimpanan data ke database. Caranya sama seperti mysql pada umumnya hanya bedanya setiap value akan diganti dengan tanda tanya (?) dan tanda (?) akan diganti ketika perintah tersebut dieksekusi dimana value-nya akan diganti dengan varibel yang ada tanda (&amp;) dimana urutan datanya tergantung dengan posisi (?) yang telah ditulis sebelumnya.</p><p>Setelah ekeskusi selesai maka akan terdirek secara otomatis ke halaman login.</p><p>8. Jalankan Program</p><p>Setelah kalian menulis semua kode diatas sekrang saatnya menguji apakah program yang telah dibuat berjalan dengan baik atau tidak.</p><p>Yaps, langsung saja jalankan perintah di bawah ini pada cmd di direktori project.</p><pre>go run main.go</pre><p>maka akan muncul console log seperti</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/399/1*Wnl_E6ZKPHg8nVLlKEuDaQ.png" /></figure><p>Kemudian langsung masuk ke halaman <strong>localhost:8000/register</strong></p><p>Jika berhasil maka akan muncul tampilan seperti ini</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H5-M1Lb4y2IcZ2DkHdXntA.png" /><figcaption>Tampilan Register</figcaption></figure><p>Setelah itu kalian coba apakah berhasil masuk ke database atau tidak :)</p><p>untuk login ada di<strong> </strong><a href="https://medium.com/@rizalyogip/simple-authentication-menggunakan-go-dan-mysql-part-2-e9c41379d880"><strong>part 2</strong> </a>ya :D</p><p>Terima Kasih</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41396844813" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codelabs-unikom/simple-login-menggunakan-go-dan-mysql-part-1-41396844813">Simple Authentication Menggunakan GO dan Mysql Part #1</a> was originally published in <a href="https://medium.com/codelabs-unikom">UNIKOM Codelabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>