<?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 Agil on Medium]]></title>
        <description><![CDATA[Stories by Agil on Medium]]></description>
        <link>https://medium.com/@aqilzeka99?source=rss-e2fb3eec7ff2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Kno74CtUWGQoRb_OxDypNQ.jpeg</url>
            <title>Stories by Agil on Medium</title>
            <link>https://medium.com/@aqilzeka99?source=rss-e2fb3eec7ff2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:18:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aqilzeka99/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[The Three Golden Rules of Distributed Systems]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@aqilzeka99/the-three-golden-rules-of-distributed-systems-3bd5132c3792?source=rss-e2fb3eec7ff2------2"><img src="https://cdn-images-1.medium.com/max/1672/1*awY4q-icUgvR8GIqEmRRhg.png" width="1672"></a></p><p class="medium-feed-snippet">Why latency, partial failure, and finite resources should shape every architecture decision.</p><p class="medium-feed-link"><a href="https://medium.com/@aqilzeka99/the-three-golden-rules-of-distributed-systems-3bd5132c3792?source=rss-e2fb3eec7ff2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@aqilzeka99/the-three-golden-rules-of-distributed-systems-3bd5132c3792?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bd5132c3792</guid>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 15:23:35 GMT</pubDate>
            <atom:updated>2026-09-25T16:37:19.973Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Eight AI Development Anti-Patterns That Make Applications Harder to Ship and Harder to Trust]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@aqilzeka99/eight-ai-development-anti-patterns-that-make-applications-harder-to-ship-and-harder-to-trust-e3ac4992b11c?source=rss-e2fb3eec7ff2------2"><img src="https://cdn-images-1.medium.com/max/1672/1*AQ_1t5-cbHeFtKzOhvjxJg.png" width="1672"></a></p><p class="medium-feed-snippet">Practical lessons on choosing the right architecture, keeping agents focused, and measuring what actually matters.</p><p class="medium-feed-link"><a href="https://medium.com/@aqilzeka99/eight-ai-development-anti-patterns-that-make-applications-harder-to-ship-and-harder-to-trust-e3ac4992b11c?source=rss-e2fb3eec7ff2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@aqilzeka99/eight-ai-development-anti-patterns-that-make-applications-harder-to-ship-and-harder-to-trust-e3ac4992b11c?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3ac4992b11c</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ai-agent]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 14:58:50 GMT</pubDate>
            <atom:updated>2026-09-25T14:58:50.924Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Java Backend Interview Practice (Middle-Senior) — Part 1]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/javarevisited/java-backend-interview-practice-middle-senior-part-1-3eed741001b4?source=rss-e2fb3eec7ff2------2"><img src="https://cdn-images-1.medium.com/max/1672/1*Nof2n-JpWkDDirP9r8m9eQ.png" width="1672"></a></p><p class="medium-feed-snippet">From immutability and garbage collection to resiliency, Kubernetes debugging, and system design</p><p class="medium-feed-link"><a href="https://medium.com/javarevisited/java-backend-interview-practice-middle-senior-part-1-3eed741001b4?source=rss-e2fb3eec7ff2------2">Continue reading on Javarevisited »</a></p></div>]]></description>
            <link>https://medium.com/javarevisited/java-backend-interview-practice-middle-senior-part-1-3eed741001b4?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3eed741001b4</guid>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[backend-development]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 21:32:57 GMT</pubDate>
            <atom:updated>2026-08-30T06:27:23.463Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Kiçik, amma davamlı əməllər]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@aqilzeka99/ki%C3%A7ik-amma-davaml%C4%B1-%C9%99m%C9%99ll%C9%99r-11c5129ed567?source=rss-e2fb3eec7ff2------2"><img src="https://cdn-images-1.medium.com/max/1672/1*3TbhphOFG7kNscjwIlj4kw.png" width="1672"></a></p><p class="medium-feed-snippet">&#x130;slami inki&#x15F;af yaln&#x131;z b&#xF6;y&#xFC;k d&#x259;yi&#x15F;iklikl&#x259;rl&#x259; ba&#x15F; vermir. &#xC7;ox vaxt insan&#x131; d&#x259;yi&#x15F;dir&#x259;n &#x15F;ey h&#x259;r g&#xFC;n t&#x259;krarlanan ki&#xE7;ik yax&#x15F;&#x131;l&#x131;qlard&#x131;r: vaxt&#x131;nda&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@aqilzeka99/ki%C3%A7ik-amma-davaml%C4%B1-%C9%99m%C9%99ll%C9%99r-11c5129ed567?source=rss-e2fb3eec7ff2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@aqilzeka99/ki%C3%A7ik-amma-davaml%C4%B1-%C9%99m%C9%99ll%C9%99r-11c5129ed567?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/11c5129ed567</guid>
            <category><![CDATA[davamli-emeller]]></category>
            <category><![CDATA[islam]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 20:38:39 GMT</pubDate>
            <atom:updated>2026-08-29T20:38:39.251Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Tech Lead and Responsibilities]]></title>
            <link>https://medium.com/@aqilzeka99/tech-lead-and-responsibilities-9ee65762d37d?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ee65762d37d</guid>
            <category><![CDATA[tech-lead]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Fri, 23 Jan 2026 19:45:41 GMT</pubDate>
            <atom:updated>2026-01-23T19:46:46.487Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong><em>A practical guide to empowering teams, driving technical quality, and leading effectively across agile ceremonies.</em></strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E6uKO9XMevr3EcbnIG3l-g.png" /></figure><p><strong>Who is a Tech Lead?</strong> A Tech Lead is a leadership role within a team often referred to as a Lead or Chief (e.g., technical lead, project lead, chief programmer, chief architect). They are responsible for guiding the technical direction of the team, mentoring team members, and ensuring the quality and delivery of technical work.</p><p><strong>Responsibilities of a Tech Lead:</strong> While specific duties may vary, some key outstanding themes of a tech lead’s responsibilities include:</p><ul><li>Empowering and enabling team members to grow and share leadership roles themselves.</li><li>Coaching and mentoring developers, facilitating their taking ownership of tasks and leadership roles.</li><li>Being involved in technical decisions, ensuring adherence to best practices, quality, and alignment with business goals.</li><li>Cultivating informal leadership and fostering psychological safety and transparency within the team.</li><li>Managing delegation effectively by ensuring that the people doing the work have the skills, tools, clear expectations, and support needed.</li></ul><p><strong>Daily Work of a Tech Lead:</strong></p><ul><li>Ensure team members are clear about their tasks and the expected outcomes.</li><li>Monitor team progress, remove blockers, and provide coaching or mentorship where needed.</li><li>Facilitate clear communication, transparency, and alignment with company goals.</li><li>Guard the team’s psychological safety and foster a culture of trust.</li><li>Conduct periodic reflection by soliciting feedback on what to stop/start/continue doing to improve team dynamics and delivery.</li></ul><p><strong>Tech Lead Role in Specific Agile Ceremonies:</strong></p><p><strong>In Retrospectives:</strong></p><ul><li>Encourage open and equal communication amongst team members.</li><li>Facilitate reflection on leadership roles and team dynamics to continuously improve.</li><li>Solicit feedback on processes and leadership to identify what the tech lead or team should start, stop, or continue doing.</li><li>Help the team internalise responsibility, promote psychological safety, and transparency.</li></ul><p><strong>In Planning Meetings:</strong></p><ul><li>Ensure a clear understanding of the scope, outcomes, and deadlines of the planned work.</li><li>Help set realistic boundary conditions for the sprint, such as budget, time, and quality expectations.</li><li>Align the team’s tasks with company goals and business importance to give a clear “why” context.</li><li>Support delegation by confirming the team understands what success looks like and reporting requirements.</li></ul><p><strong>In Grooming (Backlog Refinement):</strong></p><ul><li>Clarify and decompose work into discrete chunks so that delegation is effective and manageable.</li><li>Assess team readiness by verifying that people have the skills, tools, and understanding needed for upcoming work items.</li><li>Facilitate discussions to clarify acceptance criteria, dependencies, and priorities.</li></ul><p><strong>During the Sprint:</strong></p><ul><li>Support the team by ensuring proper self-monitoring and ownership of tasks rather than external control.</li><li>Be available to coach or mentor if the team encounters difficulties.</li><li>Monitor continuous delivery and integration processes to prevent blockers or production risks.</li><li>Align daily work with sprint goals and company objectives to foster trust and reliability within and outside the team.</li></ul><p>In summary, the tech lead acts as a technical mentor, facilitator, and leader who works daily to empower the team, clarify work, align with business objectives, and cultivate a healthy, transparent, and trusting team environment across all agile ceremonies and daily activities. They balance technical leadership with people leadership to ensure delivery and ongoing team growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ee65762d37d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What True Leadership Really Means]]></title>
            <link>https://medium.com/@aqilzeka99/what-true-leadership-really-means-20e5a633db9c?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/20e5a633db9c</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Fri, 07 Nov 2025 11:33:28 GMT</pubDate>
            <atom:updated>2025-11-07T11:47:19.101Z</atom:updated>
            <content:encoded><![CDATA[<h4>Great leaders don’t do everything themselves, they build systems that work even when they’re not around.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*alTMO9ucrkCyoHWvgePF4A.png" /></figure><p>Have you ever met a leader who seems to do it all, the one who works harder than anyone, fixes every problem, and jumps into every crisis? Admirable, right? But what if that kind of leadership actually sinks the ship instead of steering it?</p><p>This is the story of a captain and what he teaches us about the real meaning of leadership.</p><h4>The Captain Who Did Everything</h4><p>Imagine going on a cruise on a big ship with 200 passengers.<br> As you walk aboard, the captain greets everyone by name:<br> “Louise, welcome aboard.”<br> “Miles, great to see you.”<br> “Sally, come right in.”</p><p>You wonder, <em>how does he know everyone’s name? </em>It turns out, before boarding, he memorizes every passenger’s passport photo and name so he can greet each person personally. He truly cares about service quality.</p><p>You think, <em>what an amazing captain!</em></p><p>Later, in your cabin, you find a note on your pillow:</p><blockquote>“Dear Dave, your bed has been personally made by the captain himself, because he values quality.”</blockquote><p>Nice gesture, but strange. Does the captain really make everyone’s bed? When does he steer the ship?</p><p>The truth soon becomes clear:<br>The best way to ensure quality isn’t by doing everything yourself; it’s by <strong>building a system</strong> that provides quality through others.</p><h4>When Effort Turns Into Chaos</h4><p>At dinner, the captain is serving soup in a waiter’s uniform. He says he’s <em>“staying connected with the crew.” </em>Then, you find him later in the engine room, shovelling coal because a worker is sick.</p><p>He’s caring. Hardworking. Hands-on. But the ship is drifting. No one is steering it. It’s heading straight toward an iceberg.</p><p>At the last moment, he rushes to the bridge, grabs the wheel, and narrowly avoids disaster. He laughs, <em>“Wow, that was exciting! I love this job, never boring!”</em></p><p>But you think: <strong><em>This isn’t leadership. This is chaos.</em></strong></p><h4>The Real Job of a Leader</h4><p>You don’t want a captain who makes beds or serves soup. You want a captain who stands on the bridge, <strong>guiding the direction</strong> of the ship.</p><p>Leadership isn’t about doing everyone’s job. It’s about ensuring everyone <strong>can do their job well</strong>, through people, systems, and vision.</p><h4>The Three Core Responsibilities of a Leader</h4><ol><li><strong>People:</strong> The right people in the right roles, motivated and empowered.</li><li><strong>Systems:</strong> Clear, repeatable processes that ensure quality and accountability.</li><li><strong>Vision:</strong> A clear direction for where the ship (or company) is heading.</li></ol><p>If the ship crashes, it’s still the captain’s fault, even if he was in the bathroom, because he’s responsible for who was steering at that moment.</p><p>If the soup is too salty, that’s also his fault, because he hired the chef and designed the system.</p><p>In one sense, a captain “does nothing.” He asks, “Are the beds made? Is the system working?” But in another sense, <strong>he’s responsible for everything</strong>.</p><h4>When the Captain Is Gone</h4><p>Suppose everything runs perfectly, and one day, someone throws the captain overboard. For the first few days, nothing changes. The system still works. But over time, as the environment, customers, and challenges evolve, cracks start to show.</p><p>That’s when the captain’s true value becomes clear: <strong>Leadership is not maintenance, it’s renewal. </strong>Systems and people must constantly evolve.</p><p>If your team runs smoothly while you’re on vacation, it doesn’t mean you’re unnecessary. It means you’ve built a system that works, and that’s what great leadership looks like.</p><h3>Final Thoughts</h3><p><strong>A great leader doesn’t do everything.<br>A great leader builds people and systems that can thrive without them.</strong></p><p><em>Leadership is about balance between </em><strong><em>people</em></strong><em>, </em><strong><em>systems</em></strong><em>, and </em><strong><em>vision</em></strong><em>.<br></em> It’s about creating a living mechanism made of people and guiding it safely through every storm.</p><p>So, when you think of leadership, remember:<br><strong>Be the captain who steers the ship, not the one making beds below deck.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20e5a633db9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deep Dive LSM Tree (Internals of Cassandra, LevelDB, RocksDB, ScyllaDB)]]></title>
            <link>https://medium.com/@aqilzeka99/deep-dive-lsm-tree-internals-of-cassandra-leveldb-rocksdb-scylladb-2c4149db8d92?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c4149db8d92</guid>
            <category><![CDATA[cassandra]]></category>
            <category><![CDATA[rocksdb]]></category>
            <category><![CDATA[lsm-tree]]></category>
            <category><![CDATA[scylladb]]></category>
            <category><![CDATA[database-internals]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Fri, 17 Oct 2025 19:00:08 GMT</pubDate>
            <atom:updated>2025-10-17T19:00:08.246Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/751/0*P3cz0bwGoUwcTxl9" /><figcaption>Credit from: <a href="https://muhamedabdalla.hashnode.dev/the-power-of-lsm-tree">https://muhamedabdalla.hashnode.dev/the-power-of-lsm-tree</a></figcaption></figure><h3>1. What Is an LSM Tree?</h3><p><strong>Definition:<br></strong>An <strong>LSM Tree</strong> (Log-Structured Merge Tree) is a <strong>write-optimized</strong> data structure designed to efficiently handle high write throughput.</p><p>Instead of updating data in place (like B-Trees do), LSM Trees write new data <strong>sequentially</strong> to disk and later <strong>merge</strong> older data in the background.</p><p><strong>Goal:<br>- </strong>Maximize write performance<br>- Minimize random I/O<br>- Accept trade-offs in read and compaction cost</p><h3>2. Core Idea: Write Sequentially, Merge Later</h3><p>Traditional B-Trees (used in MySQL) perform <strong>in-place updates</strong>, which cause <strong>random disk I/O</strong> — slow on spinning disks (and even on SSDs with heavy concurrency).</p><p>LSM-Trees instead:</p><ol><li>Write incoming data sequentially into a <strong>memory buffer (MemTable)</strong>.</li><li>Periodically <strong>flush</strong> this buffer to disk as an <strong>immutable sorted file (SSTable)</strong>.</li><li>Background threads <strong>merge</strong> multiple SSTables to keep lookup times reasonable.</li></ol><p>This means <strong>writes are append-only</strong>, and <strong>reads require merging multiple sources</strong>.</p><h3>3. LSM Tree Architecture</h3><h4>1. MemTable (In-memory component)</h4><ul><li>Data is first written here.</li><li>Usually implemented as a <strong>balanced tree (like a Red-Black Tree or SkipList)</strong>.</li><li>Sorted by key.</li><li>When it reaches a size threshold, it’s <strong>flushed to disk</strong>.</li></ul><h4>2. Immutable MemTable</h4><ul><li>Before flushing, the current MemTable becomes <em>immutable</em> (read-only) to serve reads while flushing occurs.</li><li>A new MemTable is created for incoming writes.</li></ul><h4>3. SSTables (Sorted String Tables)</h4><ul><li>On-disk, immutable sorted files.</li><li>Each SSTable stores key-value pairs sorted by key.</li><li>Has an <strong>index</strong> (for fast key lookup) and a <strong>Bloom filter</strong> (to quickly check key existence).</li></ul><h4>4. Write-Ahead Log (WAL)</h4><ul><li>A sequential log on disk.</li><li>Ensures <strong>durability</strong> — if the system crashes before MemTable flush, data can be recovered from WAL.</li></ul><h4>5. Compaction</h4><ul><li>Periodic background process.</li><li>Merges SSTables to:<br>- Remove deleted or overwritten entries.<br>- Reduce lookup overhead.<br>- Maintain sorted order efficiently.</li></ul><h3>4. Data Flow in an LSM Tree</h3><h4>Write Path:</h4><ol><li>Write to <strong>WAL</strong> (for durability).</li><li>Insert into <strong>MemTable</strong>.</li><li>When full → flush MemTable → new <strong>SSTable</strong>.</li></ol><p><strong>Characteristics:<br>- </strong>Sequential I/O → fast writes<br>- No random writes → great for SSDs/HDDs</p><h4>Read Path:</h4><p>When reading key K:</p><ol><li>Check <strong>MemTable</strong> (most recent).</li><li>Check <strong>Immutable MemTables</strong>.</li><li>Check <strong>SSTables</strong> (from newest to oldest).</li><li>Use <strong>Bloom filters</strong> to skip files that definitely don’t have the key.</li><li>Merge results from multiple levels if duplicates exist.</li></ol><p><strong>Challenge:<br>- </strong>Reads may need to check multiple SSTables → slower reads.<br>- That’s why <strong>compaction</strong> is important.</p><h3>5. Advantages of LSM Trees</h3><p>✅ Extremely fast sequential writes<br>✅ Great for workloads with high write volume (e.g., time-series, logs, messaging)<br>✅ Compact on-disk structure<br>✅ Easy crash recovery (thanks to WAL)</p><h3>6. Disadvantages</h3><p>❌ Slower reads (especially if not well compacted)<br>❌ High background I/O from compaction<br>❌ Higher latency spikes during merge<br>❌ Write amplification (same data rewritten multiple times)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c4149db8d92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Pods in Kubernetes: Create, Watch, Troubleshoot]]></title>
            <link>https://medium.com/@aqilzeka99/understanding-pods-in-kubernetes-create-watch-troubleshoot-7dbaa0330e1a?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dbaa0330e1a</guid>
            <category><![CDATA[kubernetes-for-beginners]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[kubernetes-pods]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Fri, 25 Jul 2025 07:13:19 GMT</pubDate>
            <atom:updated>2025-07-25T07:38:57.392Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*MVYX34o__MCR8nPpZS9d5Q.png" /></figure><p>Welcome back, fellow cloud explorers! In our last adventure, we set up our own local Kubernetes cluster using Kind. If you haven’t, I highly recommend checking <a href="https://medium.com/@aqilzeka99/lets-create-a-local-kubernetes-cluster-with-kind-63c0589fb40b">“Let’s Create a Local Kubernetes Cluster with Kind”</a> first. <br>Now that our cluster is up and running, it’s time to work with <strong>Pods</strong>, the smallest deployable unit in Kubernetes.</p><p>In this article, we’ll cover:</p><ul><li>What a Pod is</li><li>How to create a simple Pod</li><li>Useful commands to inspect and troubleshoot Pods</li><li>Real-world error scenarios like CrashLoopBackOff and ImagePullBackOff</li></ul><p><strong>What is a Pod?</strong></p><p>According to the <a href="https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/">official Kubernetes documentation</a>:</p><blockquote><em>A </em><strong><em>Pod</em></strong><em> is the smallest and simplest unit in the Kubernetes object model that you can create or deploy. A Pod represents a single instance of a running process in your cluster.</em></blockquote><p>In simple terms:<br>- A Pod can contain <strong>one or more containers</strong> (usually one).<br>- Containers inside a Pod share the <strong>same network</strong> and <strong>storage volumes</strong>.<br>- They are scheduled <strong>together</strong> on the same node.</p><p>Think of a Pod like a wrapper around your application container(s), managing their lifecycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*6FTX7P-aZENWbi8pc0xYDQ.png" /><figcaption>This image shows the difference between pod and container</figcaption></figure><p>Imagine you’re building a <strong>Spring Boot app</strong> that connects to a <strong>PostgreSQL database</strong>. You could package both the application and the database into the <strong>same Pod</strong>, like the above image.</p><blockquote><strong>Real-World Best Practice</strong></blockquote><blockquote>In production, it’s usually <strong>not recommended</strong> to put your app and DB in the same Pod. Instead:<br>- Keep the <strong>database as a separate managed service</strong> or in a <strong>separate Pod</strong> with a <strong>Service</strong> in front of it.<br>- Use this co-located Pod setup only for <strong>local testing</strong>, <strong>CI pipelines</strong>, or <strong>small prototypes</strong>.</blockquote><p><strong>Create Your First Pod<br></strong>Let’s write a basic YAML file to define a Pod with a single NGINX container.<br>Create a file called 01-simple-pod.yml:</p><pre>apiVersion: v1     # Specifies the Kubernetes API version<br>kind: Pod          # Defines the type of Kubernetes object we&#39;re creating<br>metadata:          # Metadata about this Pod<br>  name: pod-1      # A unique name for our Pod<br>spec:              # The desired state specification for our Pod<br>  containers:      # List of containers to run inside this Pod<br>    - name: nginx  # Name of the container (must be unique within the Pod)<br>      image: nginx # The Docker image to use (nginx:latest from Docker Hub)</pre><p>To apply this configuration and create the Pod:</p><pre>kubectl apply -f 01-simple-pod.yml<br>Pro Tip: You can also use kubectl create -f — both work the same for Pod creation.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/1*-V0vOTlojCJ5ZdGfkivmEQ.png" /></figure><p><strong>Pro Tip:</strong> You can also use kubectl create -f — Both work the same for Pod creation.</p><p><strong>Live Monitor Your Pod</strong></p><p>You can monitor the Pod’s status live in the terminal:</p><pre># For Mac/Linux:<br>watch -t -x kubectl get pod<br><br>---<br># For Windows (PowerShell):<br><br>while ($true) {<br>  Clear-Host<br>  kubectl get pod<br>  Start-Sleep -Seconds 1<br>}</pre><p>Split your terminal vertically: one side for monitoring, the other for running commands.</p><p><strong>Inspect the Pod</strong></p><p>To see details about your Pod:</p><pre>kubectl describe pod pod-1</pre><p>You’ll see:<br>- Events (like container image pull)<br>- Networking info<br>- Mounted volumes (if any)<br>- Current state and reason</p><p><strong>Deleting the Pod</strong></p><p>To delete the Pod:</p><pre>kubectl delete -f 01-simple-pod.yml</pre><p><strong>Simulate Real-world Failures<br></strong>For <strong>ImagePullBackOff</strong>, update your YAML with an invalid image:</p><pre>image: nginx-nonexistent</pre><p>Then reapply the Pod:</p><pre>kubectl apply -f 01-simple-pod.yml</pre><p>Watch the error:</p><pre>kubectl describe pod pod-1</pre><p>You’ll see events like:</p><pre>Failed to pull image &quot;nginx-nonexistent&quot;: image not found<br>Back-off pulling image &quot;nginx-nonexistent&quot;</pre><p>For <strong>CrashLoopBackOff, </strong>change the container command in the YAML:</p><pre>apiVersion: v1<br>kind: Pod<br>metadata:<br>  name: pod-1<br>spec:<br>  containers:<br>    - name: nginx<br>      image: nginx<br>      command: [&quot;/bin/sh&quot;, &quot;-c&quot;, &quot;exit 1&quot;]<br>  restartPolicy: Always</pre><p>This will cause the container to crash immediately. Reapply and describe the pod:</p><pre>kubectl apply -f 01-simple-pod.yml<br>kubectl describe pod pod-1</pre><p>You’ll see the reason: <em>Back-off restarting failed container</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ovCkjI9qD9yFoTGT3wj5kA.png" /></figure><p><strong>CrashLoopBackOff </strong>happens when a container <strong>starts → crashes → restarts repeatedly</strong>.</p><p><strong>Common</strong><a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/"><strong> Pod Statuses</strong></a><strong> &amp; What They Mean</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*eFGuTd-o3wQOY-JaSGBbXw.png" /><figcaption>Common Pod Statuses</figcaption></figure><p><strong>Final Words</strong></p><p>Understanding Pods is fundamental to mastering Kubernetes. Start by playing with simple Pods like we did here, and we will deep dive with pods.</p><p>In the next article, we’ll cover <strong>Multiple pods with labels</strong>, <strong>multi container pods</strong> and etc.</p><p>Stay tuned!<br>If this helped, consider clapping 👏 and following for more hands-on Kubernetes content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dbaa0330e1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s Create a Local Kubernetes Cluster with Kind]]></title>
            <link>https://medium.com/@aqilzeka99/lets-create-a-local-kubernetes-cluster-with-kind-63c0589fb40b?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/63c0589fb40b</guid>
            <category><![CDATA[kubernetes-for-beginners]]></category>
            <category><![CDATA[docker-and-kubernetes]]></category>
            <category><![CDATA[local-kubernetes-cluster]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Wed, 23 Jul 2025 10:56:54 GMT</pubDate>
            <atom:updated>2025-07-30T08:04:44.699Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*CH8VzB1wGz1shDO2aLb9RA.png" /></figure><p>Welcome to the first article in my Kubernetes learning series! 🎉<br>If you’re new to Kubernetes, this is your easiest path to running a cluster <strong>locally</strong> — no cloud, no cost.</p><p>We’ll use Kind — short for “Kubernetes IN Docker.” It allows you to create Kubernetes clusters inside Docker containers.</p><h4><strong>Prerequisites</strong></h4><p>Before we get started, make sure you have the following tools installed:</p><p>1. <strong>Docker</strong><br><em>Download and install Docker from </em><a href="http://docker.com/"><em>docker.com</em></a></p><p>2. <strong>kubectl</strong><br><em>Install the Kubernetes CLI from </em><a href="https://kubernetes.io/docs/tasks/tools/"><em>here</em></a><em>. This allows you to interact with the cluster.</em></p><p>3. <strong>Kind</strong><br><em>Install Kind from: </em><a href="https://kind.sigs.k8s.io/docs/user/quick-start/#installation"><em>https://kind.sigs.k8s.io/docs/user/quick-start/#installation</em></a></p><p><strong>Step 1: Create Your Cluster Config<br></strong>In your project directory, create a file named 01-cluster.yml and paste in the following content:</p><pre>kind: Cluster<br>apiVersion: kind.x-k8s.io/v1alpha4<br>name: dev-cluster<br>nodes:<br>  - role: control-plane<br>  - role: worker<br>  - role: workeryaml</pre><p>This config defines a Kubernetes cluster with <strong>1 master node</strong> and <strong>2 worker nodes</strong>.</p><p><strong>Step 2: Spin Up the Cluster</strong></p><p>Run the following command in the same directory where 01-cluster.yml lives:</p><pre>kind create cluster --config 01-cluster.yml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*7vfexqQ2k3XidpGe-6nfjw.png" /></figure><p><strong>Boom!</strong> You now have a fully functional Kubernetes cluster running inside Docker containers.</p><p><strong>Step 3: Verify with Docker</strong></p><pre>docker ps</pre><p>You’ll see your containers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d704DUJNUd0jGNdIVK-aaA.png" /></figure><p><strong>Step 4: Interact with Your Cluster<br></strong>Check the node status using kubectl:</p><pre>kubectl get nodes</pre><p>And voilà!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*Wf-1CpMgBbULuzUwPOH3Gg.png" /></figure><p>You’re now running a real Kubernetes cluster locally. Pretty cool, right?</p><p><strong>Step 5: Clean Up — Delete Nodes</strong></p><p>Now that you’ve interacted with your cluster, you might want to clean up by deleting the running nodes. You can do this with a simple kubectl command:</p><pre>kubectl delete node --all  -&gt; remove all pods<br>kubectl delete node/node-1 or kubectl delete node node-1  -&gt; remove node-1</pre><p>This command removes <strong>all nodes or a specific pod </strong>in the current namespace</p><h3>What’s Next?</h3><p><strong><em>Next article: </em></strong><a href="https://medium.com/@aqilzeka99/understanding-pods-in-kubernetes-create-watch-troubleshoot-7dbaa0330e1a"><em>Understanding Pods in Kubernetes: Create, Watch, Troubleshoot</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63c0589fb40b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Work Productively with Environment Variables in Spring Boot]]></title>
            <link>https://medium.com/@aqilzeka99/how-to-work-productively-with-environment-variables-in-spring-boot-86af52b68dc8?source=rss-e2fb3eec7ff2------2</link>
            <guid isPermaLink="false">https://medium.com/p/86af52b68dc8</guid>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[environment-variables]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[environment]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Agil]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 03:04:42 GMT</pubDate>
            <atom:updated>2025-04-23T03:04:42.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FMbx0shM3zKZMbSPYC1Fog.png" /></figure><p>Introooo</p><p>Whether developing in Java, Python, Node.js, or any other language, <strong>environment variables</strong> can be your secret productivity weapon. They help you manage sensitive data like API keys, DB credentials, and configuration values without hardcoding anything in your codebase.</p><p>In this article, I’ll walk you through <strong>setting and using environment variables on macOS</strong>, with examples for Spring Boot developers and tips to improve your daily workflow.</p><p>If you apply the config in your company, you will save many developers&#39; time.</p><h4>🧠 Why Use Environment Variables?</h4><p>🔒 <strong>Security</strong>: Avoid committing secrets to your Git repository<br>⚙️ <strong>Configurability</strong>: Easily switch between environments (dev, test, prod)<br>🚀 <strong>Productivity</strong>: Set once, use everywhere — no need to edit config files each time</p><h4>🛠 Step 1: Set Environment Variables in Your Shell (Note: I use MacOS)</h4><p>Most macOS systems today use the zsh shell. To set environment variables:</p><ol><li>Open your terminal</li><li>Run:</li></ol><pre>nano ~/.zshrc</pre><p>3. Add your environment variables at the bottom:</p><pre>export DB_PASSWORD_DEV=my_secure_password<br>export DB_PASSWORD_TEST=my_secure_password</pre><p>4. Save and exit:</p><ul><li>Press Ctrl + O to save</li><li>Press Enter to confirm</li><li>Press Ctrl + X to exit</li></ul><p>5. Apply changes:</p><pre>source ~/.zshrc</pre><p>Now your variables are available in every terminal session.</p><p>6. You can see it in the terminal with bthe elow command:</p><pre>cat ~/.zshrc</pre><p>7. Or you can specifically see:</p><pre>echo $DB_PASSWORD_DEV</pre><h4>🧪 Step 2: Use Environment Variables in Your Application</h4><p>Let’s say you’re building a <strong>Spring Boot</strong> app. Instead of hardcoding credentials, configure your application.yml like this:</p><pre>spring:<br>  datasource:<br>    url: jdbc:postgresql://localhost:5432/mydb<br>    username: user<br>    password: ${DB_PASSWORD_DEV}</pre><h4>🧩 Step 3: IntelliJ or IDE Integration (Optional)</h4><p>If IntelliJ doesn’t automatically pick up your environment variables invalidate and restart your IntelliJ.</p><p>Then</p><p>1 -&gt; Go to <strong>Run &gt; Edit Configurations<br></strong>2 -&gt; Select your <strong>Spring Boot run</strong> config<br>3 -&gt; Select <strong>Environment Variables</strong> from <strong>Modify Options<br></strong>4 -&gt;<strong> </strong>In <strong>Environment Variables</strong>, click the <strong>edit environment variables </strong>icon<br>5 -&gt; Now you will see your added variables in the system environment variables like below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-M17iW0XClrzhFJCRdef7w.png" /></figure><h4>🎯 Final Thoughts</h4><p>Mastering environment variables is a small skill that makes a <strong>huge difference</strong> in the long run. It helps you stay organized, boost security, and focus on coding, without cluttering your configs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86af52b68dc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>