<?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 La&#39;Dale Thomas on Medium]]></title>
        <description><![CDATA[Stories by La&#39;Dale Thomas on Medium]]></description>
        <link>https://medium.com/@thomas.ladale?source=rss-37fce4328c82------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*jNL0KQCv6-1DquTH</url>
            <title>Stories by La&amp;#39;Dale Thomas on Medium</title>
            <link>https://medium.com/@thomas.ladale?source=rss-37fce4328c82------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:22:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thomas.ladale/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[5&6 Week From Console Clicks to Infrastructure as Code: My Journey Through AWS Fundamentals]]></title>
            <link>https://medium.com/@thomas.ladale/5-6-week-from-console-clicks-to-infrastructure-as-code-my-journey-through-aws-fundamentals-ed5ad4f580f1?source=rss-37fce4328c82------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed5ad4f580f1</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloudformation]]></category>
            <dc:creator><![CDATA[La'Dale Thomas]]></dc:creator>
            <pubDate>Sat, 26 Jul 2025 17:11:08 GMT</pubDate>
            <atom:updated>2025-07-26T17:11:08.066Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xcZi0Rcm9K721okDuYQygA.jpeg" /></figure><p>It’s been a minute since I first opened up that AWS Fundamentals course. I won’t lie — this journey has had its share of highs and lows. Between the long workdays, building side projects, and real life happening in between, completing this segment took time, patience, and a lot of trial and error. But here’s the truth: it was worth every second.</p><p>This wasn’t just another course. This was a shift in mindset — from clicking around in the AWS console to truly understanding how cloud infrastructure works under the hood. And more importantly, how to <strong>build it from scratch using code</strong>.</p><p>🌍<strong> Laying the Foundation: VPCs, IAM, and Subnets</strong></p><p>One of the biggest takeaways early on was learning how to design and deploy a Virtual Private Cloud (VPC) from the ground up. I had to think like a real architect:</p><ul><li>Should this subnet be public or private?</li><li>Where do I place my Bastion Host?</li><li>How do I control traffic using route tables and security groups?</li></ul><p>For someone who never came from a traditional computer science background, that was a curveball. But diagramming out the architecture, building it manually in the console, and then replicating it in <strong>CloudFormation</strong> started to paint the bigger picture.</p><p>⚙️<strong> The Beast: CloudFormation</strong></p><p>CloudFormation was easily the <strong>toughest part of the segment</strong> — and the most rewarding.</p><p>At first, I avoided it. QuickOps and the AWS console felt safer, more visual, less error-prone. But if you want to become a real cloud engineer, you have to get uncomfortable. That meant jumping into <strong>VS Code</strong>, writing YAML by hand, and deploying full stacks using templates.</p><p>From S3 buckets to IAM users, to fully built-out VPCs — I started piecing together the logic. The structure. The why behind the architecture.</p><p>The hardest part? Debugging syntax errors when a stack fails and you don’t immediately know why. But the moment it works? That’s when it clicks.</p><p>🧠<strong> What Helped Me Push Through</strong></p><ul><li><strong>ChatGPT &amp; Cloudy AI</strong>: Huge help when breaking down YAML structure or troubleshooting why a resource didn’t launch correctly.</li><li><strong>AWS Documentation</strong>: Especially for IAM and networking. It’s not always the most exciting read, but it’s gold when you need clarity.</li><li><strong>Community Support</strong>: Talking with people in tech spaces who get it, asking questions, even watching how others structure their stacks — that kept me moving forward.</li></ul><p>📦<strong> Beyond Code: What I Really Learned</strong></p><p>This journey wasn’t just about AWS. It was about persistence, curiosity, and developing a new muscle — one where I <strong>don’t just use the cloud</strong>, but <strong>build on it</strong>.</p><p>I learned:</p><ul><li>How to structure infrastructure the right way from Day 1</li><li>Why security best practices (IAM roles, least privilege, public vs private subnets) matter early</li><li>How to think in templates, automate, and version control infrastructure with GitHub</li><li>That cloud isn’t about memorizing services — it’s about connecting the dots and building solutions</li></ul><p>🚀<strong> Final Thoughts</strong></p><p>If you’re new to AWS, or even just stuck on CloudFormation like I was — keep going. The breakthrough comes after the confusion. The best way to learn this stuff is to <strong>get hands-on</strong>, fail forward, and <strong>build real infrastructure</strong> until it starts to feel second nature.</p><p>This segment helped me see that cloud engineering isn’t about being perfect — it’s about being resilient, curious, and committed to growth.</p><p>So yeah, it took me a minute. But now I’m stepping into the next level with momentum, confidence, and a stack of real-world skills I didn’t have before.</p><p>Let’s build.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed5ad4f580f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 4 Documentation: Linux and Bash]]></title>
            <link>https://medium.com/@thomas.ladale/week-4-documentation-linux-and-bash-b55a19ffab09?source=rss-37fce4328c82------2</link>
            <guid isPermaLink="false">https://medium.com/p/b55a19ffab09</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[La'Dale Thomas]]></dc:creator>
            <pubDate>Wed, 06 Mar 2024 21:33:34 GMT</pubDate>
            <atom:updated>2024-03-06T21:33:34.291Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*woXmYDXjgdpLHu4x212VNg.png" /></figure><h3>Introduction</h3><p>Week 4 has been an exhilarating journey through the core concepts of Linux and Bash scripting, enhanced by practical applications using Amazon Web Services (AWS), particularly focusing on Elastic Compute Cloud (EC2). This hands-on approach not only made the learning process engaging but also equipped us with essential skills that are directly applicable in real-world scenarios. Below is a breakdown of the lessons covered, key learnings, and personal insights from this week’s adventure.</p><h3>Lessons Overview</h3><h3>1. Intro and EC2 Linux Setup</h3><p>We began our week by diving into the fundamentals of the Linux operating system and Bash shell, contextualized within the AWS EC2 setup. Key activities included:</p><ul><li>Launching an EC2 instance with a Linux distribution.</li><li>Establishing SSH connections to remotely manage the instance.</li><li>Basic EC2 management commands and Linux system exploration.</li></ul><p>This lesson served as the cornerstone for understanding cloud-based Linux environments, emphasizing the importance of remote system administration.</p><h3>2. Navigating the Linux File System</h3><p>Mastering file system navigation is crucial for any Linux user. We explored:</p><ul><li>The structure of the Linux file system hierarchy.</li><li>Commands for listing, changing directories, and identifying the current directory path.</li><li>The distinction between absolute and relative paths.</li></ul><p>This knowledge is fundamental for efficiently moving through the system’s directories and managing files.</p><h3>3. File Operations</h3><p>Building on our navigation skills, we delved into file manipulation, covering:</p><ul><li>File creation, viewing, and editing using various commands.</li><li>Techniques for copying, moving, and deleting files and directories.</li><li>The concept and application of links within the file system.</li></ul><p>Hands-on practice solidified our understanding of these essential operations, a staple in daily Linux use.</p><h3>4. 🚀 Exercise — Creating Files</h3><p>An exercise challenged us to apply our knowledge by:</p><ul><li>Creating and organizing files and directories for a mock project.</li><li>Utilizing text editors to manage file content directly from the command line.</li></ul><p>This practical task reinforced our file operation skills in a simulated real-world scenario.</p><h3>5. Create Access Keys</h3><p>Transitioning to AWS-specific skills, we learned about:</p><ul><li>Generating and managing AWS Access Keys.</li><li>Configuring the AWS CLI with these keys for programmatic access to AWS services.</li></ul><p>The emphasis on security and best practices in access management highlighted the importance of responsible AWS resource handling.</p><h3>6. Create IAM Role and Deploy to S3</h3><p>We advanced our AWS knowledge by focusing on:</p><ul><li>IAM role creation for granular access control.</li><li>Utilizing the AWS CLI to deploy files to S3 buckets.</li></ul><p>Understanding IAM roles and S3 interactions is critical for secure and efficient cloud resource management.</p><h3>7. Changing File Permissions</h3><p>Back to Linux basics, we explored file permissions:</p><ul><li>Viewing and modifying file access rights.</li><li>The implications of different permission settings for users, groups, and others.</li></ul><p>This lesson underscored the security aspect of system administration, stressing the careful control of file access.</p><h3>8. 🚀 Exercise — File Permissions</h3><p>A hands-on exercise furthered our comprehension of permissions by:</p><ul><li>Setting specific permission levels on files and directories.</li><li>Assessing and adjusting permissions to meet security requirements.</li></ul><p>This practical application cemented our understanding of Linux’s permission system, preparing us for real-world security management.</p><h3>9. Shutdown EC2</h3><p>Concluding our week, we focused on:</p><ul><li>Properly shutting down and restarting EC2 instances.</li><li>AWS resource lifecycle management, emphasizing cost-efficiency and data preservation.</li></ul><p>This lesson wrapped up our EC2 exploration, tying together the operational and cost-management aspects of cloud computing.</p><h3>Conclusion</h3><p>Week 4’s immersive experience through Linux, Bash, and AWS EC2 has been both challenging and rewarding. The hands-on approach not only made the learning process more engaging but also ensured that the concepts and skills acquired are deeply ingrained and readily applicable in practical scenarios. As we progress, the foundation laid this week will undoubtedly enhance our proficiency in navigating and managing Linux-based environments, both on-premises and in the cloud.</p><h3>Next Steps</h3><p>Eager to build on the momentum, we look forward to the next module( Aws Fundamentals) , confident in our growing expertise and ready to tackle more complex challenges. Keep going, and great job on completing an impactful week of learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b55a19ffab09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3 — System Design Applications Documentation]]></title>
            <link>https://medium.com/@thomas.ladale/week-3-system-design-applications-documentation-c18de75ba547?source=rss-37fce4328c82------2</link>
            <guid isPermaLink="false">https://medium.com/p/c18de75ba547</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[La'Dale Thomas]]></dc:creator>
            <pubDate>Sun, 03 Mar 2024 15:19:12 GMT</pubDate>
            <atom:updated>2024-03-03T15:20:43.285Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 3 — System Design Applications Documentation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9gOXMeLzQGPpe6nCHMJ3Ag.png" /></figure><p>Week 3 of our course dives deep into the practical aspects of system design, focusing on architectural styles, their applications, and essential components of web architecture. This week is pivotal in understanding how to design, scale, and optimize applications for real-world scenarios. Here’s a breakdown of what we covered:</p><h3>Monolithic Architecture</h3><p>Monolithic architecture refers to a traditional unified model for designing software as a single, indivisible unit. This approach is straightforward, where an application is built, deployed, and scaled as a single entity.</p><ul><li>Advantages: Simplified development and deployment, ease of testing, and straightforward scalability for small applications.</li><li>Disadvantages: Challenges with scalability for large applications, difficulty in adopting new technologies, and longer deployment times.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h10B2GFskzax-d7GzPLkgA.png" /></figure><h3>Microservices Architecture</h3><p>Microservices architecture breaks down a monolithic application into a collection of smaller, interconnected services. Each service is self-contained and implements a specific business functionality.</p><ul><li>Advantages: Improved scalability, flexibility in using different technologies, and easier deployment and updating of individual components.</li><li>Disadvantages: Increased complexity in managing services, data consistency, and inter-service communication.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0kZGQeRkOUFwMC0OQKIjcQ.png" /></figure><h3>Serverless Architecture</h3><p>Serverless architecture abstracts the server management away from the developer, allowing them to focus solely on writing code. Cloud providers dynamically manage the allocation of machine resources.</p><ul><li>Advantages: Cost-efficiency for variable workloads, automatic scaling, and reduced operational responsibilities.</li><li>Disadvantages: Potential for cold starts, limitations in long-running processes, and challenges in local testing.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LG-djy8h4tjI9BTpVchmRQ.png" /></figure><h3>APIs Explained</h3><p>APIs (Application Programming Interfaces) allow different software applications to communicate with each other. They define the methods and data formats that applications use to request and exchange information.</p><h3>Three-Tier Architecture</h3><p>A three-tier architecture is a client-server architecture that includes a presentation layer, an application layer, and a data layer. It separates the UI, business logic, and database, promoting modular design and ease of maintenance.</p><h3>Cloud Storage Options</h3><ul><li>Object Storage: Ideal for storing unstructured data. It’s highly scalable and accessible through APIs.</li><li>Block Storage: Suited for databases or applications requiring high-performance, low-latency storage.</li><li>File Storage: Offers a hierarchical file system, making it suitable for applications and workloads requiring traditional file systems.</li></ul><h3>Caching</h3><p>Caching temporarily stores copies of files or data to reduce access time and improve application performance. It’s essential for enhancing the speed of data retrieval.</p><h3>Load Balancer vs API Gateway</h3><ul><li>Load Balancer: Distributes incoming network traffic across multiple servers to ensure no single server becomes overwhelmed, improving application responsiveness and availability.</li><li>API Gateway: Acts as a reverse proxy, routing requests to the appropriate microservice. It also provides additional functionalities like authentication, rate limiting, and analytics.</li></ul><h3>System Design — YouTube</h3><p>We explored practical system design through YouTube examples, analyzing how to structure applications for scalability, reliability, and performance. Topics included database schema design, video encoding and distribution, and recommendation algorithms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6yF02meudMLFPJpzjlPBig.png" /></figure><h3>Server vs Serverless Scaling</h3><p>The discussion contrasted the scaling capabilities and considerations between server-based and serverless architectures, highlighting the automatic scaling feature of serverless and the manual or semi-automatic scaling strategies for server-based architectures.</p><h3>🚀 Projects</h3><h3>Project 1: Create Your Architecture</h3><p>Design a simple e-commerce application exploring monolithic, microservices, and serverless architectures. This project aims to understand the trade-offs and decision-making processes in architectural design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xlf93_5bBMhgTceHXs_EVA.png" /></figure><h3>Project 2: Design Scalable Architecture</h3><p>Develop an architecture for a scalable web application, focusing on microservices and serverless components to ensure flexibility and scalability.</p><h3>Project 3: Video Sharing Platform</h3><p>Design a simplified version of a video-sharing platform, emphasizing scalable video storage, efficient content delivery, and a robust recommendation engine.</p><p>Week 3 has been instrumental in building a solid foundation in system design, equipping learners with the knowledge and skills to tackle complex design challenges in real-world applications. Looking foward for week 4!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c18de75ba547" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 2 Reflection: My Journey with Git & Cloud Architecture]]></title>
            <link>https://medium.com/@thomas.ladale/week-2-reflection-my-journey-with-git-cloud-architecture-1bc541b73582?source=rss-37fce4328c82------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bc541b73582</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[La'Dale Thomas]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 23:52:31 GMT</pubDate>
            <atom:updated>2024-02-16T23:52:31.007Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Jit-yNh44ed_ADKpS8biA.png" /></figure><h3>Introduction</h3><p>This past week has been an exhilarating deep dive into the world of Git and Cloud Architecture. I’ve navigated through the complexities of version control, explored the vast capabilities of GitHub, and got my hands dirty with AWS CLI, laying down a solid foundation for my future as a software developer and cloud practitioner. Here’s a look back at my journey through Week 2.</p><h3>Mastering Version Control with Git</h3><h3>The Importance of Version Control</h3><p>I started the week realizing the critical role version control plays in software development. It’s not just about tracking changes; it’s about understanding the evolution of a project and fostering collaboration.</p><h3>Getting to Grips with Git</h3><p>Learning Git was like unlocking a new level in my developer skills. The commands, the workflow, and the realization that I could track every change were empowering. It was fascinating to see how Git preserves the integrity of my projects.</p><h3>GitHub: More Than Just a Repository Host</h3><p>GitHub opened my eyes to the social side of coding. It’s not just about storing code; it’s a platform for collaboration, review, and automation. Setting up SSH keys was a minor hurdle, but it enhanced my security and eased my workflow.</p><h3>My First Repository</h3><p>Creating my first repository was a milestone. It symbolized the start of a new project, a blank canvas ready to be filled with code. Learning to navigate the Git workflow felt like learning a new language, but I was quickly becoming fluent.</p><h3>Hands-On Projects: From Theory to Practice</h3><h3>Project: Git</h3><p>Applying what I learned about Git in a project was rewarding. Branching, committing, merging — it all came together in a practical scenario that cemented my understanding and confidence.</p><h3>Project: AWS CLI Installation</h3><p>Installing the AWS CLI was my first step into the vast world of cloud computing. The command-line interface was a powerful tool, connecting me directly to AWS services.</p><h3>Exploring the Cloud</h3><h3>Cloud Architecture Basics</h3><p>Understanding cloud architecture was like peering behind the curtain of the internet. The concepts of front-end and back-end, coupled with the strategies for scaling, were enlightening.</p><h3>The Significance of Load Balancing and High Availability</h3><p>Learning about load balancing and high availability transformed my understanding of web applications. The intricacies of ensuring performance and reliability were complex but fascinating.</p><h3>AWS CLI Projects: A Practical Approach</h3><h3>Managing S3 Buckets</h3><p>Using the AWS CLI to manage S3 buckets was a hands-on introduction to cloud storage. It was a practical exercise that showed me the power of cloud resources.</p><h3>IAM User Management</h3><p>Creating and managing IAM users taught me the importance of security and access control in the cloud. It was a critical lesson in responsible cloud resource management.</p><h3>Designing Basic Cloud Architecture</h3><p>Designing a basic cloud architecture was the culmination of my learning this week. It allowed me to apply my knowledge in a creative and practical manner, designing a system that was both scalable and reliable.</p><h3>Conclusion</h3><p>Reflecting on Week 2, I’m amazed at how much I’ve learned and grown. Git and cloud architecture are no longer just buzzwords; they are tools in my arsenal, skills in my resume, and stepping stones in my journey. As I look forward to Week 3, I’m eager to continue building on this foundation, exploring new technologies, and facing new challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bc541b73582" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Summary of Cloud Infrastructure Architecture for a Web Application]]></title>
            <link>https://medium.com/@thomas.ladale/summary-of-cloud-infrastructure-architecture-for-a-web-application-16ce7d77a67e?source=rss-37fce4328c82------2</link>
            <guid isPermaLink="false">https://medium.com/p/16ce7d77a67e</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[La'Dale Thomas]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 20:30:47 GMT</pubDate>
            <atom:updated>2024-02-16T20:32:16.281Z</atom:updated>
            <content:encoded><![CDATA[<p>The proposed architecture for the web application is designed to ensure scalability, reliability, and performance. Here’s a breakdown of each component and the rationale behind the architectural decisions:</p><p>Components and Their Purposes</p><ul><li><strong>Load Balancer</strong>: Serves as the entry point for all incoming internet traffic, distributing requests evenly across multiple front-end servers to ensure no single server becomes a bottleneck, enhancing the application’s availability and response time.</li><li><strong>Front-end Servers</strong>: Host the user interface of the web application. These servers deliver static content such as HTML, CSS, and client-side JavaScript to the user’s browser, facilitating a fast and responsive user experience.</li><li><strong>Back-end Servers</strong>: Handle the application’s logic, including processing user requests, executing business rules, and communicating with the database. These servers are responsible for dynamic content generation based on user interactions.</li><li><strong>Database</strong>: Stores all persistent data required by the web application, such as user profiles, transaction records, and application state. It ensures data consistency, integrity, and availability for read/write operations initiated by the back-end servers.</li></ul><p>Architectural Decisions</p><ul><li><strong>Horizontal Scaling of Load Balancer and Servers</strong>: The choice to scale the load balancer and both front-end and back-end servers horizontally (adding more instances) rather than vertically (upgrading existing instances) is driven by the need for flexibility and resilience. Horizontal scaling allows the system to handle increased load by distributing traffic among multiple instances, improving fault tolerance through redundancy and enabling seamless capacity adjustments based on demand.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*DpHtrq7V-yla0s-5jh4Sow.png" /></figure><ul><li><strong>Vertical Scaling of the Database Initially</strong>: Starting with vertical scaling for the database (enhancing the capabilities of a single instance) simplifies initial setup and maintenance while providing a cost-effective solution for early stages. This approach is chosen for its ease of management and immediate performance benefits. However, planning for future horizontal scaling (sharding or partitioning) is essential to accommodate significant growth in data volume and access rates, ensuring long-term scalability.</li><li><strong>Load Balancer at the Front</strong>: Placing a load balancer at the front of the architecture ensures that no single front-end server becomes overwhelmed with requests, which could lead to performance degradation or outages. This design enhances the overall reliability and availability of the web application, ensuring users receive consistent and timely responses.</li><li><strong>Separation of Concerns between Front-end and Back-end</strong>: Separating front-end and back-end servers aligns with the principle of separation of concerns, allowing independent scaling, updates, and maintenance of user interface components and application logic. This separation enables more efficient development and deployment cycles and allows for specialized resources that best fit the needs of each layer (e.g., compute-optimized for back-end, memory-optimized for front-end).</li></ul><p><strong>Conclusion</strong></p><p>The architecture is designed to provide a scalable, reliable foundation for the web application, capable of adapting to varying loads and ensuring a seamless user experience. The strategic decision to employ horizontal scaling for most components, alongside a phased approach to database scaling, balances immediate performance needs with long-term growth potential. This architecture supports the application’s objectives while providing flexibility to evolve as requirements and technologies change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16ce7d77a67e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 1 Documentation: Cloud Fundamentals]]></title>
            <link>https://medium.com/@thomas.ladale/week-1-documentation-cloud-fundamentals-30dde76fa8f9?source=rss-37fce4328c82------2</link>
            <guid isPermaLink="false">https://medium.com/p/30dde76fa8f9</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[La'Dale Thomas]]></dc:creator>
            <pubDate>Mon, 12 Feb 2024 00:33:11 GMT</pubDate>
            <atom:updated>2024-02-12T00:33:11.839Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*a_5qq5wU4u1kLX1syWE2Bw.gif" /></figure><p>My journey into cloud computing began with an exploration of its core concept, clearly outlined in the initial sessions. The blend of detailed video tutorials and step-by-step project guides made complex topics accessible and engaging.</p><p><strong>What is Cloud Computing?</strong></p><p>Cloud computing is the delivery of computing services over the internet. Its benefits include cost savings, scalability, and accessibility, which were vividly explained through practical examples and real-world applications.</p><p><strong>Cloud Deployment Models</strong></p><p>We delved into public, private, and hybrid models, understanding their unique advantages and scenarios of use. This foundation was crucial for grasping the flexibility and variety within cloud computing.</p><p><strong>Software Delivery Lifecycle (SDLC)</strong></p><p>The SDLC in a cloud environment was a revelation. Learning about its phases helped me appreciate the streamlined process of software development facilitated by cloud technologies.</p><p><strong>Labs and Projects</strong></p><ul><li><strong>Creating an AWS Account:</strong> This lab was my first hands-on introduction to AWS, emphasizing the importance of security and budget management.</li><li><strong>Networking Projects:</strong> The Curl Requests, Trace Routes, and Ping Requests projects demystified the basics of networking, enhancing my practical skills.</li></ul><p><strong>Theoretical Foundations</strong></p><p>Discussions on how the internet works, virtualization, and networking provided a solid technical foundation, making the practical labs more understandable.</p><p><strong>Operating Systems and Databases</strong></p><p>The course also covered operating systems and databases in the cloud, highlighting their critical roles in cloud infrastructure.</p><p><strong>Reflections</strong></p><p>The methodical breakdown of videos and projects facilitated an effortless understanding of otherwise complex subjects. The practical exercises were not just about following instructions but also understanding the ‘why’ behind each step, which deepened my comprehension of cloud fundamentals.</p><p><strong>Conclusion</strong></p><p>Week 1 was a comprehensive introduction to cloud computing, blending theoretical knowledge with practical skills. The thoughtful organization of content, from foundational concepts to hands-on projects, laid a solid groundwork for my cloud computing journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30dde76fa8f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>