<?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 Jimmy Rema on Medium]]></title>
        <description><![CDATA[Stories by Jimmy Rema on Medium]]></description>
        <link>https://medium.com/@jimmyrema77?source=rss-bdc8fef9499a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*NtswShmKzIecJqz7</url>
            <title>Stories by Jimmy Rema on Medium</title>
            <link>https://medium.com/@jimmyrema77?source=rss-bdc8fef9499a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:38:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jimmyrema77/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[Week 5&6 — Crafting a Secure AWS VPC Architecture: A Comprehensive Guide]]></title>
            <link>https://medium.com/@jimmyrema77/week-5-6-crafting-a-secure-aws-vpc-architecture-a-comprehensive-guide-ecb7ddc40563?source=rss-bdc8fef9499a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecb7ddc40563</guid>
            <category><![CDATA[aws-vpc]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Jimmy Rema]]></dc:creator>
            <pubDate>Wed, 05 Jun 2024 00:55:40 GMT</pubDate>
            <atom:updated>2024-06-05T00:55:40.280Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 5&amp;6 — Crafting a Secure AWS VPC Architecture: A Comprehensive Guide</h3><p>In the ever-evolving landscape of cloud computing, establishing a secure and robust Virtual Private Cloud (VPC) architecture is paramount for organizations aiming to leverage the benefits of AWS infrastructure. Weeks 5 and 6 of our journey we started to delve deep into the intricacies of designing and implementing such a secure AWS VPC architecture.</p><p>At the core of our exploration were the fundamental components of <strong>AWS VPC</strong>, including <strong>public </strong>and <strong>private subnets</strong>, <strong>CIDR Blocks</strong>, <strong>route tables</strong>, <strong>security groups</strong>, and <strong>Network Access Control Lists (NACLs)</strong>. These elements serve as the building blocks for constructing a VPC environment that ensures high availability, scalability, and, most importantly, security.</p><p><strong>Subnets</strong>, or <strong>subnetworks</strong>, play a pivotal role in segmenting and organizing cloud resources based on varying levels of access and security requirements. Public subnets facilitate direct internet access to resources within them, typically through an internet gateway, while private subnets restrict internet access, allowing communication only among resources within the subnet or with resources in public subnets via a Network Address Translation (NAT) gateway.</p><p>The <strong>Amazon VPC</strong> itself acts as a logically isolated private network within the AWS cloud environment, providing both security and connectivity features. <strong>CIDR Blocks</strong> define the IP address range assigned to the VPC, setting the numerical parameters for resource allocation. <strong>Route tables</strong> guide data packets within the VPC, directing them either internally or externally to the internet or other destinations.</p><p>Security within an AWS VPC is enforced through <strong>security groups</strong> and <strong>NACLs</strong>. <strong>Security groups</strong> define rules governing inbound and outbound traffic, specifying details such as IP addresses, protocols, and port numbers. Notably, security groups are stateful, meaning they remember visitors upon re-entry, streamlining access permissions. On the other hand, <strong>NACLs</strong> act as stateless security checkpoints, scrutinizing every data packet against a set of rules to determine whether it should be allowed through.</p><p>Understanding these components is crucial for ensuring the reliability, security, and connectivity of your AWS VPC architecture. By leveraging the capabilities of AWS services and adhering to best practices in VPC design, organizations can create a resilient infrastructure that meets their operational needs while mitigating security risks.</p><p>In summary, designing and implementing secure VPC architectures requires a comprehensive understanding of the underlying components and their unique roles. Across various cloud platforms, including AWS, GCP, and Azure, security and connectivity remain foundational principles. As we continue to navigate the dynamic landscape of cloud computing, collaboration and knowledge-sharing with peers enable us to enhance security, troubleshoot connectivity issues, and ultimately deliver reliable, protected, and accessible services to businesses worldwide.</p><h3>Securing Connectivity in Cloud Architecture</h3><h3>A simple aws vpc architecture diagram:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o8oeVDLXcqpzi0iC.png" /></figure><h3>A Deep Dive:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CqRQ7jk2kLSjnWom.png" /></figure><p>CLOUD ARCHITECT DESIGN TO DEMONSTRATE SECURITY AND CONNECTIVITY</p><p>At the forefront of our architecture stands the internet gateway, the gateway to our cloud environment. Here, requests and data packets embark on their journey, flowing towards the Network Access Control Lists (NACLs) server nestled within the public subnet of availability zone 1A. This strategic placement ensures efficient traffic management and minimizes the risk of delays or bottlenecks.</p><p>The NACLs server acts as a vigilant gatekeeper, scrutinizing incoming requests and data packets before granting them access. Once verified, these requests continue their journey, passing through the security group guarding the EC2 instances housed within the private subnet. Here lies a crucial layer of defense, shielding our sensitive data and backend logic from unauthorized access.</p><p>Importantly, the private subnet boasts no direct connection to the internet gateway, fortifying our defenses against external threats. This architectural choice enhances the security posture of our infrastructure, creating a secure enclave for handling sensitive data and backend operations.</p><p>Upon reaching the EC2 instances, the requested data is retrieved, and here’s where the magic of stateful security groups comes into play. Unlike their stateless counterparts, stateful security groups remember previous interactions, obviating the need for repeated permissions for inbound and outbound traffic. This seamless flow of data within the private subnet ensures efficiency without compromising security.</p><p>However, as the data prepares to make its journey back to the user, it encounters the stateless nature of the NACLs server once again. Here, every outgoing data packet is rigorously verified before being dispatched, adding an extra layer of security to our outbound traffic.</p><p>This intricate dance of security measures within our cloud architecture is orchestrated to perfection. The NACLs server acts as a robust barrier, shielding our sensitive backend resources from external threats, while the stateful security groups facilitate seamless communication within the private subnet.</p><h3><strong>Conclusion</strong></h3><p>The design of our cloud architecture exemplifies the symbiotic relationship between security and connectivity. By strategically implementing layers of defense, from NACLs to security groups, we create a resilient environment capable of safeguarding data and maintaining optimal performance. As we continue to evolve and refine our cloud architecture, security and connectivity will remain paramount, ensuring the integrity and reliability of our cloud services.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecb7ddc40563" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3 — Part 2— Cloud Engineer Journey — Project: Designing a version of a video-sharing platform]]></title>
            <link>https://medium.com/@jimmyrema77/week-3-part-2-cloud-engineer-journey-project-designing-a-version-of-a-video-sharing-platform-e48c493d7eb1?source=rss-bdc8fef9499a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e48c493d7eb1</guid>
            <dc:creator><![CDATA[Jimmy Rema]]></dc:creator>
            <pubDate>Fri, 17 May 2024 17:54:30 GMT</pubDate>
            <atom:updated>2024-05-17T17:54:30.804Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 3 — Part 2— Cloud Engineer Journey — Project: Designing a version of a video-sharing platform</h3><p>This diagram below is a design for a simplified version of a video-sharing platform, that should allow users to upload videos, store video metadata, process videos into multiple resolutions, analyze content for appropriateness, and serve videos to users with minimal latency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B06wAPzX97pBTCc_.png" /></figure><p><strong>High level overview of the design above:</strong></p><p><strong>Video Uploading and Storage: </strong>Users should be able to upload videos in various formats and sizes, stored in object storage (simulated using Amazon S3)</p><p><strong>Metadata Handling: </strong>Here, DynamoDB is the choice to store video metadata. It is a great choice as it uses a flexible, document-like format to store data.</p><p><strong>Video Processing: </strong>The platform should support various video formats and resolutions. To accommodate this, a video encoding and transcoding component is necessary to convert uploaded videos into multiple formats suitable for streaming across different devices and network conditions. In regards to serverless functions for video processing, Serverless functions can be triggered by events such as new video uploads, making them ideal for real-time processing workflows. For instance, uploading a video to a storage service can automatically trigger a function to start processing.</p><p><strong>Content Analysis: </strong>Automated content analysis to flag inappropriate videos can be effectively implemented using a combination of serverless architecture, machine learning, and cloud-based services. For example, once a video is uploaded to a cloud storage service (e.g., Amazon S3), The upload triggers a serverless function (e.g., AWS Lambda) to initiate the content analysis workflow.</p><p>A serverless function aggregates the analysis results from image recognition, audio analysis, and text detection. It assigns a score based on the severity and frequency of detected inappropriate content.</p><p>Based on the aggregated score, the video is either flagged as inappropriate or marked as safe. Flagged videos are moved to a separate storage bucket, and a report is generated detailing the reasons for flagging.</p><p><strong>Video Delivery: </strong>Designing a content delivery strategy to serve videos with minimal latency to a global audience involves leveraging a Content Delivery Network (CDN) effectively.</p><p>For example, Choose a reliable CDN provider with a robust global network of edge servers (e.g., AWS CloudFront), Ensure the CDN supports advanced features like HTTP/2, TLS, and customizable caching policies. Configuring a CDN to cache video content at edge locations close to end users, reduces the distance data needs to travel and thus minimizing latency.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e48c493d7eb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3 — Part 1 — Cloud Engineer Journey — Designing and Comparing Architectural Styles]]></title>
            <link>https://medium.com/@jimmyrema77/week-3-part-1-cloud-engineer-journey-designing-and-comparing-architectural-styles-1b4bf7e88404?source=rss-bdc8fef9499a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b4bf7e88404</guid>
            <dc:creator><![CDATA[Jimmy Rema]]></dc:creator>
            <pubDate>Fri, 17 May 2024 17:52:56 GMT</pubDate>
            <atom:updated>2024-05-17T17:52:56.037Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 3 — Part 1 — Cloud Engineer Journey — Designing and Comparing Architectural Styles</h3><p><strong>PROJECT#1: Design a simple e-commerce application using monolithic architecture</strong></p><p>A monolithic architecture is a traditional software design approach where all components of an application are combined into a single program, typically deployed as a single executable or a single codebase. In a monolithic architecture, the entire application is built, deployed, and scaled as a single unit.</p><p>Key characteristics of a monolithic architecture include:</p><ol><li><strong>Single Codebase</strong>: All components of the application, including the user interface, business logic, data access layer, and external dependencies, are contained within a single codebase.</li></ol><p>2. <strong>Tightly Coupled Components</strong>: Components within the monolith are tightly integrated and dependent on each other, making it challenging to modify or replace individual components without affecting the entire system.</p><p>3. <strong>Shared Memory and Resources</strong>: Components within the monolith share the same memory space and resources, allowing for efficient communication and data sharing but potentially leading to resource contention and scalability limitations.</p><p>4. <strong>Unified Deployment</strong>: The entire application is deployed as a single unit, typically on a single server or a small cluster of servers. Updates and changes to the application require redeploying the entire monolith.</p><p>5. <strong>Scaling Limitations</strong>: Scaling a monolithic application involves replicating the entire application stack, which can be challenging and costly. Horizontal scaling may be limited by the capacity of individual servers or by the monolith’s architectural constraints.</p><p>6. <strong>Development and Maintenance Challenges</strong>: Large monolithic codebases can become complex and difficult to manage over time, leading to slower development cycles, increased technical debt, and challenges in debugging and testing.</p><p>7. T<strong>echnology Stack Uniformity</strong>: Since all components of the application are built using the same technology stack and programming language, there is uniformity in development practices and tooling across the entire codebase.</p><p>Monolithic architectures were commonly used in the past due to their simplicity and ease of development and deployment. However, they may face challenges in scalability, agility, and resilience as applications grow in complexity and user traffic increases. In recent years, many organizations have adopted alternative architectural styles such as microservices or serverless architectures to address these challenges.</p><p><strong>Here’s a conceptual design for a simple e-commerce application using a monolithic architecture:</strong></p><p>1. Frontend:</p><ul><li>The frontend of the e-commerce application consists of web pages that users interact with to browse products, add items to the cart, and complete purchases.</li><li>Technologies: HTML, CSS, JavaScript, and possibly a frontend framework like React or Angular.</li><li>Functionality: Display product listings, allow users to search and filter products, view product details, add items to cart, and proceed to checkout.</li></ul><p>2. Backend:</p><ul><li>The backend handles the business logic, data processing, and interaction with the database.</li><li>Technologies: Server-side scripting language such as Node.js, Python (Django/Flask), Ruby (Ruby on Rails), or Java (Spring Boot).</li><li>Functionality: Process user requests, handle user authentication and authorization, manage product inventory, process orders, and interact with external services such as payment gateways.</li></ul><p>3. Database:</p><ul><li>The database stores information about products, users, orders, and other relevant data.</li><li>Technologies: Relational database management system (RDBMS) like MySQL, PostgreSQL, or SQLite.</li><li>Schema:</li><li>Products table: Stores product details such as ID, name, description, price, quantity, etc.</li><li>Users table: Stores user information such as ID, username, password (hashed), email, shipping address, etc.</li><li>Orders table: Stores order details such as ID, user ID (foreign key), product ID (foreign key), quantity, total price, status, etc.</li></ul><p>4. Payment Gateway Integration:</p><ul><li>Integrates with a third-party payment gateway to process payments securely.</li><li>Technologies: Payment gateway APIs provided by services like PayPal, Stripe, or Square.</li><li>Functionality: Allow users to make payments using credit/debit cards, digital wallets, or other payment methods, and handle payment processing securely.</li></ul><p>5. Authentication and Authorization:</p><ul><li>Implements user authentication and authorization to ensure secure access to user accounts and sensitive operations.</li><li>Technologies: JSON Web Tokens (JWT), session cookies, or OAuth/OpenID Connect for authentication.</li><li>Functionality: Authenticate users during login/signup, generate and validate access tokens, enforce access control rules based on user roles and permissions.</li></ul><p>6. Order Processing:</p><ul><li>Manages the lifecycle of orders, from creation to fulfillment.</li><li>Functionality: Create new orders, update order status (e.g., pending, processing, shipped), handle order cancellations and returns, generate order invoices and shipping labels.</li></ul><p>7. Administration Panel:</p><ul><li>Provides an administrative interface for managing products, orders, and users.</li><li>Functionality: CRUD operations for products, users, and orders, view sales reports and analytics, manage inventory, and perform other administrative tasks.</li></ul><p>8. Logging and Monitoring:</p><ul><li>Implements logging and monitoring to track application behavior, detect errors, and ensure system health.</li><li>Technologies: Logging frameworks like Winston or Bunyan, monitoring tools like Prometheus or Grafana.</li><li>Functionality: Log application events, errors, and performance metrics, monitor system resources, and receive alerts for abnormal behavior or performance issues.</li></ul><p>9. Deployment:</p><ul><li>Deploys the application on a server or cloud platform.</li><li>Technologies: Virtual private servers (VPS), containerization with Docker, cloud platforms like AWS, Azure, or Google Cloud.</li><li>Functionality: Deploy application components, configure scaling policies, monitor resource utilization, and ensure high availability and reliability.</li></ul><p>This monolithic architecture simplifies development and deployment by consolidating all application components into a single codebase and deployment unit. However, it may face scalability challenges as the application grows in complexity and user traffic increases.</p><p><strong>Example of an E-commerce application using monolithic architecture illustrated below:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9mq7JoqO85eOJwubaufTvA.jpeg" /></figure><p>In this example, the client browser (represented as browser and device agnostic here) accesses the application, which displays the UI to interact with the product catalog and completes the order through communication with one or more databases shared by the entire monolithic application.</p><p><strong>PROJECT#2: Breaking down the monolithic design into microservices:</strong></p><p>Microservice architecture is an architectural style that structures an application as a collection of small, autonomous services modeled around a business domain. Each microservice is a discrete piece of functionality that can be developed, deployed, and scaled independently. These services typically communicate over a network, often using HTTP or messaging queues, and work together to fulfill the overall business objectives of the application.</p><p>Key characteristics of microservice architecture include:</p><ol><li><strong>Independent Deployment</strong>: Each microservice can be deployed independently without affecting the rest of the system, allowing for more flexible and frequent updates.</li></ol><p><strong>2. Decentralized Data Management</strong>: Microservices often manage their own databases, which helps to encapsulate the data and reduce coupling between services.</p><p><strong>3. Business-Centric</strong>: Services are designed around business capabilities and processes rather than technical concerns, promoting better alignment with business goals.</p><p><strong>4. Resilience and Fault Isolation</strong>: Failure in one microservice does not necessarily lead to the failure of the entire system. This isolation can enhance the overall resilience of the application.</p><p><strong>5. Scalability</strong>: Individual microservices can be scaled independently to meet demand, making it easier to handle varying loads on different parts of the application.</p><p><strong>6. Polyglot Programming</strong>: Different services can be built using different programming languages and technologies, allowing teams to choose the best tool for each job.</p><p><strong>7. Continuous Delivery</strong>: The independence of microservices supports continuous integration and continuous deployment (CI/CD) practices, enabling faster delivery of new features and updates.</p><p>Microservice architecture is well-suited for complex, large-scale applications that require high agility, scalability, and maintainability. However, it also introduces complexity in terms of service orchestration, inter-service communication, data consistency, and operational overhead, requiring robust DevOps practices and tools for effective management.</p><p><strong>Example of an E-commerce application using microservices architecture illustrated below:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZryMqA7Xi50KWqnoEAHejA.jpeg" /></figure><p>In comparison to a monolith, a microservices-based architecture uses independent e-commerce applications to handle each unique business function. These microservices communicate via <a href="https://fabric.inc/blog/ecommerce-apis/">e-commerce APIs</a> to support a flexible and scalable e-commerce architecture.</p><p>With microservices, there’s no single codebase or database to contend with. Each microservice is its own application with its own database. This lets brands change, modify, and scale each microservice without impacting the overall architecture</p><p><strong>PROJECT#3: Incorporating Serverless Architecture</strong></p><p>Serverless architecture is a cloud computing execution model where the cloud provider dynamically manages the allocation and provisioning of servers. In a serverless setup, developers write code without having to worry about the underlying infrastructure, as the cloud provider automatically handles the scaling, management, and maintenance of the servers.</p><p>Key characteristics of serverless architecture include:</p><ol><li><strong>Event-Driven Execution</strong>: Functions (units of code) are triggered by events such as HTTP requests, database changes, or other service-specific events. This allows for responsive and real-time processing.</li><li><strong>No Server Management</strong>: Developers do not need to provision, scale, or manage any servers. All infrastructure concerns are abstracted away by the cloud provider.</li><li><strong>Automatic Scaling</strong>: Serverless applications automatically scale up and down based on the number of incoming requests. This ensures that applications can handle variable loads without manual intervention.</li><li><strong>Cost Efficiency</strong>: Billing is based on actual usage rather than pre-allocated capacity. This means you only pay for the compute time consumed by your code, typically measured in milliseconds.</li><li><strong>Rapid Deployment</strong>: Without the need to manage infrastructure, developers can deploy code quickly and focus more on writing code rather than managing servers.</li><li><strong>Micro-billing</strong>: Since billing is based on precise usage, it is often more granular and can lead to cost savings, especially for applications with intermittent or unpredictable workloads.</li><li><strong>Stateless Functions</strong>: Serverless functions are generally stateless, meaning they do not retain information between invocations. Any necessary state must be stored externally, typically in a database or another storage service.</li></ol><p>Serverless architecture is ideal for applications with unpredictable or intermittent workloads, real-time data processing, and rapid development cycles. It simplifies operations and can reduce costs, but it also requires careful consideration of function cold starts, statelessness, and possible vendor lock-in.</p><p><strong>Example of a Serverless E-commerce application illustrated below:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nudQZ_GKsMAzeNeY.png" /></figure><p><strong>Conclusion:</strong></p><p>Choosing between monolithic, microservices, and serverless architectures depends on various factors, including the project’s scale, complexity, team expertise, and specific requirements.</p><ul><li><strong>Monolithic</strong> is suitable for small teams or projects with straightforward requirements.</li><li><strong>Microservices</strong> is ideal for large, complex applications requiring high scalability and flexibility, with experienced teams.</li><li><strong>Serverless</strong> fits projects needing rapid deployment, automatic scaling, and cost efficiency, especially for variable workloads.</li></ul><p>Evaluate your specific needs, team capabilities, and project goals to choose the most appropriate architecture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b4bf7e88404" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Engineering Journey | Week 2 Git & Cloud Architecture]]></title>
            <link>https://medium.com/@jimmyrema77/cloud-engineering-journey-week-2-git-cloud-architecture-dea6f829d0fd?source=rss-bdc8fef9499a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dea6f829d0fd</guid>
            <dc:creator><![CDATA[Jimmy Rema]]></dc:creator>
            <pubDate>Wed, 15 May 2024 16:57:59 GMT</pubDate>
            <atom:updated>2024-05-15T16:57:59.160Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to week two of my Cloud Journey! Being from a QA background, I am familiar with Git commands and Github as a version control. This week, I went over how to Enable SSH Access to GitHub, Create a Github repository through CLI, Creating new branches through CLI , committing changes to a branch, pushing changes to the remote branch, creating a pull request in GitHub, pulling to update local repository.</p><p>I also learned how to install AWS CLI and use AWS CLI to create and upload a file to an S3 Bucket. I also learn how to create a new IAM User and attach a policy to the new IAM user using AWS CLI.</p><p>I also covered cloud architecture, System Design Principles, Front End vs Back End, Vertical vs Horizontal Scaling, Load Balancing, High Availability, Fault Tolerance and last but not least, I developed a conceptual design for a cloud infrastructure supporting a web application.</p><h3>Intro to Version Control</h3><p>Version control, also known as source control or revision control, is a system that records changes to files over time, allowing multiple contributors to collaborate on a project simultaneously. It tracks modifications made to files, stores different versions of the project’s codebase, and facilitates collaboration by managing conflicts and enabling the merging of changes.</p><p><strong>Key features of version control include:</strong></p><ol><li>History Tracking: Version control systems (VCS) maintain a chronological record of changes made to files, including who made the changes and when they were made.</li></ol><p>2. Branching and Merging: VCS allows developers to create branches to work on new features or bug fixes independently of the main codebase. Changes made in branches can be merged back into the main codebase seamlessly.</p><p>3. Collaboration: Version control enables multiple developers to work on the same project concurrently by providing mechanisms for code sharing, conflict resolution, and communication</p><p>4. Revert and Rollback: It allows developers to revert to previous versions of files or the entire project, facilitating error correction and troubleshooting</p><p>5. Documentation: Each change made to the codebase is accompanied by a descriptive message, serving as documentation for understanding the purpose and context of the modifications.</p><p>Version control systems are essential tools in software development, enabling teams to manage code effectively, maintain project history, and ensure the integrity and reliability of software products. Examples of popular version control systems include Git, Subversion (SVN), Mercurial, and Perforce.</p><p><strong>Understanding Git Concepts:</strong></p><ul><li>Repository: The central storage site that holds all versions of files, their history, and associated information.</li><li>Commit: A snapshot of files at a particular time, along with a descriptive message explaining the changes.</li><li>Branch: An independent line of development that allows for parallel work on features or fixes.</li></ul><p><strong>Types of Version Control Systems:</strong></p><ul><li>Local VCS: Managed on a user’s local machine, lacking collaboration capabilities.</li><li>Centralized VCS (CVCS): Involves a central server for storing versioned files, enabling collaboration among team members.</li><li>Distributed VCS (DVCS): Each user has a complete copy of the repository, promoting better collaboration and redundancy.</li></ul><p><strong>Introduction to Cloud Architecture</strong></p><p>Cloud architecture provides a fundamental blueprint for integrating cloud components to achieve scalability, security, reliability, performance, and cost-effectiveness. Here’s what I explored:</p><p><strong>Key Components:</strong></p><ul><li>Frontend Development: Focuses on building user interfaces and experiences using technologies like HTML, CSS, and JavaScript.</li><li>Backend Development: Manages server-side logic, database interactions, and business logic supporting the application.</li><li>Cloud-Based Deployment models: Leverages services like SaaS, IaaS, and PaaS for scalable and flexible delivery of applications.</li><li>Network Development: Ensures seamless communication between frontend and backend platforms over the internet.</li></ul><p><strong>Cloud Architecture Layers:</strong></p><ul><li>Hardware Layer: Consists of physical servers, storage solutions, and networking equipment forming the backbone of cloud services.</li><li>Application and Service Layer: Provides cloud-based applications and services directly accessible to end-users.</li><li>Virtualization Layer: Abstracts physical hardware to create virtual machines, optimizing resource utilization and scalability.</li></ul><p><strong>Scaling Needs: Vertical vs. Horizontal Scaling</strong></p><ul><li>Vertical Scaling (Scaling Up): Vertical scaling, also known as scaling up or scaling vertically, refers to the process of increasing the capacity of a single server or resource to handle additional workload or traffic. In vertical scaling, resources such as CPU, memory, or storage are upgraded or added to a single server to improve its performance and capacity.</li></ul><p><strong>Key characteristics of vertical scaling include:</strong></p><ol><li>Increasing Resource Capacity: Vertical scaling involves adding more resources, such as upgrading the CPU, adding more memory (RAM), or expanding storage capacity, to a single server.</li></ol><p>2. Enhancing Performance: By increasing the resources available to a single server, vertical scaling aims to improve its processing power, memory allocation, and storage capacity, thereby enhancing overall performance and throughput.</p><p>3. Single Point of Failure: Since vertical scaling relies on a single server or resource, it may introduce a single point of failure. If the server fails, the entire application or service may become unavailable until the issue is resolved.</p><p>4. Limited Scalability: Vertical scaling has inherent limitations in terms of scalability. There is a maximum threshold to which resources can be upgraded or added to a single server, beyond which further scaling becomes impractical or cost-prohibitive.</p><p>Vertical scaling is commonly used in environments where the workload or traffic is predictable and can be accommodated by a single, powerful server. It is suitable for applications with moderate to high resource requirements but may not be suitable for highly distributed or rapidly growing systems where horizontal scaling is preferred.</p><ul><li>Horizontal Scaling (Scaling Out): Horizontal scaling, also known as scaling out, refers to the process of adding more machines or instances to a system to distribute the workload across multiple servers. In horizontal scaling, additional resources are added in parallel to handle increased traffic or workload, rather than upgrading a single server vertically.</li></ul><p><strong>Key characteristics of horizontal scaling include:</strong></p><ol><li>Adding More Servers: Horizontal scaling involves adding more servers or instances to a system to increase its capacity. Each new server operates independently and shares the workload, allowing the system to handle higher levels of traffic or workload.</li></ol><p>2. Improved Scalability: Horizontal scaling offers improved scalability compared to vertical scaling, as it allows for unlimited expansion by adding more servers as needed. This makes it well-suited for environments with unpredictable or rapidly growing workloads.</p><p>3. Redundancy and Fault Tolerance: Horizontal scaling improves fault tolerance and redundancy by distributing workload across multiple servers. If one server fails, the remaining servers can continue to handle the workload, reducing the risk of downtime or service interruptions.</p><p>4. Load Balancing: To ensure even distribution of traffic across multiple servers, horizontal scaling typically employs load balancing techniques. Load balancers distribute incoming requests among available servers based on factors such as server capacity, response time, or traffic patterns.</p><p>5. Complexity: Horizontal scaling may introduce complexity in managing and coordinating multiple servers, especially in distributed environments. However, modern cloud platforms and orchestration tools provide automation and management capabilities to streamline horizontal scaling operations.</p><p>Horizontal scaling is commonly used in cloud computing environments and distributed systems, where scalability, fault tolerance, and flexibility are critical requirements. It complements vertical scaling by offering a more flexible and scalable approach to handling increased workload or traffic.</p><p><strong>Designing a Basic Cloud Architecture</strong></p><p>I covered a conceptual architecture, illustrating the data flow, component interactions, and infrastructure setup necessary to support a web application in a cloud environment.</p><p>These are some <strong>basic requirements</strong> which every web-application must satisfy.</p><ul><li>The application <em>must be highly scalable, must be highly available, must be able to recover in case of failure</em>.</li><li>The application must <em>have a domain name</em>.</li><li>The application must provide <em>different content based on geographic location</em>.</li><li>The application must ensure protection in case of <em>DDOS attacks</em> and other cyber attacks in case of<em> web exploits, sql injection, cross site scripting attacks</em>.</li><li>The application must be <em>continuously monitored</em> for performance and developers must be notified in case of changes to the performance of the application.</li><li>The application must <em>allow users to access the application using mobile devices</em>.</li></ul><p>The architecture to satisfy the above requirements is as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eyM4Wqo3dMbB9CbB.png" /></figure><p>The explanation for the each component in the architecture is as follows:</p><p>1 — The application is hosted on <a href="https://aws.amazon.com/ec2/">EC2</a> instances, in order to <strong>resolve for scalability</strong>, the application is hosted in an <a href="https://aws.amazon.com/de/ec2/autoscaling/">Autoscaling Group</a>. One can control the traffic to allow/deny in the EC2 instances using <a href="https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html">Security Groups</a>.</p><p>2 — In order to have <strong>high availability</strong> the application is hosted in multiple <a href="https://aws.amazon.com/about-aws/global-infrastructure/regions_az/">availability zones</a>.</p><p>3 — Traffic is distributed across availability zones using an <a href="https://aws.amazon.com/elasticloadbalancing/">Elastic Load Balancer</a>.</p><p>4 — In order to <strong>recover</strong> the application during any unfortunate events, one can store the EC2 and database images using <a href="https://aws.amazon.com/s3/">AWS S3</a>.</p><p>5 — In order to<strong> store the application based data</strong>, one can use a fully managed relational database like <a href="https://aws.amazon.com/rds/">Amazon RDS</a>.</p><p>6 — In order to expose the application with a domain name (application URL) and convert the domain name to a public IP one must use a <strong>domain name service.</strong> In our case this is <a href="https://aws.amazon.com/route53/">AWS Route53</a>. One must also protect the application from <strong>Distributed Denial of Service (DDOS) attacks</strong>, to satisfy this requirement one can use <a href="https://aws.amazon.com/shield/">AWS Shield</a>.</p><p>7 — Using <a href="https://aws.amazon.com/waf/">AWS Web Access Firewall</a> one can define managed rules in order to protect the application from <strong>common web exploits, bots that can affect availability, compromise security, sql injection, cross site scripting and consume excessive resources</strong>. The managed rules for waf are defined to control the attacks based on http headers, geo-location and frequency of requests.</p><p>8 — <a href="https://aws.amazon.com/cloudfront/">Cloudfront</a> is the <strong>content delivery network service</strong> from AWS, one can use this to deliver content based on region, or one can use it to cache the frequent requests</p><p>9 — The <strong>mobile users </strong>can access the application using <a href="https://aws.amazon.com/api-gateway/">API gateway</a>, it is a fully managed service to create, publish and secure APIs at any scale.</p><p>10 — AWS <a href="https://aws.amazon.com/lambda/">Lambda</a> is a serverless compute service from AWS that can be used to <strong>apply business logic</strong> to the applications data.</p><p>11 — AWS <a href="https://aws.amazon.com/cloudwatch/">Cloudwatch</a> is used for <strong>continuously monitoring </strong>the application’s webservers if they are down, or if they are restarting. Cloudwatch is used to continuously monitor the performance of the application.</p><p>12 — AWS <a href="https://aws.amazon.com/guardduty/">GuardDuty</a> is an <strong>intelligent threat detection service</strong>, it continuously monitors the servers and notifies if a server, database, s3 is compromised, malware, anomalous behavior.</p><p>13 — AWS <a href="https://aws.amazon.com/sns/">Simple Notification Service</a> is a fully <strong>managed messaging service</strong> for communication, allowing messaging between decoupled microservices applications or directly to<strong> users with SMS</strong>. This can notify users for any performance changes in the application.</p><p><strong>Conclusion:</strong></p><p>The architecture explained above is a basic aws based architecture for web-application, depending on the use case and user requirements one can add/remove services from the architecture.</p><p>The architecture shown above is a fully managed architecture, however one can also deploy serverless architecture for web-application using <a href="https://aws.amazon.com/elasticbeanstalk/">AWS Elastic Beanstalk</a>.</p><p><strong>Reflection</strong></p><p>This week’s journey was both challenging and rewarding. I gained a deeper understanding of version control with Git, cloud architecture fundamentals, and the importance of scalability in modern applications. Join me next week as I continue to explore advanced topics and practical implementations in my Cloud Journey!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dea6f829d0fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embarking on my cloud Journey | Week 1 Cloud Fundamentals]]></title>
            <link>https://medium.com/@jimmyrema77/embarking-on-my-cloud-journey-week-1-cloud-fundamentals-2524c0d0c136?source=rss-bdc8fef9499a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2524c0d0c136</guid>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Jimmy Rema]]></dc:creator>
            <pubDate>Fri, 10 May 2024 17:24:35 GMT</pubDate>
            <atom:updated>2024-05-10T17:24:35.387Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DkUjxhGEeEY1C1Zl34VgvA.jpeg" /></figure><p>Hello, my name is Jimmy Rema. I have always wanted to learn cloud technology and I have finally made the jump. Through my research, I came across Soleyman Cloud Engineer Academy. The hands on labs and building a portfolio of impressive cloud projects that you can showcase during interviews or share on your LinkedIn is what caught my eyes. I’m super excited to learn from this Academy. Below is what I have covered in week 1:</p><p><strong>what is Cloud Computing?</strong></p><p>Cloud computing is the on-demand delivery of IT resources i.e. servers, storage, databases etc., over the internet with pay-as-you-go pricing. This paradigm eliminates the need for physical hardware management, enabling remote access to resources and programs.</p><p><strong>Deployment models for cloud computing</strong></p><p>When selecting a cloud strategy, a company must consider factors such as required cloud application components, preferred resource management tools, and any legacy IT infrastructure requirements.</p><p>The three cloud computing deployment models are public cloud-based, private cloud, and hybrid:</p><p>. With public cloud-based: Run all parts of the application in the cloud, Migrate existing applications to the cloud, Design and build new applications in the cloud. It is accessible to everyone.</p><p>. With private cloud: Deploy resources by using virtualization and resource management tools, Increase resource utilization by using application management and virtualization technologies. It is maintained on a private network, used internally for businesses with strict control, privacy and sensitive data such as governments.</p><p>. With hybrid cloud: In a hybrid deployment, public cloud-based resources are connected to private cloud infrastructure.</p><p><strong>Types of cloud service models</strong></p><p>There are three main models for cloud computing. Each model represents a different part of the cloud computing stack:</p><p>Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) models.</p><ul><li>IaaS: Infrastructure as a Service contains the basic building blocks for cloud IT and typically provide access to networking features, computers (virtual or on dedicated hardware), and data storage space. Infrastructure as a Service provides you with the highest level of flexibility and management control over your IT resources and is most similar to existing IT resources that many IT departments and developers are familiar with today.</li><li>PaaS: Platforms as a service remove the need for organizations to manage the underlying infrastructure (usually hardware and operating systems) and allow you to focus on the deployment and management of your applications. This helps you be more efficient as you don’t need to worry about resource procurement, capacity planning, software maintenance, patching, or any of the other undifferentiated heavy lifting involved in running your application.</li><li>SaaS: Software as a Service provides you with a completed product that is run and managed by the service provider. In most cases, people referring to Software as a Service are referring to end-user applications. With a SaaS offering you do not have to think about how the service is maintained or how the underlying infrastructure is managed; you only need to think about how you will use that particular piece of software. A common example of a SaaS application is web-based email where you can send and receive email without having to manage feature additions to the email product or maintaining the servers and operating systems that the email program is running on.</li></ul><p><strong>Virtualization</strong></p><p>Virtualization in cloud computing is the process of creating virtual versions of physical component such as servers, storage devices, networks and operating systems.</p><p><strong>Networking</strong></p><p>In cloud computing, networking is about linking various cloud based resources such as servers, storage systems and applications over the internet. This networking allows for the exchange of data and services across a distributed and often scattered globally infrastructure.</p><p><strong>IP Addresses</strong></p><p>An IP address(Internet Protocol) is a numerical label assigned to each device connected to a computer network that used Internet Protocol for communication. The limited number of IPv4 addresses has led to various techniques such as NAT(Network Address Translation) and the push towards adopting IPv6</p><p><strong>DNS(Domain Name System)</strong></p><p>The role of DNS is to translate human readable domain names into numerical IP addresses that computers use to locate each other on a network. By converting domain names into IP addresses, DNS ensures data packets are routed correctly across the internet to reach the intended destination.</p><p><strong>Cloud Operating Systems and Features</strong></p><p>Operating systems manage hardware resources such as CPU, Memory, Storage across distributed environments.</p><p>Window server is designated to support Hybrid Cloud Architectures, allowing businesses to expand their on-premises infrastructures into Microsoft Azure.</p><p>Linux Distributions such as Ubuntu, Centos, Red Hat are common in cloud environments.</p><p><strong>Databases</strong></p><p>A database is a structured collection of data that is stored electronically on a computer system. Its purpose is to make it easy to access, manipulate, update and retrieve data. There are many types of databases, the most common ones being, Relational and No-relational(Also known as NoSQL) databases.</p><p><strong>Practical Projects</strong></p><p>Week 1’s projects focused on AWS account setup, and essential networking tasks such as curl requests, traceroutes, IP address retrieval, and OS setup, providing hands-on experience in essential tools and techniques.</p><p><strong>Closing thoughts</strong></p><p>In just one week, my journey through cloud computing concepts has been enlightening and exhilarating. Stay tuned for more insights and experiences as I continue to navigate the ever-evolving landscape of cloud technology.</p><p><a href="http://www.linkedin.com/in/">www.linkedin.com/in/</a>jimmy-rema-a3ba441bb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2524c0d0c136" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>