<?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 Basat Tayfun on Medium]]></title>
        <description><![CDATA[Stories by Basat Tayfun on Medium]]></description>
        <link>https://medium.com/@bttsidehussle.aws.training?source=rss-b25510614fba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9d3LVoDJnChD-3BN</url>
            <title>Stories by Basat Tayfun on Medium</title>
            <link>https://medium.com/@bttsidehussle.aws.training?source=rss-b25510614fba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:07:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bttsidehussle.aws.training/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[An eyewitness news report: Building a Scalable Web Application using AWS Elastic Beanstalk…]]></title>
            <link>https://medium.com/@bttsidehussle.aws.training/an-eyewitness-news-report-building-a-scalable-web-application-using-aws-elastic-beanstalk-eee4e605cd74?source=rss-b25510614fba------2</link>
            <guid isPermaLink="false">https://medium.com/p/eee4e605cd74</guid>
            <category><![CDATA[amazon-cloudfront]]></category>
            <category><![CDATA[aws-edge-location]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[aws-auto-scaling]]></category>
            <dc:creator><![CDATA[Basat Tayfun]]></dc:creator>
            <pubDate>Wed, 21 Feb 2024 18:07:06 GMT</pubDate>
            <atom:updated>2024-02-21T18:07:06.959Z</atom:updated>
            <content:encoded><![CDATA[<h3>An eyewitness news report: Building a Scalable Web Application using AWS Elastic Beanstalk, DynamoDB, CloudFront and Edge Location</h3><p>What if you were responsible for implementing a high-demand application? Here is a real-life example: A voucher application that was accessed simultaneously by over 10,000 users (!) during a large conference. The users attended the conference (and accessed the application) from dozens of locations around the Globe.</p><p>The event was broadcast live and involved drawing for 10 vouchers for three (3) cloud certifications. During the live event, over 10,000 conference participants registered their e-mails to enter the drawing at the same time.</p><p>We used AWS to build and deploy the raffle application: Elastic Beanstalk to deploy the web application, DynamoDB to store emails, and CloudFront to cache static and dynamic files in Edge Locations around the World.</p><p>“Peace of cake”! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eee4e605cd74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A perfect example of how obsolete libraries can turn a good thing bad (or, how a simple Lift &…]]></title>
            <link>https://medium.com/@bttsidehussle.aws.training/a-simple-example-of-a-migration-from-on-premise-to-aws-web-front-end-mysql-back-end-1cbd8780444b?source=rss-b25510614fba------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cbd8780444b</guid>
            <category><![CDATA[software-migration]]></category>
            <category><![CDATA[version-conflict]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[legacy-software]]></category>
            <dc:creator><![CDATA[Basat Tayfun]]></dc:creator>
            <pubDate>Mon, 12 Feb 2024 10:11:21 GMT</pubDate>
            <atom:updated>2024-02-12T10:26:12.075Z</atom:updated>
            <content:encoded><![CDATA[<h3>A perfect example of how obsolete libraries can turn a good thing bad (or, how a simple Lift &amp; Shift exercise becomes a headache)</h3><p>This should have been simple. It should have been easy. In a perfect world, should have taken 30 minutes, 1 hour, tops! But, no! The Universe had other plans… A migration of a in-house workload to AWS was to have some nasty twists and turns.</p><p>The good thing was that the infrastructure (OS/machine, storage, DB and networking) was a piece of cake — must have taken less than 30 minutes to set up. Migrating the database was short and sweet, too.</p><p>But, the application (built with Flask) had other ideas. I blame the software developers! A systems guy like me can do only so much. The code and the stack it depends on have to be maintained. The “write once, use everywhere” is not “write once, then forget it”!</p><p>AWS does not support the older (obsolete?) versions of Python and associated Flask framework libraries. The Python part was OK — the code was new enough that it worked (as far as I could see, that is). But, the app used Flask for most functionality — from the UI to SQL transactions. Flask code for connecting to MySQL would not work as-is. So, I had to painstakingly update all SQL/back-end code so that the application would place nice with RDS.</p><p>Cloud does a lot to simplify life. But software can get in the way massively. You can take a piece of code to the cloud, but you cannot make it run on it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Y_jNDDOvBs6UwkMYSFa2g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cbd8780444b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Journey from utility-computing to cloud computing to multi-cloud computing]]></title>
            <link>https://medium.com/@bttsidehussle.aws.training/journey-from-utility-computing-to-cloud-computing-to-multi-cloud-computing-4028b7e84af1?source=rss-b25510614fba------2</link>
            <guid isPermaLink="false">https://medium.com/p/4028b7e84af1</guid>
            <category><![CDATA[stock-market]]></category>
            <category><![CDATA[multi-cloud]]></category>
            <category><![CDATA[business-history]]></category>
            <category><![CDATA[technology-trends]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Basat Tayfun]]></dc:creator>
            <pubDate>Thu, 08 Feb 2024 03:32:16 GMT</pubDate>
            <atom:updated>2024-02-08T03:32:16.529Z</atom:updated>
            <content:encoded><![CDATA[<h3>What do the Cloud and Stocks have in common? History says, a lot!</h3><h3>The journey from the in-house datacenter to utility-computing to cloud computing is about to enter a revolutionary phase — cloud providers will not be amused!</h3><p>First, it was utility-computing — also called grid-computing by some. The idea was to automate a datacenter (or any unified IT infrastructure) so as to make it possible to deploy services (applications, systems, etc.) on-demand with rules-based self-scaling (i.e., auto-scaling) with little, if any, human intervention — while keeping unused hardware powered off (or at least in low-power mode). In the early 2000s this was a novel idea — even revolutionary, if not disruptive. Private and public organizations resisted it like the plague. It required an entirely new way of thinking. A completely software-defined and -operated data center sounded great. But, it also scared the living daylights out of practically everyone — from system admins who feared becoming obsolete, irrelevant or redundant; to COOs and CTOs that feared an operational melt-down; to CEOs, CFOs and corporate lawyers that feared regulatory and legal risks of having systems that were here, there, nowhere and anywhere at any given time. Just how do you demonstrate to the FDA or FBI that the data (a DB or log file) that was on this server yesterday, is now on that server today, and will almost be certainly on another server tomorrow… is intact and will remain as such!</p><p>But this resistance eventually gave way. I guess the shift came with virtualization. I think it is fair to say VMware deserves the most credit in selling the idea of separating the HW from the SW (and data). Once that idea took hold and IT pros and CxOs feared less and less the abstraction of HW and the independence it brought to the application stack and data storage/access, it was only a matter of time until economies of scale, freedom from up-front costs (CapEx), 100% flexible operational costs (variable OpEx), and never-before-imagined flexibility (instantaneous deployment, scale up/down, rollout/rollbacks, etc.) would crash the virtualization party!</p><p>Today, cloud is familiar, easy, proven, mature and almost standardized (in terms of general offerings and features). An entire ecosystem of services, HW and SW that leverage cloud platforms’ APIs are multiplying by the day, vying for corporate IT budget Dollars with new value-add propositions. What used to be IaaS is now SaaS, SaS, XaS, YaS… Everything is a service — cloud-hosted and cloud-priced service. And it is the new normal.</p><p>But, the arc of data center history is not complete. For it to reach the end of its history, it must complete the next stage in its life cycle: operations that run seamlessly across different cloud providers. The cloud must now become what were once the HW and OS stacks — completely abstracted and commoditized. Today it is Storage-as-a-Service (SaS) or Compute resources (VMs) from cloud provider X. Tomorrow it should be just SaS and VM — no “X”. A company should be able to pick and chose — on the fly — and based strictly on SLA, performance criteria and pricing which X, Y, or Z provider to use that moment. A spot market of cloud resources is next. And a spot market needs its own common language and rules so IT budgets can float from one provider to the next without a second thought. Much like how US Dollars flow from one equity to another in Wall Street — based on trading that is automated or manual. This is where multi cloud comes in. That is where we are.</p><p>Enjoy the ride everyone. Well, not everyone. Cloud providers will most likely not like what comes next… Oh, well. We cannot please everyone. And the customer is always right, right?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4028b7e84af1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>