<?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 Ridmi Thilakarathna on Medium]]></title>
        <description><![CDATA[Stories by Ridmi Thilakarathna on Medium]]></description>
        <link>https://medium.com/@ridmisameera.18?source=rss-f80aa71e91e6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*51JiQdTrbC2BM-EV</url>
            <title>Stories by Ridmi Thilakarathna on Medium</title>
            <link>https://medium.com/@ridmisameera.18?source=rss-f80aa71e91e6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:08:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ridmisameera.18/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[Hidden Risks in Your Code: Simple Security Lessons for Developers]]></title>
            <link>https://medium.com/@ridmisameera.18/hidden-risks-in-your-code-simple-security-lessons-for-developers-85c1a830f3ea?source=rss-f80aa71e91e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/85c1a830f3ea</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ridmi Thilakarathna]]></dc:creator>
            <pubDate>Mon, 10 Nov 2025 13:04:32 GMT</pubDate>
            <atom:updated>2025-11-10T13:04:32.446Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I was assigned a few security-related tasks and honestly, it turned out to be a really eye-opening experience.</p><p>While security isn’t my main area of focus, I quickly realized just how crucial it is and how much developers need to pay attention to it. There’s a whole world happening behind the scenes to keep applications safe, and even tiny misconfigurations, overlooked settings, or unused features can create vulnerabilities that attackers could exploit.</p><p>I wanted to share some of the most interesting things I learned, so even if security isn’t part of your daily work, you’ll still go, “Ah, that actually makes sense!”</p><h3>Absence of Rate Limiting on API</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*NIfLSdzVmvcedPVakrWfZQ.png" /></figure><p>APIs are the part of your app that handle requests from users or other systems, things like “give me this data,” “log me in,” or “update this record.” Rate limiting is the rule that controls how many requests a client can send in a given time.</p><p>If there’s no rate limiting, it means there’s no rule controlling how many requests someone can send in a short amount of time. Anyone, a regular user, a bot, or a hacker could send thousands of requests per second. Your server would try to handle all of them, even if most of the traffic is nonsense or malicious.</p><p>💥 <strong>Why This Is a Problem</strong></p><ul><li><strong>Denial-of-Service (DoS)</strong>: Someone can crash your server by flooding it with too many requests.</li><li><strong>Brute-force attacks</strong>: Attackers can try thousands of password combinations on login endpoints to guess user passwords.</li><li><strong>Account enumeration</strong>: Hackers can repeatedly hit “forgot password” or similar endpoints to discover valid usernames or emails.</li><li><strong>Credential stuffing</strong>: Stolen username-password lists can be tried at high speed against your login API to gain unauthorized access.</li><li><strong>Data scraping</strong>: Automated scripts can pull large volumes of data quickly, potentially exposing sensitive information.</li></ul><p>🛠️ <strong>How to Fix It</strong></p><ul><li>Set request limits per client per timeframe (e.g., 100 requests per minute).</li><li>Apply stricter limits for sensitive endpoints like login.</li><li>Return HTTP 429 (“Too Many Requests”) for clients exceeding limits.</li><li>Implement rate limiting at the API gateway, web server, or app level.</li><li>Monitor and log repeated abuse patterns.</li></ul><h3>Header Injection → JWT Manipulation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*aTZ7t4wk_d-f_FJ3.png" /></figure><p>Many web apps sit behind proxies or load balancers, which often add headers like X-Forwarded-For, X-Forwarded-Proto, or X-Forwarded-Prefix. These headers tell the app what the original client request looked like. Header injection happens when an attacker manipulates these headers before they reach your app. If your app blindly trusts them, especially when creating JWTs (tokens) or making routing/permission decisions, attackers can trick your app into issuing or accepting tokens they shouldn’t.</p><p>💥 <strong>Why This Is a Problem</strong></p><ul><li>Forge or alter JWT claims (by influencing what goes into the token payload).</li><li>Trick the app into accepting a token it should reject.</li><li>Bypass authentication or escalate privileges.</li><li>Cause malicious redirects or session-hijacking by injecting attacker-controlled URLs into tokens.</li></ul><p>🛠️ <strong>How to Fix It</strong></p><ul><li>Only trust headers from known, trusted proxies.</li><li>Validate and sanitize all headers.</li><li>Avoid using headers to build JWT claims; rely on server-side data instead.</li><li>Always verify JWTs server-side, checking signature, expiry, and claims.</li><li>Log suspicious header activity and set alerts for repeated tampering.</li></ul><h3>Server Version Disclosure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*EYTaFcHawVb4T7aNZqQW8w.png" /></figure><p>Web servers and application platforms sometimes reveal their software and version numbers in headers or pages. For example:</p><pre>Server: Apache/2.4.37 (Ubuntu)<br>X-Powered-By: PHP/7.4.33</pre><p>This tells the world exactly what software you’re running. If those versions are old or unsupported, attackers can easily look up known vulnerabilities for that software and target them.</p><p><strong>💥 Why this is a problem</strong></p><ul><li>Attackers can identify precisely which CVEs (publicly known vulnerabilities) apply to your server and write targeted exploits.</li><li>Old or unsupported components often have known, unpatched vulnerabilities, giving attackers reliable ways to break in.</li><li>If multiple components are outdated (web server + OpenSSL + PHP), attackers can chain exploits (one bug leads to another) for remote code execution, privilege escalation, or denial of service.</li><li>Running EOL software can also break compliance and increase business risk.</li></ul><p><strong>🛠️ How to fix it</strong></p><ul><li>Ensure all server components (web server, runtime, libraries) are running versions that still receive security updates. Outdated software leaves known vulnerabilities open.</li><li>Don’t expose software or version info in responses or auto-generated pages. This makes it harder for attackers to target known exploits.</li><li>Disable unnecessary modules, features, or debug endpoints. Only expose what’s required for the application to run.</li><li>Regularly check for unsupported or EOL software and update components before they become a security risk.</li></ul><h3>JWT Misconfiguration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/391/1*g4RVLl2nfLQtsnZotUZgAw.png" /></figure><p>JWTs (JSON Web Tokens) are digital ID cards your app issues to users after login. They prove who a user is and what they’re allowed to do. Misconfigured JWTs are tokens that are insecure in some way: maybe they last too long, use weak signing algorithms, or are stored unsafely. Misconfigured tokens make it easier for attackers to impersonate users or access private data.</p><p><strong>💥 Why this is a problem</strong></p><ul><li>Long expiry tokens can be misused if stolen.</li><li>Using symmetric algorithms like HS256 means the same secret signs and verifies tokens. If the secret leaks, attackers can forge tokens. Using RS256 (asymmetric) separates signing (private key) and verification (public key), making forgery much harder.</li><li>Storing tokens in LocalStorage exposes them to any JavaScript on the page. XSS vulnerabilities can let attackers steal all tokens.</li><li>Blindly trusting tokens without checking signature, expiry, or claims allows attackers to manipulate tokens, escalate privileges, or impersonate users.</li></ul><p><strong>🛠️ How to fix it</strong></p><ul><li>Minimize how long a token is valid (minutes or hours). This limits the impact if stolen.</li><li>Prefer RS256 (asymmetric) over HS256 (symmetric) for stronger token verification.</li><li>Use HTTP-only, secure cookies instead of LocalStorage to prevent JavaScript from stealing tokens.</li><li>Always check token signature, expiry, and claims on the server before granting access.</li></ul><h3>Absence of Security Headers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*BaLTjJAvr04nB5s-.jpg" /></figure><p>Security headers are instructions your server gives the browser on how to handle your site’s content safely. They tell the browser which scripts and resources are allowed, whether framing is permitted, how HTTPS should be handled, and what information can be sent to other sites. Without them, browsers don’t know what’s safe, leaving users more exposed to attacks.</p><p>Common headers that protect your site:</p><ul><li><strong>Content-Security-Policy (CSP):</strong> Controls which scripts, styles, or content can run on the page.</li><li><strong>X-Frame-Options:</strong> Prevents your site from being embedded in another site (defends against clickjacking).</li><li><strong>X-Content-Type-Options:</strong> Stops browsers from guessing file types incorrectly (prevents MIME-type attacks).</li><li><strong>Strict-Transport-Security (HSTS):</strong> Forces secure HTTPS connections.</li><li><strong>Referrer-Policy:</strong> Controls what information is sent when navigating away from your site.</li></ul><p><strong>💥 Why this is a problem</strong></p><ul><li>Easier for attackers to inject malicious scripts (XSS).</li><li>Clickjacking attacks become possible.</li><li>MIME-type sniffing attacks can execute harmful code.</li><li>Users’ data and trust are at risk.</li></ul><p><strong>🛠️ How to fix it</strong></p><ul><li>Enable headers via your web server or security plugins.</li><li>Configure Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, HSTS, and Referrer-Policy.</li><li>Regularly review headers to ensure protection.</li></ul><h3>TRACE Method Enabled</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*5Yn2kM-aYNCWgSf1zdNpGQ.png" /></figure><p>TRACE is an HTTP method like GET or POST, but it simply echoes back exactly what the client sent to the server. It’s meant for debugging, so developers can see how requests travel through servers and proxies. Leaving it enabled in production can unintentionally expose sensitive information like cookies or authentication headers.</p><h4>💥 Why this is a problem</h4><ul><li>Cross-Site Tracing (XST) attacks — Attackers combine TRACE with other attacks, like XSS, to steal session cookies or auth tokens.</li><li>Sensitive data like cookies, authorization headers, and other private info can be exposed.</li><li>Session hijacking — With stolen headers, attackers can impersonate users and gain unauthorized access.</li></ul><h4>🛠️ How to fix it</h4><ul><li>Disable TRACE on your server.</li><li>Explicitly reject TRACE requests in server configs.</li><li>Ensure input sanitization and secure headers are in place.</li></ul><p>Even small security misconfigurations can cause bigger problems than you might expect. The good news is, most of these issues are easy to catch with a bit of attention, some simple best practices, and regular checks.</p><p>If you found any of these tips helpful, hit that 👏 and show some love! Thanks for reading 💛, here’s to safer, smoother code, See you on the next ride!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c1a830f3ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Cluster Architecture — A 10,000 Feet View]]></title>
            <link>https://medium.com/@ridmisameera.18/kubernetes-cluster-architecture-a-10-000-feet-view-f2a102d2c46a?source=rss-f80aa71e91e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2a102d2c46a</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Ridmi Thilakarathna]]></dc:creator>
            <pubDate>Tue, 29 Jul 2025 13:33:57 GMT</pubDate>
            <atom:updated>2025-07-29T13:33:57.419Z</atom:updated>
            <content:encoded><![CDATA[<h3>Kubernetes Cluster Architecture — A 10,000 Feet View</h3><p>Hey hey! 👋<br>If you missed my first blog “<a href="https://medium.com/@ridmisameera.18/what-is-kubernetes-a-beginner-friendly-introduction-5a42126924cc">What is Kubernetes</a>”, I recommend starting there, that’s where we began our shipping story to explain containers and Kubernetes.</p><p>If you’re back, welcome! 🫡 Go ahead, grab a coffee and settle in. Because I’m about to continue the story, right where we left off.</p><p>Last time, we saw how apps live inside containers, like cargo packed in boxes, and met Kubernetes, the calm helmsman keeping things smooth.</p><p>But Kubernetes isn’t working alone. Behind the scenes is a whole crew, control center, and multiple ships making decisions, solving problems, and moving your app-cargo across ports.</p><p>That whole team? It’s called a Kubernetes Cluster.</p><p>This article is your easy 10,000-foot view of what’s really going on beneath the surface.</p><h3>Two Types of Ships in Our Fleet</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W70Vf1-AxKA6lY3WAFAyrg.png" /><figcaption>Source : <a href="https://kubernetes.io/docs/concepts/architecture/">https://kubernetes.io/docs/concepts/architecture/</a></figcaption></figure><p>Don’t let the right-side picture scare you off! Trust me, by the end of this blog, you’ll be able to look at that diagram and go, <em>“Aha! I get it now.”</em> Stick with me, and we’ll piece it all together.</p><p>Imagine our shipping fleet has two kinds of ships:</p><ol><li><strong>Cargo Ships — the heavy lifters :</strong> These ships carry your containers (your apps) across the ocean from port to port. In Kubernetes, they’re called Worker Nodes, running your apps and doing the actual work.</li><li><strong>Control Ships — the strategic masterminds</strong> : Imagine if cargo ships sailed without a plan, no idea where to go, what to carry, total chaos! That’s why we have Control Ships, the ones calling the shots. Control Ships don’t carry containers but manage the whole fleet. They decide which cargo ship carries what, watch for delays, and adjust routes when needed. In Kubernetes, these are the Control Plane components, handling big decisions like where containers run, fixing problems, and tracking everything.</li></ol><p>So when you put it all together, the hard-working cargo ships (Worker Nodes) and the smart, strategic control ships (Control Plane), you get a fully functional Kubernetes Cluster.</p><h3>Meet the Control Plane Crew</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ao5mVUcn72IgkoJElnNaVw.png" /><figcaption>Control Plane Components (Source : <a href="https://kubernetes.io/docs/concepts/architecture/">https://kubernetes.io/docs/concepts/architecture/</a>)</figcaption></figure><p>Now that we’re aboard the control ship, let’s meet the teams keeping everything on track.</p><ul><li><strong>etcd — The Fleet’s Memory</strong></li></ul><p>In a busy fleet, containers are always being loaded, moved, updated, or replaced. To keep track of every detail, Kubernetes depends on <strong>etcd</strong>, its trusted logbook.</p><p><em>“Hey, which ships do we have? What’s running where? When did that pod restart? Any config updates waiting?”</em></p><p>etcd is a distributed key-value store, acting as Kubernetes’ reliable memory. It stores the entire state of the cluster. If etcd goes down, Kubernetes kind of… loses its mind. Back it up, protect it, and treat it with care.</p><ul><li><strong>Scheduler — The Crane Operator with a Plan</strong></li></ul><p>Alright, your containers are ready to go. But you can’t just throw them onto any ship like random luggage. Someone needs to plan it out.</p><p>Imagine cargo ships are lined up at a busy port, waiting to be loaded. Now there’s a massive crane, but it’s not just picking containers at random.</p><p>It looks at each ship: how full it is, How much space each ship has, where it’s headed, How heavy the container is, and any special rules. Only then does it go, <em>“Container #42, you’re heading to Ship-3. Perfect fit.”</em></p><p>In Kubernetes terms, the Scheduler checks each worker node: how much CPU and memory it has left, where it’s located, and any special labels or rules. Only then does it say, <em>“Pod-42? You’re going to Node-3.”</em></p><p>The Scheduler doesn’t actually run the container, it just picks the best spot.</p><ul><li><strong>Controllers — The Coordinating Departments on the Dock</strong></li></ul><p>Controllers are like the dedicated departments at the dock, making sure everything stays in order without waiting for someone to shout instructions.</p><p>They constantly watch what’s happening, compare it with the desired plan, and if something drifts off course, they step in.</p><p>Some of these controllers are:</p><ul><li>Node Controller:<br><em>“Ship-5 vanished! Let’s move its cargo somewhere safe before it sinks.”</em><br> It tracks all ships (nodes), and if one disappears, it quickly reschedules containers to healthy ships so nothing gets lost.</li><li>ReplicaSet Controller:<br><em>“We want 5 containers running, only 4 here? Spinning up another one now!”</em><br>This team makes sure your app always runs the desired number of copies, no fewer, no extras.</li><li>Deployment Controller:<br><em>“We’re upgrading App-X from version 1.2 to 1.3, one container at a time to avoid disruptions. Uh-oh, something broke? Rolling back, fast!”</em><br> It handles updates, rollbacks, and scaling with a steady hand, keeping your app running smoothly through every change.</li><li><strong>API Server — The Harbor Master</strong></li></ul><p>Every order, request, or update goes through the API Server, the port’s boss and central command:<br><em>“Want to deploy a new app? Check if a ship is healthy? Grab logs? Come through me, no shortcuts!”</em></p><p>It’s the only one who talks directly to etcd, makes sure everyone’s following the rules, and keeps the cluster secure and organized. It handles authentication, authorization, and validation, basically making sure only the right people do the right things. Without it, chaos.</p><ul><li><strong>Cloud Controller Manager — The Cloud Helper</strong></li></ul><p>Thinking about moving your fleet to the cloud? This helper is your go-to:<br><em>“I’ll talk to AWS, Google Cloud, or Azure, checking which ships are sailing, setting up the routes, and managing the gates so your fleet moves smoothly in the cloud.”</em></p><p>It bridges Kubernetes with cloud providers, making sure your containers keep sailing without a hitch. Running Kubernetes on your own hardware? You won’t need me.</p><h3>Meet the Worker Node Crew</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*kgg45Uwn1zvIhCSz1oqBWg.png" /><figcaption>Worker Node Components (Source : <a href="https://kubernetes.io/docs/concepts/architecture/">https://kubernetes.io/docs/concepts/architecture/</a>)</figcaption></figure><p>Alright, we’ve talked enough about the control ship. Now let’s zoom in on the cargo ships out at sea. These are the worker nodes in Kubernetes, the ones doing the real heavy lifting, carrying and running your containers.</p><ul><li><strong>Kubelet — The Captain on Each Ship</strong></li></ul><p>Every cargo ship needs a captain to keep things running smoothly. In Kubernetes, that’s the kubelet.</p><p>It runs on every worker node and listens carefully to orders from the control ship (the API Server). Its job? Make sure everything happens just right.</p><p>It tells the API Server when it’s ready, follows instructions to load or unload containers, watches their health closely, and regularly updates the control ship on how things are going.</p><p>The kubelet doesn’t make decisions, it just follows orders perfectly.</p><ul><li><strong>Meet the Network Officer — kube-proxy</strong></li></ul><p>Now, while the kubelet runs the ship, there’s another important role: making sure containers on different ships can talk to each other.</p><p>Imagine you have a web server container on one ship and a database container on another. How does the web server send its requests across the sea?<br>That’s kube-proxy’s job.</p><p>Running on every worker node, kube-proxy is like the network officer. It sets up all the network routes and rules so containers can find and chat with each other whether they’re on the same ship or spread out across the fleet.</p><p>It organizes the pathways and traffic signals so your web server’s messages don’t get lost on the way to the database.<br>And it works closely with Kubernetes Services, which give containers stable network addresses even when containers move, start, or stop.</p><ul><li><strong>Container Runtime — The Engine Room Below Deck</strong></li></ul><p>Every cargo ship needs powerful engines to move containers around. In our Kubernetes world, that engine is the Container Runtime.</p><p>While the captain (kubelet) gives the orders, it’s the runtime that actually starts, stops, and runs the containers. Think of it like the machinery deep in the ship’s engine room, the stuff that makes the cargo actually move.</p><p>Kubernetes doesn’t care which engine you use, as long as it does the job. You might be using containerd, CRI-O, or even Docker. These runtimes follow a standard (called the CRI — Container Runtime Interface), so Kubernetes can work with any of them without changing how it gives orders.</p><p>So whenever kubelet says,<em> “Fire up Container #7!”</em>, it’s the container runtime below deck turning the gears and spinning it into action.</p><h3>Wrapping Up the Voyage</h3><p>And there you have it, your 10,000-foot view of the Kubernetes fleet.</p><p>From the masterminds on the control ships to the hard-working crew on the cargo ships, every component in a Kubernetes Cluster plays a specific role to keep your containers sailing smoothly.</p><p>The API Server gives the orders. The Scheduler plans the loading. The Controllers keep things steady. And out at sea, the kubelet, kube-proxy, and container runtime bring those plans to life.</p><p>Whether you’re new to Kubernetes or just needed a clearer picture, I hope this story helped you connect the dots.</p><p>But this is just the surface. In future posts, we’ll dive deeper.</p><p>Until then, keep your fleet steady and your containers healthy.</p><p>And if you enjoyed the ride, hit that 👏 and show some love! See you in the next voyage!. Thanks for reading 💛.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2a102d2c46a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Computing, Minus the Jargon: A Beginner’s Guide]]></title>
            <link>https://medium.com/@ridmisameera.18/cloud-computing-minus-the-jargon-a-beginners-guide-071090372260?source=rss-f80aa71e91e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/071090372260</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Ridmi Thilakarathna]]></dc:creator>
            <pubDate>Wed, 07 May 2025 14:46:21 GMT</pubDate>
            <atom:updated>2025-05-07T14:46:21.896Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey there! 👋</p><p>Ever sat through a technical explanation and felt like your brain was about to melt? Yeah, me too.</p><p>I’m not a fan of memorizing complex definitions or decoding buzzwords. I like it when things just make sense💡. That’s exactly what we’re going to do today, no jargon, no textbooks , just an easy, breezy journey into cloud computing.</p><h3>The Storm Before the Cloud: The Old Days of Hosting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*wsa4D3y-vPDLSaUN.png" /></figure><p>Let’s go back in time⏳. Imagine you just launched your own small business. You’re pumped.💥 You’ve got a killer product, and now it’s time to build a website to sell it.</p><p>You think, “Alright, let’s get this thing online!”</p><p>But suddenly, you’re hit with questions like:</p><ul><li>❓Where do I host my website?</li><li>❓How many people will visit?</li><li>❓How much server space do I need?</li></ul><p>It’s like guessing how many seats you need for a party where you don’t know the guest list.</p><p>So, you take a shot in the dark and buy some servers. Maybe you overestimate and waste money. Or worse, you underestimate and the site crashes when people visit.</p><p>But that’s not even the worst part 😬.</p><p>Suddenly, you’re not just a business owner. You’re also:</p><ul><li>🔧 A technician fixing broken servers</li><li>🌐 A network expert making connections work</li><li>🛡️ A security guard fighting off cyber threats</li><li>💾 A backup wizard saving data “just in case”</li></ul><p>All before your first sale. It’s exhausting, expensive, and hard to scale.</p><h3>And Then Came the Cloud: Your Business’s New Best Friend</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/0*whBRzjKP9vVNEjdp.png" /></figure><p>Now, picture this:</p><p>Instead of buying servers and dealing with all that mess, you just rent what you need from a cloud provider, like Amazon Web Services (AWS), Google Cloud Platform (GCP), or Microsoft Azure etc.</p><p>They’ve already set up the servers, networking, and security in massive data centers 🏢🔒. You just say, “Hey, I need a bit of space and computing power,” and boom, it’s yours in seconds ⚡.</p><p>And here’s the best part: You only pay for what you use. Like electricity!<br>You don’t need your own power plant at home, right? You just flip a switch, use electricity, and pay for what you used. Cloud computing is exactly the same — but for tech stuff like storage, servers, and databases.</p><p>So, What Is Cloud Computing?</p><blockquote>Cloud computing is the on-demand delivery of IT resources over the<br>Internet (“Cloud”) with pay-as-you-go pricing. Instead of buying, owning, and maintaining physical data centers and servers, you can access technology services, such as computing power, storage, and databases, on an as-needed basis from a provider.</blockquote><h3>Why Cloud Computing is a Total Game-Changer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/0*CkP6-i910rF1Awiy.png" /></figure><ul><li>💸<strong> No More Huge Upfront Costs! Pay Only for What You Use</strong><br>Picture this: You’re launching a product. But before even making your first sale, you’d need to spend a fortune on servers, cables, and cooling systems.<br>With cloud computing, that stress disappears. You simply rent what you need and only pay for what you actually use. No upfront gambles, no wasted money.</li><li><strong>💰 Big Savings, Even for the Little Guys</strong><br>Ever wondered how a tiny startup gets access to the same tech muscle as a global corporation? Cloud providers like AWS or Azure serve millions of customers, letting them buy in bulk and pass on the savings. That means you get top-tier services at a fraction of the cost it would take to build them yourself.</li><li><strong>🎯 No More Guessing About Capacity</strong><br>In the past, you had to guess traffic and buy servers in advance, too much meant wasted money, too little meant crashes. With the cloud, you scale automatically, paying only for what you use. No more guessing.</li><li>⚡<strong> Move Faster, Experiment More</strong><br>No more waiting for hardware. With the cloud, you can set up resources in minutes, test ideas, and pivot quickly, no IT delays. Go from idea to action faster than ever.</li><li>🏢<strong> Say Goodbye to Data Centers</strong><br>Running your own data center is a huge responsibility, managing hardware, keeping the place cool, securing everything… it’s a lot. With cloud computing, the heavy lifting is handled by pros. You focus on your business. They focus on uptime, maintenance, and reliability. Win-win.</li><li><strong>🌍 Expand Globally in a Click (or Two)</strong><br>each users worldwide in just a few clicks. With the cloud, you can deploy your app globally and deliver fast experiences without building server rooms on every continent.</li><li><strong>🚀 Always Top-Notch Performance</strong><br>The big cloud players don’t mess around, they’re constantly upgrading their infrastructure. That means you get blazing-fast servers, minimal downtime, and the ability to handle massive workloads.</li><li>🔄<strong> Easy Data Backup &amp; Recovery</strong><br>Things go wrong, power outages, bugs, bad updates. But with the cloud, your data is backed up across multiple locations, so you can recover quickly and keep your business running.</li><li>🛡️<strong> Serious Security (That You Can Customize)</strong><br>Security is a big deal. And while no system is invincible, cloud providers offer enterprise-grade protection, encryption, firewalls, compliance standards, and 24/7 monitoring. You can also layer in your own security settings to match your needs. So yes, your data is in good hands, and you stay in control.</li></ul><h3>Exploring Cloud Deployment Models: Which One’s Right for You?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*J1ArmDjHZmBNz3-D.png" /></figure><p>When it comes to using the cloud, there’s no one-size-fits-all. Different businesses have different needs, some want full control, others want low maintenance, and many want a mix of both. That’s where the three main cloud deployment models come in: <em>Private Cloud, Public Cloud, and Hybrid Cloud</em>. Let’s break them down.</p><ul><li>🏠 <strong>Private Cloud: Your Own Personal Cloud Space</strong><br>A private cloud is like having a cloud built just for you, whether on-site or with a provider, the resources are yours alone. It’s great for businesses with strict security or compliance needs, giving you full control while keeping sensitive data safe and local.</li><li><strong>🌐Public Cloud: The Most Common Model</strong><br>Public clouds like AWS, Google Cloud, and Azure let you rent computing power, storage, or apps over the internet, while they handle the hardware and upkeep. It’s a flexible, cost-friendly choice, ideal for startups and growing businesses that want to scale easily without managing infrastructure.</li><li>🔁<strong>Hybrid Cloud: The Best of Both Worlds</strong><br>A hybrid cloud mixes private and public clouds, letting your data and apps move between them smoothly. It’s great when you need control for sensitive tasks and flexibility for things like analytics or traffic spikes, perfect for businesses that want both security and scalability.</li></ul><h3>Understanding Cloud Service Models: IaaS, PaaS, and SaaS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*JjNnZ1_QtTOlp_yA.png" /></figure><p>When you use cloud computing, you’re not just choosing where your services run (like public or private cloud), you’re also choosing how much control and responsibility you want. That’s where the three main service models come in:<em> IaaS, PaaS, and SaaS.</em></p><ul><li>🏗️ <strong>Infrastructure as a Service (IaaS)</strong><br>You rent basic computing resources like virtual machines, storage, and networking. You’re responsible for installing and managing your own operating systems, apps, and updates.<br><em>Example:</em> Hosting a website using AWS EC2 or Microsoft Azure where you configure everything but don’t worry about physical servers.</li><li>💻 <strong>Platform as a Service (PaaS)</strong><br>The cloud provider manages the infrastructure and platform (like OS and runtime), so you can focus on writing and deploying your code.<br><em>Example:</em> Using Google App Engine or Heroku to build and launch an app without setting up servers or managing updates.</li><li>🧑‍💼<strong> Software as a Service (SaaS)</strong><br>Fully managed software delivered over the internet. No installation or maintenance is needed on your part, just log in and use it.<br><em>Example:</em> Tools like Google Docs, Salesforce, or Netflix where the provider handles everything behind the scenes.</li></ul><p>✨ That’s a wrap! My goal here was to make cloud computing feel way less intimidating. If you enjoyed this or just liked the vibe, go ahead and smash that <strong>clap</strong> button. 👏</p><p>Thanks a ton for hanging out and reading — you’re awesome! 💛</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=071090372260" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Little Things That Make Interviews and Work Feel Amazing]]></title>
            <link>https://medium.com/@ridmisameera.18/the-little-things-that-make-interviews-and-work-feel-amazing-47398af4a9b7?source=rss-f80aa71e91e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/47398af4a9b7</guid>
            <category><![CDATA[software-industry]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[supportive-environment]]></category>
            <dc:creator><![CDATA[Ridmi Thilakarathna]]></dc:creator>
            <pubDate>Sun, 04 May 2025 08:12:47 GMT</pubDate>
            <atom:updated>2025-05-04T08:12:47.648Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*buXvhLbODa83BZiGpt9E0A.png" /></figure><p>I saw this line recently on social media, and it stuck with me. Today, I want to share something a little different from my usual topics , something that’s been on my mind because of that post. It reminded me of some small but powerful moments I’ve experienced during interviews and at work, and I felt inspired to write this piece.</p><h3>🌟When Interviews Become Learning Moments</h3><p>I’ve been working in the software industry for about a year and a half now. I’m still relatively new, and though I haven’t yet been on the interviewer side, I’ve gone through plenty of job interviews after graduation. Those experiences left a deep impression on me.</p><p>What amazes me most are the interviewers who turn an interview into a journey of discovery.</p><p>I’ve had a few interviews where, even if I didn’t know the answer right away, the interviewer would help guide me step by step, starting from what I do know, and helping me connect the dots. It’s such an amazing feeling when you realize halfway through, “Hey, I can figure this out”.</p><p>What stood out most was how they made me feel, not like I was failing, but like I just needed a little nudge to find my way. I feel it’s such a beautiful quality when someone can unlock that hidden potential in a person.🌱 It’s not just about getting the “right” answer; it’s about creating a moment where you feel proud of your own thinking.</p><h3>🌧️And Then There Are the Others…</h3><p>Not every interview leaves you feeling inspired, and that’s okay, too.</p><p>I remember one of my early interviews before I got my first job. There was a project on my CV, a university module project. You probably know how these usually go: lecturers give them to help students understand concepts, not necessarily to build a polished, production-level product.<br>As I remember, this one was about Elasticsearch. When the interviewer asked me about it, I explained what I had done. He then asked, “What can you even do with these kinds of projects in the real industry?”</p><p>The way he used words and kept the conversation going made me feel like you’re nothing and kept pulling me down, making me feel dumb. And honestly, that project wasn’t just a simple exercise; it had made it into the top six in our class, and our lecturer had even suggested presenting it in a top-six showcase. It wasn’t something to be dismissed as insignificant.</p><p>And the thought that came to my mind in that moment was: even if I had been selected (which I wasn’t), I’m not going for it, because this feels like the kind of mindset you see at the managerial level in that company.</p><p>I’m not saying this to insult anyone or to make it sound wrong, I’m just sharing the situation as it unfolded.</p><h3>🌻 Finding Supportive Mentorship at Work</h3><p>Fast forward to when I landed my first job as a fresh graduate, within weeks, I was thrown into a project. I was lucky to have seniors who didn’t just expect me to know everything from day one. They understood that people learn and grow at their own pace.</p><p>In Sri Lanka, I’ve noticed a difference across universities: some universities focus heavily on industry preparation, shaping students to jump right into work. Others balance things like research, higher studies, and industry, which means it can take a little longer to adapt on the job, but those, they often have great potential to pick things up quickly once they get going. I feel like both approaches are valuable, just in different ways.</p><p>Personally, I’m someone who struggles a bit at the beginning but picks up speed once I get the hang of things. What really made a difference for me was having seniors who recognized that and supported me without making me feel small.🌻 I feel it’s such a wonderful quality when someone guides you without ever making you feel like you’re less. I have so much respect for those kinds of seniors, they create space for growth, and that’s something I carry with a lot of gratitude.</p><p>And I believe that kind of gratitude doesn’t just stay inside, it shapes who we become. Someone who feels that gratitude will naturally carry it forward, and a few years down the road, they’ll likely be the kind of senior who supports others in the same way.💫 It helps build a supportive, uplifting network without toxic ego, where everyone has space to rise and thrive. Because that’s how we keep the chain of kindness going, and that’s how we all grow stronger together.</p><h3>🌈A Few Final Thoughts</h3><p>Here’s the heart of what I want to say: Interviews and mentorship aren’t just about evaluating technical skill. They’re about unlocking potential.</p><p>A great interviewer or senior doesn’t just check off a list of requirements. They help someone grow into their capabilities. They inspire, they guide, and they leave you better than they found you, even if the outcome isn’t what they hoped for.</p><p>Interviews and mentorship can have a huge impact on how someone sees themselves and their future. It’s not just about finding the right fit for the company, it’s about helping someone see the potential they may not even know they have.</p><p>For me, it’s not about having the perfect answers or impressing anyone. What really stands out is being in environments where curiosity, learning, and encouragement thrive. 🌟That’s when people surprise themselves with what they’re truly capable of.</p><p>✨ Thanks for reading! It really means a lot. ✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47398af4a9b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is Kubernetes? A Beginner-Friendly Introduction]]></title>
            <link>https://medium.com/@ridmisameera.18/what-is-kubernetes-a-beginner-friendly-introduction-5a42126924cc?source=rss-f80aa71e91e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a42126924cc</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Ridmi Thilakarathna]]></dc:creator>
            <pubDate>Mon, 14 Apr 2025 13:17:16 GMT</pubDate>
            <atom:updated>2025-04-14T13:17:16.181Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*3Rf2ro-A10MtFuj1akogCw.png" /></figure><p>When I first heard of Kubernetes, I thought: “Wow, sounds complicated. Probably not my thing.”</p><p>It felt like I had walked into a room where everyone was speaking in code — “containers,” “orchestration,” “clusters,” “pods” — and I was just standing there thinking, what the heck is all this?🤯</p><p>I’d watch a few videos, read some docs, feel kinda smart, and then… forget everything the next week.😅<br>So here’s the version of Kubernetes I wish someone had given me — no jargon, no lectures, just plain words and real-life comparisons.🙌</p><h3>🧱Containers First — Why They Matter</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*w0mKNTrNd-2PtQ6njEPzyg.png" /></figure><p>Now, let’s be real — most of us didn’t grow up thinking about <em>software containers</em>. But what we do know are real-world containers, like the ones we see on cargo ships.</p><p>Imagine the shipping industry before standard containers. Let’s say:</p><ul><li>One company wants to ship potatoes🥔.</li><li>Another wants to ship cars🚗.</li><li>And another wants to ship oil🛢️.</li></ul><p>These are totally different items. Potatoes are bulky, cars are huge and need special care, and oil is messy and requires leak-proof barrels. Each of these items requires different types of packaging, handling equipment, and storage conditions.</p><p>You can’t just stack cars on top of each other or treat barrels of oil like sacks of potatoes. Everything needs custom care — total chaos.😵</p><p>Then came <strong>shipping containers</strong>. Now, everything — no matter what it is inside — goes into the same kind of box. Easy to stack, move, ship, and track.📦<br>Suddenly the world could move things faster and smarter.🌍</p><p>Now bring that idea to software.💻</p><p>You’ve got a Node app, a Python app, a Go service — each needs its own setup, libraries, and configs. Deploying all that? Same chaos as the 1970s port.</p><p>So here’s the deal:<br> “You get a virtual, isolated box. You pack everything your app needs inside it — the code, the runtime, the libraries, the dependencies — all of it. We don’t care if it’s Java, Python, Node, or even C++. Just pack it, seal it, and hand it over. Done. ✅”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*IyXA5rhoqa103_6zzKuJtw.png" /></figure><p>Put each app into its own software container, and boom — now they all behave the same way, anywhere — on your laptop, in staging, or in the cloud. And it’ll work exactly the same way every time. Why? Because it brings its own environment with it.<br>No more dependency drama. No more “but it works on my machine” headaches. Just clean, consistent, portable apps.✨</p><h3>⚓Kubernetes — Your Ship’s Calm, Capable Helmsman</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*R0IBtbE8RoXaZgv8kvR61w.png" /></figure><p>Cool, so you’ve got containers. Lots of them. Now what?</p><p>You need someone to:</p><ul><li>Run them🏃</li><li>Restart them when they crash♻️</li><li>Make more copies when users show up📈</li><li>Spread them across machines🧩</li><li>Roll out updates without downtime🔄</li></ul><p>That’s a lot of work. And you doing it all manually? Nightmare.😬</p><p>This is where Kubernetes comes in — your chill, smart helmsman.🧭</p><p>Imagine telling it:</p><ul><li>“I want 3 copies of this app running at all times.”</li><li>“If one crashes, replace it.”</li><li>“Oh, we got a traffic spike? Make it 10.”</li><li>“Deploy version 2 — but carefully, and roll back if users panic.”</li></ul><p>And Kubernetes says: “Aye aye, captain. I got this.”🫡</p><h3>📘A Few Words That Sound Scarier Than They Are</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*gN3Ps9CkNhqvc4Eu2yO6TQ.png" /></figure><p>Let’s break down a few Kubernetes terms:</p><p>📝<strong><em>Important Note</em></strong><em>: Until now, we’ve been saying “Kubernetes manages containers.” But actually, Kubernetes manages </em><strong><em>pods</em></strong><em> — which usually </em>contain<em> one or more containers.</em></p><p><em>Why more than one? Because Sometimes, a single container isn’t enough — for example, your app might need a helper to collect logs or refresh cache. In such cases, multiple containers are grouped into one pod to work together efficiently.</em></p><ul><li><strong>Pod</strong>: The smallest unit in Kubernetes. It wraps one or more containers. Think of it as a <em>running box</em> for your app.</li><li><strong>Node</strong>: A physical or virtual machine that runs pods. Kubernetes decides where to place them.</li><li><strong>Cluster</strong>: A group of nodes plus the control system — this is your Kubernetes environment.</li><li><strong>Service</strong>: A steady entry point to your pods. Even if a pod dies, users reach your app through the same address.</li><li><strong>Deployment</strong>: A blueprint that says: “Run 3 of these pods, always updated to version X.” Like your rollout plan.</li></ul><h3>✨The Magic Stuff Kubernetes Does</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*dXuQOO3sVuMX7_SgjD7pGA.png" /></figure><p>Here’s where it gets cool. Kubernetes doesn’t just run things — it runs them smart.</p><p>🔧<strong>Self-Healing</strong><br> One of your app components (called a pod) dies?<br> Kubernetes notices and just… replaces it. Like:</p><p>“Oh, you crashed? No problem, I’ll bring you back.”</p><p>No alerts. No panic. Just auto-repair mode.</p><p>📈<strong>Auto Scaling</strong><br> Traffic goes from 10 users to 1,000 in 10 minutes?<br> Kubernetes can scale your app up automatically — like hiring more chefs during a dinner rush.<br>And when it’s quiet again? It scales back down.</p><p>🧮<strong>Load Balancing</strong><br>Got 5 pods running your app? Kubernetes spreads the traffic out so no one pod gets roasted.<br>Imagine you’ve got 5 bartenders — Kubernetes is the host assigning each customer to the next available one.</p><p>🔁<strong>Rolling Updates (Without Downtime)</strong><br> Wanna ship a new version of your app? Kubernetes does it gradually.</p><ul><li>Replaces old pods one at a time</li><li>Makes sure the new one is healthy before continuing</li><li>And if something goes wrong? 🚨 It rolls back!<br> All while users are still using your app.</li></ul><p>Basically, it does the stuff you’d do if you were babysitting your servers 24/7 — but it does it for you.</p><h3>🧠You Don’t Need to Memorize Everything</h3><p>Just know what it can do.<br>Start small. Break stuff. Fix it.<br>Soon you’ll go from <em>“What the heck is this thing?”</em> to <em>“Ohhh, that’s kinda cool.”</em>😎</p><p>You got this. 💪</p><p>🎤And finally… Here, I gave you a storyline — something I want you to understand effortlessly. If it made sense, and if you felt even a tiny spark of <em>“hey, I am getting this now”</em> — go ahead and hit a <strong>clap</strong>. 👏</p><p>Also… this is my very first blog post (yay! 🎉). Thanks for reading 💛</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a42126924cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>