<?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 Ademola on Medium]]></title>
        <description><![CDATA[Stories by Ademola on Medium]]></description>
        <link>https://medium.com/@abadmus012?source=rss-35b43b5cb3a7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YVgLocUX3V8wzfOnN38qIA@2x.jpeg</url>
            <title>Stories by Ademola on Medium</title>
            <link>https://medium.com/@abadmus012?source=rss-35b43b5cb3a7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:48:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abadmus012/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[Six Months in America: I Thought Getting Here Was the Hard Part]]></title>
            <link>https://medium.com/@abadmus012/six-months-in-america-i-thought-getting-here-was-the-hard-part-86386de0e5c6?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/86386de0e5c6</guid>
            <category><![CDATA[grad-school]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[america]]></category>
            <category><![CDATA[immigration]]></category>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 04:06:33 GMT</pubDate>
            <atom:updated>2026-06-30T04:06:33.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KfuC_TZ8bQhZ4HKN" /><figcaption>Six months ago. Soul buffering.</figcaption></figure><p>Six months ago, I landed in America with one suitcase, one backpack and the blank, hollow expression of a man whose soul had temporarily left his body to process what was happening.</p><p>I had made it.</p><p>After the prayers. After the emails nobody owed me a reply to. After being told “we’re not hiring” twice, by the same people who eventually hired me. After the visa uncertainty, the presidential proclamation that nearly ended everything before it began, the administrative processing that aged me spiritually and the connecting flight to a city called Wichita, Kansas that I had to Google to confirm was, in fact, a real place in the United States.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Pdn9iyM_BxbNRhkW" /><figcaption>Had to confirm this place existed.</figcaption></figure><p>It is. I’ve checked multiple times.</p><p>Standing in Dallas Fort Worth airport, immigration stamp fresh in my passport, I felt something settle in my chest. A long exhale. The end of something hard and the beginning of something unknown.</p><p>I thought the hardest part was behind me.</p><p>I was adorably, completely, spectacularly wrong.</p><p><strong>America Is Less About Arrival and More About Adjustment</strong></p><p>People celebrate your arrival like it’s the finale.</p><p>They say things like “Wow, you’re in America now!” with the energy of someone who has just watched you win a championship. Fireworks energy.</p><p>What they forget to mention is that the championship was just the qualifier. The actual tournament starts Monday.</p><p>Moving countries doesn’t solve your problems. It relocates and changes the context of them. You’re still you, the same habits, the same fears, the same brain that won’t stop catastrophizing at 2am. Your overthinking, your insecurities, your tendency to Google things that should absolutely not be Googled before bed, all of it clears immigration without so much as a secondary screening.</p><p>The audacity.</p><p>The systems here also have a particular way of welcoming you that I can only describe as warmly threatening. Every portal, every office, every form says: <em>you’re welcome here. Now prove it. By Friday.</em></p><p>I learned quickly that arrival is not a moment. It’s a posture you have to maintain, every single day, until it stops feeling like effort.</p><p><strong>I Finished My First Semester With a 4.0</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*wvuUOEDJsLOF2893" /><figcaption>Me checking final grades like I wasn’t stressed all semester.</figcaption></figure><p>I need to say this slowly so it lands correctly.</p><p>A. Four. Point. Zero.</p><p>I’m not sharing this to brag. I’m sharing it because of what it disproved internally.</p><p>Because six months ago, beneath all the preparation and prayer and confidence I’d carefully assembled, a quieter voice was asking a quieter question: <em>what if you’ve overestimated yourself? What if everyone here is sharper, faster, more prepared? What if you get here and discover you were never supposed to be in this room?</em></p><p>I felt all of that. Loudly. In the first week.</p><p>Then something unremarkable happened. I submitted an assignment. The feedback was good. I submitted another. Also good. And somewhere in that ordinary, unglamorous rhythm of just showing up and doing the work, the fear quietly packed its bags and left. Not dramatically. It just stopped being as loud.</p><p>The 4.0 didn’t answer every insecurity I carried here. But it silenced one important lie, the one that said I didn’t belong.</p><p>I’ll take it.</p><p><strong>I Got My Driver’s License. Please Acknowledge This Achievement.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5BGrdPXUjrAO2B5W" /><figcaption>Lagos vs Wichita driving culture.</figcaption></figure><p>This deserves its own section. Possibly its own essay. Maybe a small ceremony.</p><p>Because I want you to understand something about what it means to learn to drive as someone who grew up in Lagos, a city where traffic is less a system and more a philosophy, where lane markings are suggestions and where the ability to merge without indicating is considered a personality trait.</p><p>American roads are a completely different conversation.</p><p>The rules are followed. Consistently. By almost everyone. Indicators are used. Stop signs are respected. People wait their turn at a four way intersection like civilized participants in a shared social contract. It is deeply, profoundly disorienting.</p><p>But I adapted. I studied. I passed.</p><p>And when I got that little card, I felt something I didn’t expect: freedom. Real, tangible freedom. Because in Wichita specifically, not having a car isn’t inconvenient. It is a logistical emergency. Public transport exists here the way good WiFi exists in some hotels. Technically present. Practically unreliable.</p><p>I also now understand why Americans casually say “it’s just 20 minutes away.” In Lagos, 20 minutes is not a distance. It is an aspiration. A thing you say when you don’t want to tell the truth about traffic. In Wichita, 20 minutes means you’ve crossed the entire city, gotten coffee and made a new friend.</p><p>I am adjusting.</p><p><strong>The Work Has Been Stretching Me</strong></p><p>I came here thinking mostly like an engineer.</p><p>Pipelines. Architectures. Clean systems built over messy problems. Data that goes in one end and comes out the other end useful and organized. I like things organized.</p><p>The work I’ve been doing this season has complicated that preference in the best way.</p><p>I’ve been building a tool that converts scanned paper surveys into structured datasets for research purposes. An engineering problem on the surface: optical character recognition, confidence scoring, human review for uncertain extractions, configurable pipelines. The kind of problem I know how to hold.</p><p>But somewhere in the middle of building it, I kept running into the humans on the other side of the data. The surveys weren’t just documents. They were evidence of what communities needed. What they lacked. What they were quietly asking for without always having the language to ask clearly.</p><p>Behind every dataset is a story. Behind every metric is a person living inside that statistic.</p><p>I knew that intellectually before I arrived here. I feel it now. That’s a different kind of knowing, the kind that changes not just how you work, but what you’re working for. I did not expect this season to teach me that. But here we are.</p><p><strong>On the Subject of People Leaving</strong></p><p>Let me tell you what nobody warned me about.</p><p>You spend six months building a life in a new place. You find your rhythm. You find your people: colleagues who make the work feel less like work, a supervisor whose questions make you think differently, people whose presence in your week you stop noticing until it’s no longer there.</p><p>And then, without warning or adequate notice, everyone leaves.</p><p>I am not being dramatic. I am being precise.</p><p>One colleague, brilliant, kind, someone whose perspective I genuinely valued, is heading to New York for her PhD. Another is starting a new role right here in Wichita, which sounds less dramatic until you realize that even a short physical distance can completely change the texture of a working relationship. And my course coordinator, someone who pushed my thinking in ways I’m still processing months later, is moving to another institution entirely.</p><p>Three people. Six months. Gone.</p><p>I would like to file a formal complaint with the universe but I’ve been told the processing time is indefinite and outcomes are not guaranteed.</p><p>Nobody prepares you for this. The fact that building community in a new country also means watching that community rearrange itself constantly. That the people who anchor you in a season are sometimes only meant for that season, their purpose in your story complete, even if the chapter feels too short.</p><p>I’m happy for all of them. Genuinely, fully happy.</p><p>I’m also allowed to find the timing slightly inconsiderate.</p><p>So to them: congratulations on your next chapters. You are all doing wonderful, inconvenient things. I will be here in Wichita, quietly rebuilding my support network from scratch, as one does. Please check in.</p><p><strong>People in Wichita Are Surprisingly Nice</strong></p><p>I say “surprisingly” not because I expected hostility but because I genuinely didn’t know what to expect arriving in the middle of the American heartland as a Nigerian man in January, wearing a coat I had purchased specifically for this occasion and immediately discovered was insufficient for this occasion.</p><p>Wichita is warm. Not performatively nice. Actually warm. Helpful in the small, specific ways that matter when you’re new somewhere and nobody owes you anything.</p><p>Which forced me to reckon with something uncomfortable about myself.</p><p>I can be reserved. I can stay inside my comfort zone for longer than is reasonable or productive. I have, over these six months, blamed environment, busyness and the general weight of being a first year international student for my social quietness, all legitimate reasons that collectively obscured a simpler truth:</p><p>Sometimes the limitation is just me.</p><p>So recently I’ve been doing something uncomfortable. Initiating more. Showing up more. Having conversations that don’t have a productive agenda. Remembering that friendship in adulthood doesn’t happen to you passively. You have to participate in it, even when participation feels awkward, even when you would genuinely rather be home reading about data architecture.</p><p>It’s working. Slowly. Imperfectly. But it’s working.</p><p>I still want more people around me. But I’ve also learned not to dismiss quiet progress.</p><p><strong>Ah Yes. Romance.</strong></p><p>I was hoping this section would volunteer to remove itself.</p><p>It did not.</p><p>So let’s just say America has offered what I will diplomatically call character development in this particular area of life. There have been conversations. Unexpected chemistry. Mild confusion. A few lessons learned at reasonable personal expense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*wS9jVSll9418ADGZ" /><figcaption>No further comments at this time.</figcaption></figure><p>No further details will be provided at this time.</p><p>Moving on. Swiftly. Permanently.</p><p><strong>I Am Not the Same Person Who Landed Here</strong></p><p>Something else has shifted that I didn’t expect and almost didn’t notice until recently.</p><p>Six months ago, I was obsessed with outcomes. The job. The sponsorship. The salary. The five year plan, the ten year plan, the plan for the plan. I wanted certainty the way some people want water, urgently, constantly, as if without it something essential would dry up.</p><p>America has been slowly, patiently teaching me something different.</p><p>I still care deeply about where I’m going. That hasn’t changed. But I’ve become far more interested in how I’m getting there. In the quality of the work in front of me today. In whether I’m showing up faithfully to what I can control, rather than spending my energy on what I can’t.</p><p>That is not small. For me, that is enormous.</p><p>Because old Ademola wanted guarantees before he could move.</p><p>Current Ademola is learning to move without them.</p><p><strong>The Real Battle Has Been Internal</strong></p><p>If I’m being fully honest and these essays have committed me to honesty at personal expense, the biggest battles of these six months have not been academic. Not even logistical.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*07cBSBacDW4FQpsM" /><figcaption>Me reading immigration news at 1:47 AM.</figcaption></figure><p>They have been internal.</p><p>Nobody really prepares you for how much mental space the future occupies when you’re building something that isn’t guaranteed. There’s a particular kind of anxiety that lives underneath ambition when the stakes feel high, when you’ve sacrificed enough that failure doesn’t feel like something you can casually accept.</p><p>I’ve spent evenings reading things I probably shouldn’t read before bed. Watching policy conversations unfold in real time. Wondering how decisions made in rooms I’ll never sit in might quietly reshape the path I’m walking. Asking myself versions of the same question on rotation: <em>am I doing enough? Is the door still open? What if I do everything right and the rules change anyway?</em></p><p>My mind, I’ve learned, is very good at this. At constructing elaborate worst case scenarios with the thoroughness of someone who should really be channeling that energy elsewhere.</p><p>What I’ve been slowly learning is that I cannot carry five years of the future in my chest at once. I can prepare. I can work. I can show up. But I cannot control what I cannot control and the sooner I stop trying to, the more present I actually become in the life I’m living right now.</p><p>That lesson is ongoing. I don’t think it ever fully ends.</p><p><strong>Faith Looks Different Now</strong></p><p>Six months ago, my prayers sounded like: <em>God, please let this work.</em></p><p>Now they sound more like: <em>God, help me stay grounded while I do the work in front of me. And if You’re arranging things I can’t see, keep arranging. I’ll try to stop interfering.</em></p><p>Less transactional. More relational.</p><p>I still have questions I can’t answer. Fears I haven’t outgrown. Moments where uncertainty is louder than faith and I have to choose, consciously, which one I’m going to let drive.</p><p>But I’ve also seen enough quiet evidence to keep going. The doors that opened after they’d already closed. The provision that arrived before I knew to ask for it. The small, daily mercies that don’t make good testimony posts but accumulate, over time, into something real and undeniable.</p><p>God has been faithful in quiet ways. Not always through dramatic moments. Sometimes through endurance. Through timing. Through the specific grace of being held together on the days when holding yourself together wasn’t quite working.</p><p>That’s what I’ve been given.</p><p>And it has been enough.</p><p><strong>Six Months In</strong></p><p>So where am I?</p><p>Not fully settled. Not fully certain. Not where I imagined being at this point and slowly, imperfectly, making peace with that gap.</p><p>But I’m not the same person who landed here either.</p><p>I’m stronger in ways I didn’t choose to become. More self aware about my fear and what it actually costs me. More honest about what I want and what scares me about wanting it. More disciplined in the building, in showing up every day to something that matters, even when the progress is invisible and nobody is watching.</p><p>Six months ago, I thought getting here was the hard part.</p><p>Turns out getting here was just the address.</p><p>The life still had to be built.</p><p>Room by room. Day by day. Prayer by prayer. With better directions than I had at the start, more patience than I knew I possessed and the slow, growing understanding that becoming is the whole point.</p><p>Not the destination you’re becoming toward.</p><p>But the becoming itself.</p><p>I’m still in it.</p><p>And for the first time in a long time, I’m okay with that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86386de0e5c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Month in America: Nothing Prepared Me for This]]></title>
            <link>https://medium.com/@abadmus012/one-month-in-america-nothing-prepared-me-for-this-3c73575e1f1d?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c73575e1f1d</guid>
            <category><![CDATA[graduate-school]]></category>
            <category><![CDATA[masters-degree]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[immigration]]></category>
            <category><![CDATA[united-states]]></category>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Sun, 08 Feb 2026 06:18:22 GMT</pubDate>
            <atom:updated>2026-02-08T06:28:00.455Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TCf5cQN7wH2NvFe8.jpg" /></figure><p>I’ve been in the United States for over a month.</p><p>That sentence still feels strange to write. Not because of skyscrapers or highways, Google Maps and YouTube already showed me those but because the experience has been quieter, heavier and more personal than I expected.</p><p>Before I came, I prayed for clarity.<br>After I arrived, I learned that clarity often shows up disguised as patience.</p><h3>Arrival Isn’t a Moment. It’s a Process.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*q7mWqJh4GUxxBYuO" /></figure><p>I thought arrival would be a moment.</p><p>Touchdown. Deep breath. “Welcome to your new life.”</p><p>Instead, arrival is paperwork.</p><p><strong>Forms</strong>. <strong>Portals</strong>. <strong>Waiting rooms</strong>. Emails that begin with <strong><em>“Dear Ademola”</em></strong> and end with a deadline that feels slightly threatening.</p><p>Every system politely says:<br><em>You’re welcome here.</em><br>Now prove it.</p><p>Some days felt overwhelming, not in a dramatic way, just in the slow accumulation of small things. On those days, my prayers changed. Less asking God to move things faster. More asking Him to steady me while things unfolded.</p><p>That was my first real lesson here: faith isn’t always about movement. Sometimes it’s about posture.</p><h3>School Began Without Drama</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UMzJ6elRE1Iow_11.JPG" /></figure><p>Classes started quietly.</p><p>No cinematic moment. No soundtrack playing in my head. Just walking into a classroom and realizing something unexpected:</p><p>I wasn’t out of place.</p><p><strong>Intro to Business Analytics</strong>.<strong> Python for Business</strong>. <strong>ERP</strong>.</p><p>The material didn’t feel foreign. It felt familiar, like God gently reminding me that nothing about this journey was accidental. That the experiences I carried with me weren’t baggage. They were preparation.</p><p>That realization brought more peace than any motivational quote ever could.</p><h3>Faith in the Small, Unsexy Things</h3><p>This period has tested my faith in ways no testimony video prepares you for.</p><p>Health screenings. TB tests. Waiting on results.<br>SSN delays.<br>HR approvals.<br>Insurance portals that insisted I didn’t exist yet.</p><p>There were moments I felt suspended between systems, not fully active anywhere. Too international for one office, not official enough for another.</p><p>But every time anxiety crept in, something small would happen. A result would come back clean. An email would arrive. A door would open just enough.</p><p>Nothing dramatic. No thunder. Just enough reassurance to keep going.</p><p>I started to see God less as someone rushing me forward and more as someone teaching me how to wait without falling apart.</p><h3>Loneliness and Quiet Grace</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*O4pnRUbgz4AXaMXI" /></figure><p>No one really tells you this, but I will tell you.</p><p>Loneliness in a new country doesn’t scream.<br>It whispers.</p><p>It shows up when the tasks are done and the noise settles. When you realize your support system is now mostly prayer, memory and trust.</p><p>On those nights, faith became less about words and more about confidence, confidence that obedience doesn’t always feel loud and being alone doesn’t mean being abandoned.</p><p>Grace, I learned, is often quiet.</p><h3>Gratitude Changes the Math</h3><p>Here’s what one month brought:</p><p>My SSN came through.<br>My GA start date is confirmed.<br>My medical results came back clean.<br>Gotten my learner’s permit and next is to get my driver’s license.<br>My classes are fully underway.</p><p>None of these are headline-worthy.<br>All of them are answered prayers, some I prayed intentionally, some I didn’t even know how to ask for.</p><p>Perspective changes when you slow down enough to count progress.</p><h3>One Month In</h3><p>I’m not fully settled.<br>I’m not fully comfortable.<br>I don’t have everything figured out.</p><p>But I’m covered.</p><p>Covered by grace.<br>Covered by preparation.<br>Covered by a God who didn’t bring me this far to leave me uncertain.</p><p>One month in, this is what I know:</p><p><strong><em>Faith doesn’t always move mountains.<br>Sometimes it teaches you how to climb patiently.</em></strong></p><p>And for now, that’s enough.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c73575e1f1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Was Told “We’re Not Hiring.”]]></title>
            <link>https://medium.com/@abadmus012/i-was-told-were-not-hiring-17860130a994?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/17860130a994</guid>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Mon, 05 Jan 2026 01:50:17 GMT</pubDate>
            <atom:updated>2026-01-05T02:00:51.491Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Six Months Later, I Was Sitting in America Realizing God Had Been Quietly Working the Whole Time.</blockquote><p>Six days ago, I landed in the United States.</p><p>Not with fireworks. Not with loud celebration. Just quiet disbelief.</p><p>I cleared immigration, sat down near my check-in gate and stared at my backpack for a long time like it might suddenly explain how I got here. Somewhere between exhaustion and gratitude, it hit me: this was real. I wasn’t imagining it. I hadn’t woken up yet.</p><p>What followed wasn’t excitement. It was silence. The kind that comes when something long prayed for finally happens and your soul needs a moment to catch up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/0*Ti94l35I_TtD66La.jpg" /><figcaption>Dallas Forth Worth AirPort, Dallas, Texas.</figcaption></figure><h3>Where This Story Actually Begins</h3><p>Early 2025. Lagos.</p><p>I was working full-time as a Data Engineer at one of Africa’s leading Tech companies, doing well enough by most standards. I had stability, a routine and just enough comfort to notice something missing.</p><p>I felt capped.</p><p>Not unhappy. Just unfinished.</p><p>Then my uncle called and suggested I apply for graduate school. After some thought (and prayer), I decided on Business Analytics in the United States for the Spring session.</p><p>On paper, this was a terrible idea.</p><p>Business Analytics programs rarely fund international students. Spring admissions are famously unfriendly to assistantships. And the Lagos U.S. embassy has humbled people with far stronger confidence than mine.</p><p>Still, I prayed.</p><p>Not dramatic prayers. Just honest ones.</p><p>“God, please let my plans align with Your will for my life.”<br>“Lord, give me clarity on this path. And if it pleases You, let it work.”</p><p>Then I did something small that would quietly change everything.</p><p>I sent emails.<br>A lot of emails.</p><p>I reached out to multiple departments. I even called my course coordinator directly, using my MTN line from Lagos, like a man who had decided to leave nothing untried.</p><h3>The Email That Led Nowhere (At First)</h3><p>One of the departments I contacted was a research center connected to the program. I introduced myself. Explained my background. Expressed interest.</p><p>They replied kindly.</p><p>They were not hiring.</p><p>The email was polite, professional and non-committal, the academic equivalent of “we’ll see.” I took it as a maybe. In hindsight, it was very much a <strong>no</strong>.</p><p>Most people would stop there.</p><p>But I didn’t.</p><p>Not because I was confident. But because something in me felt unsettled, like there was still something to do.</p><h3>The Season of Building Without Applause</h3><p>Instead of waiting, I started working.</p><p>Nobody asked me to. There was no job posting. No encouragement. No guarantee that this effort would ever matter.</p><p>I built a full data project aligned with the center’s work. Research, analysis, dashboards and documentation. Nights. Weekends. Quiet hours when doubt was loud.</p><p>Friends asked reasonable questions like:<br> “Who asked you to do this?”<br> “What are you even doing?”</p><p>I didn’t have good answers.</p><p>All I had was prayer and the growing realization that obedience doesn’t always come with clarity.</p><p>So I kept going.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*f1XFWU5mAvFu8hYV.jpg" /></figure><h3>Prayer in the Middle of Uncertainty</h3><p>This was the season I prayed the most and understood the least.</p><p>I wasn’t praying for success anymore. I was praying for peace. For direction. For confirmation that this effort wasn’t wasted.</p><p><strong>“God, if You’re not in this, please stop me.<br>“If You are, please sustain me.”</strong></p><p>Sometimes the prayers felt powerful. Other times they felt like words bouncing off the ceiling.</p><p>Still, I showed up the next day and worked again.</p><h3>The Rejection That Felt Final</h3><p>In October, I followed up.</p><p>The response came back quickly and clearly.</p><p>They were not hiring. Not now. Not later. Not for Spring.</p><p>It wasn’t cruel. It was just… final.</p><p>I sat with that email for a long time. Long enough for disappointment to turn into acceptance. Long enough to start recalculating my plans. Canada? Europe? Staying Put? “Maybe next year?”</p><p>I prayed again, this time without asking for a reversal. Just asking God to help me let go if this was truly the end.</p><p>For about two weeks, I assumed it was.</p><h3>When God Answers Quietly</h3><p>Then something shifted.</p><p>Another email arrived. Same people. Different tone.</p><p>Circumstances had changed. Funding had moved. Conversations were happening. They wanted to talk.</p><p>I didn’t celebrate immediately. I’d learned better by then. I just listened.</p><p>We scheduled a meeting. We spoke honestly about my background, my work and the project I’d built months earlier when nothing was guaranteed.</p><p>Hours later, an offer came.<br>Not weeks. Not months.<br><strong>Hours</strong>.</p><p>I didn’t shout. I didn’t run around the room. I just sat there, stunned, realizing that what felt like a closed door had actually been a delay.</p><h3>Numbers That Made Me Pause</h3><p>When the official documents arrived, I read the funding breakdown slowly. Then again.</p><p>Most of my costs were covered.</p><p>Enough to breathe. <br>Enough to focus. <br>Enough to make the journey possible without panic.</p><p>I called my parent. They shouted with excitement.</p><p>But the journey wasn’t done yet. The reality reminded me that a funded offer still means nothing without a visa.</p><h3>The Part Where Faith Was Tested Again</h3><p>Days before my visa interview, a presidential proclamation dropped that made Nigerian student visas uncertain.</p><p>Bad timing is an understatement.</p><p>I prayed again. Not with confidence. With surrender.</p><p>At the embassy, the interview was calm. Professional. Then came Administrative Processing…And just for the record it wasn’t as smooth as this essay makes it sound.</p><p>Waiting again.</p><p>This time, I didn’t ask God <em>why</em>. I just asked Him to carry me through whatever the outcome would be.</p><p>Then, unexpectedly, it cleared.</p><p>Administrative Processing changed to <strong>Approved</strong>.<strong> <br></strong>Approved changed to <strong>Issued</strong>.</p><h3>Arrival Without Noise</h3><p>Six days ago, I cleared immigration in Dallas-Fort Worth Airport, Texas waiting for my connecting flight to Kansas.</p><p>No announcements. <br>No applause. <br> Just a stamp and a nod.</p><p>I sat down afterward and felt something I hadn’t felt in months: stillness.</p><p>Looking back now, I see what I couldn’t see then.</p><p>God wasn’t absent in the silence.<br> He wasn’t ignoring the rejection.<br> He wasn’t late.</p><p>He was rearranging things quietly, while I was busy worrying.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*EsKNy0zKyUbIsyRp" /></figure><h3>What This Journey Taught Me</h3><ul><li>Prayer doesn’t always change circumstances immediately. Sometimes it changes endurance.</li><li>Opportunities don’t always exist before you prepare for them</li><li>Faith doesn’t mean waiting passively. It means working faithfully without guarantees.</li><li>Anxiety is low but rarely accurate.</li><li>Rejection can be accurate and still not be final.</li><li>And God rarely explains Himself in advance. He lets the story make sense in hindsight.</li><li>Sometimes the thing that changes your life starts as an email nobody owes you a reply to.</li></ul><h3>Final Reflection</h3><p>Six months ago, I was told <em>“we’re not hiring.”</em></p><p>Six days ago, I landed in the United States.</p><p>Not because I forced anything.<br>Not because I was entitled to anything.</p><p>But because I stayed in motion when it would’ve been easier to stop.</p><p>If you’re in a season where you’ve prayed and nothing seems to be moving, hear this:</p><p><strong>The story might not be over yet.<br>You might just be between emails.</strong></p><p><strong>Silence is not absence.<br>Effort is never wasted when surrendered to God.</strong></p><p>Faith kept me moving when clarity didn’t exist.</p><p>Sometimes that’s enough!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17860130a994" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Here’s What I Wish Someone Told Me Today]]></title>
            <link>https://medium.com/@abadmus012/heres-what-i-wish-someone-told-me-today-641aaafd8d2c?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/641aaafd8d2c</guid>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Sat, 01 Nov 2025 06:31:55 GMT</pubDate>
            <atom:updated>2025-11-01T06:31:55.763Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A very real survival guide by a man in transition</em></p><p>Today I wish someone told me,</p><p>“Bro, you’re not losing it, you’re evolving.”</p><p>Because sometimes trying feels like madness.</p><p>Trying to become more than where you started.</p><p>Trying to build a future you’ve never seen modeled.</p><p>Trying to put your head down and grow while the world pretends success happens instantly.</p><p>Trying to pick yourself up after silent rejections and ghosted messages, corporate or romantic lol.</p><p>Trying to believe that the late nights, dashboards, scripts and strategy boards will one day matter.</p><p><strong>Some days I wish someone would remind me:</strong></p><p>“You’re not behind, you’re just early in your becoming.”</p><p>Because it’s easy to scroll through timelines and feel like everyone else is already living the soft life, while you’re refreshing emails, troubleshooting a broken Docker container and praying that the thing you’re pouring into eventually pours back.</p><p><strong>The Hallway Season</strong></p><p>Nobody talks enough about the transition phase,</p><p>when you’ve outgrown your old story</p><p>but haven’t fully stepped into your new one.</p><p>That hallway is loud.</p><p>Plans echo there.</p><p>Doubts echo there.</p><p>Faith echoes there.</p><p>Hope echoes too, if you listen closely.</p><p>But if the questions are still there, it means you haven’t quit.</p><p>And to be honest? That’s enough to keep going.</p><p>I’ve lost sleep.</p><p>I’ve lost plans.</p><p>I even lost a Duolingo streak I was irrationally proud of.</p><p>But I haven’t lost my hunger.</p><p>And as long as the fire is still there, the future is too.</p><p>Data Engineering and Dating Shouldn’t Feel Alike</p><p><strong>Funny thing:</strong> debugging pipelines sometimes feels easier than decoding people.</p><p>Kafka at least comes with producers, consumers and topics that make sense.</p><p>Real life? Sometimes you just get silence and you’re left wondering whether you’re the bug or the feature they weren’t ready for.</p><p>But even then, the goal isn’t to be loved first.</p><p>It’s to be seen.</p><p>For someone, even if that someone is you, to notice the discipline, the building, the vision, the grit.</p><p>I don’t need applause.</p><p>I just need alignment.</p><p><strong>If My Life Were a Dashboard Right Now…</strong></p><p>It would probably have 3 tabs:</p><p>1) Becoming Mode: study plans, projects, growth checkpoints</p><p>2) Silent Hustle Tracker: effort logged, even when results lag</p><p>3) Faith vs Frustration Chart: belief spiking, doubt dipping, progress trending upward</p><p>The metrics might fluctuate, but the commitment is constant.</p><p><strong>To Everyone in the In-Between</strong></p><p>If you’re in the hallway too, between where you were and where you’re going…</p><p>You’re not weak for wanting more.</p><p>You’re not dramatic for feeling the weight of patience.</p><p>You’re not lost, you’re in motion.</p><p>Everything you’re building is accumulating,</p><p>even if no one is clapping yet.</p><p>Keep sharpening.</p><p>Keep believing.</p><p>Keep becoming.</p><p>One day soon, when doors open, don’t downplay how hard you fought to hold on during the wait.</p><p>With resilience, humor and quiet confidence</p><p>— <strong>Ademola</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=641aaafd8d2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Building a Kafka Pipeline with Python and Docker: From Local Dev to Real-Time Streaming]]></title>
            <link>https://medium.com/@abadmus012/building-a-kafka-pipeline-with-python-and-docker-from-local-dev-to-real-time-streaming-e8ca24e54941?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8ca24e54941</guid>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Wed, 16 Jul 2025 16:14:31 GMT</pubDate>
            <atom:updated>2025-07-16T16:19:52.208Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4oX4h6DouxWXtHZ2CPV72g.png" /></figure><h3>👋 Hello, Kafka Curious!</h3><p>You’ve heard about Kafka. You’ve seen it in job listings. People toss the term around like seasoning in a dev conference.</p><p>But what is Kafka, really? And how do you, as a beginner, go from <em>“I’ve never seen this thing before”</em> to <em>“I can build a working Kafka pipeline”</em>?</p><p>That’s exactly what I did — and in this post, I’ll walk you through every single step, with humour, honesty, and real working code.</p><p>This article covers:</p><ul><li>Creating a virtual environment</li><li>Setting up Kafka with Docker</li><li>Writing a Python producer script</li><li>Reading messages with a Kafka consumer</li><li>Troubleshooting (like a boss)</li><li>Understanding what’s really happening behind the scenes</li></ul><p>No fluff. No complex jargon. Just real talk, real code.</p><h3>🔧 Step 1: Create a Python Virtual Environment (Best Practice)</h3><p>Why? To keep your Python dependencies clean and separate from other projects.</p><h3>✅ Create and Activate VENV:</h3><pre>python -m venv kafka_env<br>.\kafka_env\Scripts\activate     # On Windows<br>source kafka_env/bin/activate       # On Mac/Linux</pre><h3>📚 Install the kafka-python package:</h3><pre>pip install kafka-python</pre><h3>⚙️ Step 2: Kafka in Docker (Your New Best Friend)</h3><p>Installing Kafka manually is a pain. But Docker makes it easy.</p><p>Here’s the docker-compose.yml file I used to spin up everything:</p><h3>🛠️ docker-compose.yml</h3><pre>services:<br>  zookeeper:<br>    image: confluentinc/cp-zookeeper:7.2.1<br>    environment:<br>      ZOOKEEPER_CLIENT_PORT: 2181<br><br>  kafka:<br>    image: confluentinc/cp-kafka:7.2.1<br>    depends_on:<br>      - zookeeper<br>    ports:<br>      - &quot;9092:9092&quot;<br>    environment:<br>      KAFKA_BROKER_ID: 1<br>      KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181<br>      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://localhost:9092,DOCKER://kafka:29092<br>      KAFKA_LISTENERS: PLAINTEXT://0.0.0.0:9092,DOCKER://0.0.0.0:29092<br>      KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: PLAINTEXT:PLAINTEXT,DOCKER:PLAINTEXT<br>      KAFKA_AUTO_CREATE_TOPICS_ENABLE: &#39;true&#39;<br>      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1<br><br>  connect:<br>    image: confluentinc/cp-kafka-connect:7.2.1<br>    depends_on:<br>      - kafka<br>    ports:<br>      - &quot;8083:8083&quot;<br>    environment:<br>      CONNECT_BOOTSTRAP_SERVERS: &quot;kafka:29092&quot;<br>      CONNECT_REST_PORT: &quot;8083&quot;<br>      CONNECT_REST_ADVERTISED_HOST_NAME: &quot;connect&quot;<br>      CONNECT_GROUP_ID: &quot;connect-cluster&quot;<br>      CONNECT_CONFIG_STORAGE_TOPIC: &quot;connect-configs&quot;<br>      CONNECT_OFFSET_STORAGE_TOPIC: &quot;connect-offsets&quot;<br>      CONNECT_STATUS_STORAGE_TOPIC: &quot;connect-status&quot;<br>      CONNECT_CONFIG_STORAGE_REPLICATION_FACTOR: &quot;1&quot;<br>      CONNECT_OFFSET_STORAGE_REPLICATION_FACTOR: &quot;1&quot;<br>      CONNECT_STATUS_STORAGE_REPLICATION_FACTOR: &quot;1&quot;<br>      CONNECT_KEY_CONVERTER: &quot;org.apache.kafka.connect.json.JsonConverter&quot;<br>      CONNECT_VALUE_CONVERTER: &quot;org.apache.kafka.connect.json.JsonConverter&quot;<br>      CONNECT_INTERNAL_KEY_CONVERTER: &quot;org.apache.kafka.connect.json.JsonConverter&quot;<br>      CONNECT_INTERNAL_VALUE_CONVERTER: &quot;org.apache.kafka.connect.json.JsonConverter&quot;<br>      CONNECT_PLUGIN_PATH: &quot;/usr/share/java,/etc/kafka-connect/jars&quot;<br>    volumes:<br>      - ./local_folder_container:/tmp/inputservices:<br>  zookeeper:<br>    image: confluentinc/cp-zookeeper:7.2.1<br>    environment:<br>      ZOOKEEPER_CLIENT_PORT: 2181</pre><h3>🔧 To Run:</h3><pre>docker-compose up -d     # Start everything<br>docker-compose down      # Stop everything<br>docker ps                # Check containers</pre><h3>📨 Step 3: Write the Producer Script</h3><p>Let’s produce some data to Kafka! Our data source? A plain text file.</p><h3>🐍 file_producer.py</h3><pre>from kafka import KafkaProducer<br><br>producer = KafkaProducer(<br>    bootstrap_servers=&#39;localhost:9092&#39;,<br>    value_serializer=lambda v: v.encode(&#39;utf-8&#39;)<br>)<br><br>with open(&#39;local_folder_container/input.txt&#39;, &#39;r&#39;) as file:<br>    for line in file:<br>        message = line.strip()<br>        if message:<br>            producer.send(&#39;my-topic&#39;, value=message)<br>            print(f&quot;Sent: {message}&quot;)<br><br>producer.flush()<br>producer.close()</pre><p>Make sure your file is named input.txt and inside local_folder_container</p><h3>▶️ Run it:</h3><pre>python file_producer.py</pre><h3>📂 Step 4: Write the Consumer Script</h3><p>Let’s read those messages from the topic we just wrote to.</p><h3>🧔‍♂️ file_consumer.py</h3><pre>from kafka import KafkaConsumer<br><br>consumer = KafkaConsumer(<br>    &#39;my-topic&#39;,<br>    bootstrap_servers=&#39;localhost:9092&#39;,<br>    auto_offset_reset=&#39;earliest&#39;,<br>    enable_auto_commit=True,<br>    group_id=&#39;my-group&#39;,<br>    value_deserializer=lambda x: x.decode(&#39;utf-8&#39;)<br>)<br><br>print(&quot;Listening for messages... Press Ctrl+C to stop.&quot;)<br><br>try:<br>    for message in consumer:<br>        print(f&quot;Received: {message.value}&quot;)<br>except KeyboardInterrupt:<br>    print(&quot;\nStopping consumer...&quot;)<br><br>consumer.close()</pre><h3>▶️ Run it:</h3><pre>python file_consumer.py</pre><h3>↖️ Recap: What Just Happened?</h3><p>Here’s the data flow in plain English:</p><pre>Your Text File → Producer Script → Kafka Topic → Python Consumer</pre><p>Or visually:</p><pre>📄 input.txt<br>   │<br>   ▼<br>🐍 file_producer.py (Python script)<br>   │<br>   ▼<br>📆 Kafka (my-topic)<br>   │<br>   ▼<br>📅 file_consumer.py (read messages)</pre><p>You just ran a full event streaming pipeline locally like a real data engineer.</p><h3>🪰 Helpful Commands</h3><h3>🔍 Docker Basics</h3><pre>docker-compose up -d     # Start all services<br>docker-compose down      # Stop them all<br>docker ps                # Check running containers<br>docker logs &lt;name&gt;       # Get logs (good for debugging)</pre><h3>🦨 Kafka CLI Goodies</h3><pre># List topics<br>docker exec -it kafka kafka-topics \<br>  --bootstrap-server kafka:9092 \<br>  --list<br><br># Read messages<br>docker exec -it kafka kafka-console-consumer \<br>  --bootstrap-server kafka:9092 \<br>  --topic my-topic \<br>  --from-beginning</pre><p><strong>Now that we have Kafka working:</strong></p><p>✅ You understand the fundamentals<br> ✅ You’ve created your own working pipeline<br> ✅ You’ve isolated dependencies in a venv</p><p>Let’s go further:</p><ul><li>🔊 Connect Kafka to a real database like PostgreSQL</li><li>🌍 Use Kafka Connect to move data between systems</li><li>📊 Build a real-time dashboard with Streamlit or Grafana</li></ul><h3>💡 Final Thoughts</h3><p>Kafka seemed scary at first. Now? You’ve containerized it, scripted it, and sent real data through it.</p><p>You’re not just learning. You’re building. You’re preparing for real-world data engineering work.</p><p>Let’s keep going.<br>Let’s build something magical.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8ca24e54941" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Scaling Smart: How ELB, ASG & GWLB Keep AWS Applications Running Smoothly]]></title>
            <link>https://medium.com/@abadmus012/scaling-smart-how-elb-asg-gwlb-keep-aws-applications-running-smoothly-1fc21e913fdb?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fc21e913fdb</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[autoscaling]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Tue, 15 Apr 2025 23:03:28 GMT</pubDate>
            <atom:updated>2025-04-15T23:19:50.351Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ogm1pp9_72jfNT8nqwV2kQ.jpeg" /></figure><p>🌟 <strong>Introduction<br>Imagine this:</strong> You’ve built a fantastic application, users are loving it and suddenly, Traffic surges and your server crashes. 😱 What went wrong? Your infrastructure wasn’t ready for scale.</p><p>Enter <strong>Elastic Load Balancing (ELB)</strong>, <strong>Auto Scaling Groups (ASG)</strong> and <strong>Gateway Load Balancer (GWLB)</strong>, three AWS superheroes that ensure your application remains <strong>fast, reliable, </strong>and <strong>cost-efficient</strong> no matter how much traffic comes its way.</p><p><em>But how do they work? And why should you care? This article will break it all down in a fun and engaging way! Let’s dive in</em>! 🚀</p><p>🎯 <strong>The Problem:</strong> Handling Traffic Spikes &amp; Failures</p><p>Picture an e-commerce website during Black Friday. Millions of users rush in, eager to land deals. If the infrastructure isn’t prepared, the site will slow down, freeze or crash completely.<strong> Lost sales. Angry customers. Nightmare scenario!</strong></p><p>Thankfully, AWS has<strong> three secret weapons</strong> to tackle this issue:<br>1. <strong>Elastic Load Balancing (ELB)</strong> — Distributes traffic efficiently across multiple servers 🏗️.<br>2. <strong>Auto Scaling Groups (ASG)</strong> — Automatically scales resources up and down as needed 📈📉.<br>3. <strong>Gateway Load Balancer (GWLB)</strong>— Handles traffic at scale while keeping network security top-notch 🔒.</p><p>Let’s break them down! 👇</p><p>⚖️ <strong>Elastic Load Balancing (ELB):</strong> The Traffic Director 🎛️</p><p>Think of ELB as a skilled traffic officer 🚦 directing incoming requests to the best-performing server. Without ELB, some servers would be overwhelmed while others sit idle. <strong>That’s inefficient!</strong></p><p>🛠️ <strong>What ELB Does:</strong><br>✅ <strong>Balances Load</strong> — Prevents any single server from getting overloaded.<br>✅ <strong>Handles Failures</strong> — If a server goes down, ELB reroutes traffic to healthy servers.<br>✅<strong>Enhances Security </strong>— Works with AWS security groups and firewalls to block malicious traffic.<br>✅ <strong>Improves Speed</strong>— Ensures user requests reach the closest and fastest available server.</p><p>⚡ Types of ELB:<br>- <strong>Application Load Balancer (ALB)</strong> — Best for handling HTTP/HTTPS web traffic 🌍.<br>- <strong>Network Load Balancer (NLB)</strong> — Ideal for ultra-low latency networking 🚀.<br>- <strong>Classic Load Balancer (CLB)</strong> — Basic load balancing for older applications 🔧.</p><p>👉<strong><em> Picture Idea: An illustration of a busy intersection with an ELB sign directing cars (traffic) to multiple roads (servers).</em></strong></p><p>📈<strong> Auto Scaling Groups (ASG):</strong> The Elastic Workforce 💪</p><p>What if your system could <strong>magically </strong>add more servers when traffic spikes and remove them when demand drops? That’s exactly what ASG does! 🚀</p><p>🔥 <strong>Why ASG is Awesome</strong>:<br>✅ <strong>Automatic Scaling</strong> — Adds or removes instances based on demand.<br>✅ <strong>Cost Efficiency</strong> — Only pays for what’s needed, avoiding over-provisioning.<br>✅ <strong>Resilience</strong> — Instantly replaces failed instances.<br>✅ <strong>Handles Spikes</strong>— Expands infrastructure automatically during peak hours.</p><p>🏗️ How ASG Works:<br>1. You <strong>set rules</strong> (e.g., “Add a new server if CPU usage goes above 80%”).<br>2. ASG <strong>monitors</strong> system health in real time.<br>3. It s<strong>pins up</strong> new instances when demand increases.<br>4. It <strong>scales down</strong> when traffic slows to save costs.</p><p>🏢 <strong>Gateway Load Balancer (GWLB):</strong> The Security Boss 🔒</p><p>What if you have <strong>firewalls, intrusion detection systems (IDS) or deep packet inspection (DPI) tools</strong> that need to scale <strong>without creating bottlenecks</strong>? That’s where <strong>GWLB </strong>comes in! 🎯</p><p>🛡️ <strong>Why You Need GWLB:</strong><br>✅ <strong>Scales Security Appliances</strong> — Load balances traffic across security tools.<br>✅ <strong>Centralized Network Inspection</strong> — Simplifies network security deployment.<br>✅ <strong>Seamless Failover</strong> — Ensures no downtime if a security appliance crashes.<br>✅ <strong>Works with Any Firewall </strong>— Compatible with Fortinet, Palo Alto, and more!</p><p>🔄 <strong>How GWLB Works:</strong><br>1. <strong>Routes traffic</strong> to security appliances.<br>2. <strong>Scales security instances</strong> dynamically.<br>3.<strong> Ensures security processing</strong> without causing slowdowns.</p><p>🔗 <strong>ELB, ASG &amp; GWLB: The Ultimate AWS Trio </strong>🤝</p><p>These three AWS services <strong>work together seamlessly</strong> to keep applications performing at their best:</p><p>- <strong>ELB </strong>distributes traffic 🏎️.<br>- <strong>ASG </strong>ensures enough servers handle the load ⚙️.<br>- <strong>GWLB</strong> secures everything 🔐.</p><p>🏆 <strong>Real-World Example</strong>:<br>Imagine you run a streaming platform 📺 like Netflix. During peak hours:<br>- ELB <strong>routes user requests</strong> efficiently.<br>- ASG <strong>spins up more instances</strong> to handle more viewers.<br>- GWLB <strong>ensures security appliances scale smoothly</strong>.</p><p>Result? <strong>No buffering. No downtime. No complaints.</strong>🎉</p><p>🚀 <strong>Getting Started with ELB, ASG &amp; GWLB</strong></p><p>Want to try it yourself? Follow these simple steps:<br>1. <strong>Set up an ELB</strong> in AWS and choose the right type (ALB, NLB, CLB).<br>2. <strong>Create an Auto Scaling Group</strong> to manage EC2 instances dynamically.<br>3. <strong>Integrate a GWLB</strong> if you need advanced network security at scale.<br>4. <strong>Test your setup </strong>by simulating high traffic and checking load balancing behavior.</p><p>AWS provides step-by-step guides, but <strong>hands-on experience is the best teacher!</strong>🎓</p><p>🎯 <strong>Conclusion</strong>: Build Scalable &amp; Resilient AWS Applications</p><p>If you want to build <strong>highly available, cost-effective, and secure</strong> cloud applications, <strong>ELB, ASG, and GWLB are your best friends.</strong></p><p>✅ <strong>ELB </strong>ensures traffic is evenly distributed.<br>✅ <strong>ASG </strong>makes sure your app scales automatically.<br>✅ <strong>GWLB </strong>keeps your network **secure and efficient**.</p><p>So, next time you hear abou<strong>t load balancing, auto-scaling, or network security</strong>, you’ll know exactly what’s happening behind the scenes! <strong>Keep exploring AWS, and soon you’ll be scaling applications like a pro! 🚀</strong></p><p>💡 Want More? Let me know what AWS topic you’d love to learn about next in the comments! 👇</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fc21e913fdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding Amazon EC2: Instance Types, Pricing Models and Use Cases ]]></title>
            <link>https://medium.com/@abadmus012/decoding-amazon-ec2-instance-types-pricing-models-and-use-cases-2e271b0dc3a4?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e271b0dc3a4</guid>
            <category><![CDATA[ec2-instance]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[servers]]></category>
            <category><![CDATA[computing]]></category>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 22:39:51 GMT</pubDate>
            <atom:updated>2025-01-29T08:43:04.958Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there! If you’re new to AWS, you’ve probably heard about Amazon EC2. It’s one of AWS’s most talked-about services but when I first looked into it, I felt completely lost. 😅</p><p>What are these “instance types”? Why are there so many pricing options? And how do you even know which one to pick? If these questions sound familiar, you’re in the right place. In this guide, I’ll share what I’ve learned about EC2 in a way that (hopefully) makes it easy for both of us to understand. Let’s figure this out together! 💡</p><p><strong>What is Amazon EC2?<br></strong>Imagine you’re building something cool, maybe a website, an app or a data processing tool. You need a computer to run it on but buying and managing servers sounds stressful. That’s where EC2 come in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Ccc3nkDvvpn7f31DkliXQ.jpeg" /><figcaption>Amazon Elastic Compute Cloud</figcaption></figure><p>Amazon EC2 lets you “rent” virtual computers in the cloud. You can:</p><ul><li><strong>Choose how powerful your computer is.</strong></li><li><strong>Pay only for the time you use it</strong></li><li><strong>Scale up or down as your needs change.</strong></li></ul><p>Think of it like renting a laptop when you need it instead of buying one outright. More convenient, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*GZPK1y5ajxuQSfF7U4rv4g.gif" /></figure><p><strong>Instances Type: What are they?</strong> <strong>🤔<br></strong>Okay, so “instance types” are basically different kinds of virtual computers. AWS give you a bunch of options and each one is optimized for specific tasks. Here’s a breakdown:</p><ol><li><strong>General Purpose Instances</strong><br>- <strong>What they are</strong>: Jack-of-all-trades. Good for most tasks.<br>- <strong>Examples</strong>: t3,m5<br>- <strong>Use Case</strong>: Hosting a website, running small apps or experimenting<br>- <strong>Analogy</strong>: Like a family car reliable for everyday use.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*kQw6A_daa0RRE789m5IgFA.gif" /><figcaption>Family Car lol</figcaption></figure><p><strong>2. Compute Optimized Instances<br></strong>- <strong>What they are</strong>: Built for speed and power<br>- <strong>Examples</strong>:c5, c6g<br>- <strong>Use Case</strong>: Heavy math calculation, gaming servers or machine learning.<br>- <strong>Analogy</strong>: A sports car fast and efficient but not for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*akm1PfrtelGRlumUYAsdKQ.gif" /><figcaption>Sport Car?</figcaption></figure><p><strong>3. Memory Optimized Instances<br></strong>- <strong>What they are</strong>: Tons of memory for handling large datasets.<br>- <strong>Examples</strong>: r5, x2idn<br>- <strong>Use Case</strong>: Big data analytics, caching or in-memory databases.<br>- <strong>Analogy</strong>: A moving truck made for carrying heavy loads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*-46VkXuRTM09jdt6sIHQYA.gif" /><figcaption>Moving Truck</figcaption></figure><p><strong>4. Storage Optimized Instances<br></strong>- <strong>What they are</strong>: Designed for fast and massive storage.<br>- <strong>Examples</strong>: i3, d2<br>- <strong>Use Case</strong>: Processing huge files like videos or big databases.<br>- <strong>Analogy</strong>: A cargo train carries a lot but needs a clear track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*WBS7SGpYvwHIOEMUX6bmGQ.gif" /><figcaption>Cargo Train</figcaption></figure><p><strong>5. Accelerated Computing Instances<br></strong>- <strong>What they are</strong>: Packed with GPUs for high-performance tasks.<br>- <strong>Examples</strong>: p4, g5<br>- <strong>Use Case</strong>: Training AI models, rendering videos or scientific simulation.<br>- <strong>Analogy</strong>: A rocket, powerful but specialized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*oqVd8_K9eoecXC6QW9rnXg.gif" /><figcaption>Powerful Rocket</figcaption></figure><p><strong>Pricing Models: How much Does it Cost? </strong>💸</p><p>AWS gives you multiple ways to pay for EC2, depending on your needs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*GSSXqDlnyjvRkEP8aWFbQQ.gif" /></figure><ol><li><strong>On-Demand Instances<br></strong>- <strong>What it is</strong>: Pay as you go. No commitments.<br>- <strong>Best for</strong>: Trying things out or short-term projects.<br>- <strong>Analogy</strong>: Like renting a car for a day trip</li><li><strong>Reserved Instances<br></strong>- <strong>What it is</strong>: Commit to using an instance for 1 or 3 years for big savings.<br>- <strong>Best for</strong>: Long-term, predictable projects.<br>- <strong>Analogy</strong>: Leasing a car, you pay less but commit for the long haul</li><li><strong>Spot Instances<br></strong>- <strong>What it is</strong>: Buy unused capacity at a discount (up to 90% off!).<br>- <strong>Best for</strong>: Flexible tasks that can handle interruptions.<br>- <strong>Analogy</strong>: Last-minute flight deals, cheap but not guaranteed</li><li><strong>Saving Plans<br></strong>- <strong>What it is</strong>: Commit to a set amount of usage (e.g., $10/hour) for a discount.<br>- <strong>Best for</strong>: Projects with consistent workloads.<br>- <strong>Analogy</strong>: A subscription box, predictable costs with flexibility.</li></ol><p><strong>Use Cases: When Should You Use EC2?</strong></p><ul><li><strong>Building a Portfolio Website</strong>. 🌐<br>Use a general-purpose instance to host your personal site</li><li><strong>Learning Machine Learning</strong>. 🤖<br>Train small models on a compute-optimized instance</li><li><strong>Storing and Analysing Data</strong>. 📊<br>Try a memory-optimized instance to crunch numbers or store datasets.</li><li><strong>Running Experiments</strong> 🧪<br>Use spot instances to test new ideas without spending much.</li></ul><p><strong>Tips for Beginners (from someone just diving into AWS!)</strong></p><ol><li><strong>Start Small</strong>: Use the AWS Free Tier (e.g. t2.micro) to practice without spending money.</li><li><strong>Watch Tutorials</strong>: AWS has great free resources or check out YouTube.</li><li><strong>Track Costs</strong>: Use AWS Cost Explorer to make sure you’re not overspending.</li><li><strong>Experiment</strong>: Don’t be afraid to break things (virtually). It’s how you learn!</li></ol><p><strong>Final Thoughts</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*GziWJssWJ5ZG2ml5buInyw.jpeg" /><figcaption>You’ve Got This! 🙌</figcaption></figure><p>Amazon EC2 might seem intimidating at first but once you break it down, it’s not so bad. Start with small projects, experiment with different instance types and keep learning.</p><p>💡<strong>Your Turn:</strong> What’s the first thing you’d like to try with EC2?</p><p><strong><em>If this post helped you, give it a clap 👏 and save it for later. Let’s learn AWS together, one step at a time!</em> 🚀</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e271b0dc3a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Understanding AWS Identity and Access Management (IAM): The Basics]]></title>
            <link>https://medium.com/@abadmus012/understanding-aws-identity-and-access-management-iam-the-basics-f62fa6d4f229?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f62fa6d4f229</guid>
            <category><![CDATA[iam-roles]]></category>
            <category><![CDATA[iam-policy]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Wed, 01 Jan 2025 18:49:16 GMT</pubDate>
            <atom:updated>2025-01-01T18:49:16.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ojvGatXSA1bQ1iYBAbDDVA.png" /></figure><p><strong>Ever wondered how companies secure their cloud environments on AWS? 🤔</strong> Imagine you’re running a company and need to grant access to employees but only for the tasks they need to do, no more, no less. That’s exactly where AWS Identity and Access Management (IAM) steps in! Let’s take a fun and beginner-friendly dive into IAM and why it’s the backbone of AWS security. 🔒</p><p><strong>What is AWS IAM?</strong> 🌐<br>AWS IAM (Identity and Access Management) is like the security guard 🚓 for your AWS environment. It decides: <br>- <strong>Who can access what?</strong> 🧑‍💻<br>- <strong>What actions can they perform?</strong> ✅<br>- <strong>Under what conditions?</strong> 🤷‍♂️</p><p>With IAM, you can create and manage <strong>users, groups </strong>and <strong>roles</strong> ensuring that everyone and everything in your AWS account only gets the permissions they actually need.</p><p><strong>Why Should You Care About IAM?</strong> 🧐<br>Think about IAM as a set of keys 🔑 for different rooms in your office. You wouldn’t give the janitor access to your financial records, right? Similarly, in AWS, IAM ensures that each user has the right level of access without compromising security.</p><p><strong>Core Components of IAM</strong> 🏗️<br>Let’s break it down step-by-step:</p><p>1. <strong>Users: </strong>The Who 👤<br>A user in IAM represents a <strong>person</strong> or <strong>application </strong>that interacts with AWS. Each user gets:<br>- A <strong>username</strong> 🏷️<br>- <strong>Credentials</strong> (passwords or access keys) 🔐<br>- Assigned <strong>permissions</strong>📜</p><p>Example: Jane, the database administrator, needs access to RDS databases but not to billing information.</p><p>2. <strong>Groups</strong>: The Team 👥<br>Groups are like departments in a company. Instead of assigning permissions to users one by one, you can group them and apply rules collectively.</p><p>Example: The “Developers” group has access to EC2 and S3, while the “Finance” group only views billing data.</p><p>3. <strong>Roles</strong>: Temporary Hats 🎩<br>Roles are a bit different, they’re not tied to specific users. Instead, they’re temporary identities that services or applications can assume to perform specific tasks.</p><p>Example: An EC2 instance can assume a role to access an S3 bucket without storing credentials.</p><p>4. <strong>Policies: </strong>The Rules 📜<br>Policies are the heart ❤️ of IAM. They define <strong>what actions</strong> are allowed or denied on <strong>which resources</strong>. Policies are written in JSON (don’t worry, it’s easier than it sounds). 😅</p><p>Here’s an example policy that allows users to view only S3 buckets:</p><pre>{<br>  &quot;Version&quot;: &quot;2012-10-17&quot;,<br>  &quot;Statement&quot;: [<br>    {<br>      &quot;Effect&quot;: &quot;Allow&quot;,<br>      &quot;Action&quot;: &quot;s3:ListBucket&quot;,<br>      &quot;Resource&quot;: &quot;*&quot;<br>    }<br>  ]<br>}</pre><p><em>Translation: </em><strong><em>You can look, but you can’t touch!</em></strong><em> 👀❌</em></p><p>5. <strong>Multi-Factor Authentication (MFA):</strong> The Lock 🔒<br>Want an extra layer of security? IAM supports MFA, requiring a one-time code 🔢 along with your password. This is like adding a fingerprint scanner to your office door. 👆</p><p><strong>Common IAM Scenarios and Use Cases </strong>💼</p><p>1. <strong>Managing Team Access</strong>: Grant developers access to deploy applications but restrict access to billing data. 💻📊<br>2. <strong>Third-Party Access</strong>: Allow contractors to upload files to a specific S3 bucket without giving them full access. 🛠️📦<br>3. <strong>Application Roles</strong>: Enable Lambda functions to read/write from DynamoDB without embedding credentials in code. ⚡📂<br>4. <strong>Temporary Access</strong>: Use IAM roles for temporary access during audits or troubleshooting. 🕵️‍♂️⏳</p><p><strong>Best Practices for Using IAM</strong> ✅<br>Here’s how to make IAM work smarter (and safer) for you:</p><p>1.<strong> Follow the Principle of Least Privilege</strong>: Only grant the minimum permissions required for the task. 🔑<br>2. <strong>Enable MFA</strong>: Always enable multi-factor authentication for admin accounts. 🔒📲<br>3. <strong>Use Roles Instead of Access Keys</strong>: Roles are safer and easier to manage than storing long-term credentials. 🦾<br>4. <strong>Rotate Credentials Regularly</strong>: Avoid using static credentials by rotating them periodically. 🔄🔑<br>5. <strong>Monitor Access Logs</strong>: Use AWS CloudTrail to track who accessed what and when. 🕵️‍♀️📊</p><p><strong>Why IAM is a Game-Changer </strong>🏆<br>IAM is more than just an access control system; it’s the foundation of security in AWS. Whether you’re a solo developer or part of a large team, mastering IAM ensures that your resources are both accessible and protected. 💪</p><p><strong>What’s Next?</strong>🚀<br>Ready to get hands-on? Start by logging into your AWS console and experimenting with IAM Users and Groups. Create a policy, assign it, and test permissions. The more you practice, the more confident you’ll become. 😎</p><p><strong>Pro Tip</strong>: AWS provides a free tier, so you can try IAM without worrying about costs. 💸</p><p>Let me know how your IAM journey goes, I’d love to hear your thoughts and questions in the comments below! 💬✨</p><p><strong>Happy Learning and Secure Your AWS Cloud Like a Pro! </strong>🌟</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f62fa6d4f229" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Demystifying the AWS Global Infrastructure: Regions, Availability Zones and Edge Locations ]]></title>
            <link>https://medium.com/@abadmus012/demystifying-the-aws-global-infrastructure-regions-availability-zones-and-edge-locations-6885fc9f9edb?source=rss-35b43b5cb3a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6885fc9f9edb</guid>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[data-engineer]]></category>
            <category><![CDATA[servers]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Ademola]]></dc:creator>
            <pubDate>Sun, 08 Dec 2024 13:58:59 GMT</pubDate>
            <atom:updated>2024-12-08T14:33:14.908Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever watched a movie where a team of tech experts heroically saves the day by using servers all over the world, you’ve seen a Hollywood take on how modern cloud computing works. In reality, it’s less about dramatic countdowns and more about where our data lives, how it’s kept safe, and how it travels the internet.</p><p>I’m pretty new to this world myself — just a curious learner diving into AWS (Amazon Web Services) and figuring things out as I go 😅. Since I’ve been learning about the AWS Global Infrastructure, I wanted to share what I’ve discovered so far. In this article, I’ll break down three key concepts — <strong>Regions</strong>, <strong>Availability Zones (AZs)</strong>, and <strong>Edge Locations </strong>and show you why they matter to anyone interested in building or understanding cloud-based applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SXpctwi4zsBo5TtLu_PLew.png" /><figcaption>Amazon Web Services</figcaption></figure><h3>What Is AWS Global Infrastructure and Why Should You Care?</h3><p>Think of AWS Global Infrastructure as a network of data centers scattered worldwide — strategically placed and carefully managed. These locations aren’t random; they’re chosen based on things like internet connectivity, local regulations, stable weather, and how close they are to customers.</p><p><strong>Why this matters:</strong> The physical location of your data affects how quickly you can access it. If a user in South Africa tries to load a website hosted on the other side of the planet, they might notice sluggish load times. Minimizing distance makes a difference in performance, reliability, and even meeting certain legal rules on where data can be stored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*CVwJueshvTxgTY2M8OjHvg.png" /><figcaption>A world map with small server icons placed at different points.</figcaption></figure><h3>AWS Regions: Your “Neighborhood” in the Cloud</h3><p>An AWS Region is like a big “neighborhood” of data centers in a specific geographic area — think places like Northern Virginia in the U.S., Dublin in Ireland or Sydney in Australia. Each Region represents a distinct part of the world where you can run your applications.</p><p><strong>Why Regions Matter:</strong></p><ul><li><strong>Performance:</strong> Closer Regions mean faster load times. It’s like choosing a nearby grocery store instead of one across town.🙂</li><li><strong>Compliance:</strong> Some data must legally stay within certain countries. Picking a Region in that country solves the problem.</li><li><strong>Cost &amp; Latency Differences:</strong> Each Region can have slightly different pricing or performance. Being aware of these can save money and improve user experience.</li></ul><p><strong>A Simple Example:</strong><br>If you have an app for users in West Africa, hosting it in a U.S. Region might cause noticeable lag. By choosing a Region in Europe or the Middle East, you bring the servers closer, making the experience smoother.</p><h3>Availability Zones: Built-In Safety Nets</h3><p><strong>What’s an AZ?</strong><br>Within each Region, there are multiple Availability Zones, each one containing one or more data centers. Think of them as individual houses inside the same neighborhood. Each AZ has its own power, cooling, and networking. The idea is that if one AZ faces a problem, the others won’t necessarily go down with it.</p><p><strong>Why AZs Matter:</strong></p><ul><li><strong>High Availability:</strong> By using multiple AZs, your application can survive even if one goes offline.</li><li><strong>Fault Tolerance:</strong> With AZs, you can design systems that keep running under almost any circumstance, which is huge for critical services like banking apps or healthcare systems.</li></ul><p><strong>A Simple Example:</strong><br>If your website is in only one AZ and that AZ experiences a power outage, your site is toast — at least until it’s fixed. But if you’ve spread your servers across two AZs, one can fail but the other keeps your app running smoothly.😊</p><h3>Edge Locations: Bringing the Cloud Even Closer</h3><p><strong>What’s an Edge Location?</strong><br>If Regions are neighborhoods and AZs are houses, Edge Locations are like the handy convenience stores on each street corner. They’re smaller, more specialized locations that hold copies of content — like images, videos, or web pages — to deliver them faster to nearby users.</p><p><strong>Why Edge Locations Matter:</strong></p><ul><li><strong>Reduced Latency for Content Delivery:</strong> Content stored closer to users means quicker load times. It’s like finding a store right around the block instead of driving across town.</li><li><strong>Global Consistency:</strong> With Edge Locations scattered worldwide, your users get a fast, consistent experience no matter where they’re located.</li></ul><p><strong>A Simple Example:</strong><br>If your website’s homepage has a big, beautiful image, users in Asia shouldn’t have to wait an extra second for it to load from a U.S. server. With an Edge Location in Tokyo, that image can be served up instantly, making the site feel snappy and responsive.🤗</p><h3>Putting It All Together</h3><ul><li><strong>Regions</strong> are broad geographic areas hosting multiple data centers, giving you choice and control over where your resources live.</li><li><strong>Availability Zones</strong> within those Regions ensure that if one data center has issues, your application doesn’t go down with it.</li><li><strong>Edge Locations</strong> make sure your content reaches users quickly, no matter which corner of the planet they’re on.</li></ul><p>By blending these three concepts together, AWS provides a global backbone for applications that can scale to millions of users, remain highly available, and deliver content at breakneck speeds.</p><h3>Why Understanding This Matters (Even If You’re a Beginner)</h3><p>As someone who’s still wrapping their head around AWS (just like I am), you’ll see these concepts in almost every architectural decision. Where do you launch servers? Which AZs should you choose? How do you ensure users on the other side of the globe get the same fast experience?</p><p>Understanding Regions, AZs and Edge Locations isn’t just for passing an exam. It’s about building apps that feel reliable, flexible and attuned to your users’ needs, wherever they are. Even if you’re just starting out, having a grasp on these ideas will help you design better solutions from day one.</p><p><strong>In the end, cloud computing may not have the Hollywood drama, but it’s a global, interconnected story worth understanding</strong>. As a fellow beginner, I hope this breakdown helps you feel more confident in navigating AWS’s global infrastructure. Let’s keep learning together! 🙂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6885fc9f9edb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>