<?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 Ken Ong on Medium]]></title>
        <description><![CDATA[Stories by Ken Ong on Medium]]></description>
        <link>https://medium.com/@ridlock?source=rss-3997b0aa7259------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LkzvDiPZf0nCSQ4qm0mqtQ.jpeg</url>
            <title>Stories by Ken Ong on Medium</title>
            <link>https://medium.com/@ridlock?source=rss-3997b0aa7259------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:58:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ridlock/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[Use SSH Agent Forwarding to Access Instances in AWS —  Module 4]]></title>
            <link>https://medium.com/@ridlock/use-ssh-agent-forwarding-to-access-instances-in-aws-module-4-0dc0fdc2365a?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/0dc0fdc2365a</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[aws-instance]]></category>
            <category><![CDATA[multiple-ssh-keys]]></category>
            <category><![CDATA[ssh]]></category>
            <category><![CDATA[ssh-agent-forwarding]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Tue, 15 Oct 2024 19:20:09 GMT</pubDate>
            <atom:updated>2024-10-15T19:20:09.961Z</atom:updated>
            <content:encoded><![CDATA[<h3>Use SSH Agent Forwarding to Access Instances in AWS — Module 4</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7vn-Ro5kqaFD-Flla-g93w.png" /><figcaption>SSH-ing…</figcaption></figure><p>Diving Into Week 4 Of Cloud Engineer Academy by Soleyman (<a href="https://www.cloudengineeracademy.io/">Cloud Engineer Academy</a>) I was particularly challenged when it was mentioned that there was a way to log in to instances with different credentials. In the module, it was discussed for simplicity that the private key would be copied into the instance to retain access to it for demonstration and learning purposes. The process was a bit more complex if we were to use different keys for different instances. This is on the premise that you have a bit of a background in AWS Services. Time to dive a little bit deep.</p><p><strong>THE SETUP:</strong></p><p>We create a Multi-AZ setup with 2 Availability Zones with 3 subnets each. Subdivide the subnets into 1 Public subnet and 2 Private subnets in each AZ totaling to 6 subnets.</p><p>Create the appropriate instances.</p><ul><li>One (1) instance for the Public subnet which will serve as a Bastion Host</li><li>Two (2) instances for the Private subnet.</li><li>Points above should be replicated to another Availability Zone.</li><li>Each instances are to have different keys in order to access them.</li></ul><p>Create Security Groups with the following:</p><ol><li>SSH into the Bastion Host Instance publicly.</li><li>SSH into the 1st private instance in AZ-1 with the appropriate key.</li><li>SSH into the 2nd private instance in AZ-1 with the appropriate key.</li><li>The 1st private instance in AZ-1 will be able to PING/ICMP a private instance in AZ-2. Just to test out the connection.</li></ol><p>Either use 2 ways to set this up depending on what you are used to. Through CloudFormation/ Terraform or ClickOps in the AWS Console. Should look something like below diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*xV7nfVmMuCUzI1yUNEE3hg.png" /><figcaption>AWS VPC</figcaption></figure><p>So instead I sought out to find out how to actually make it more secure instead of just leaving the credentials on the instance and anyone that could gain access to the credentials (God forbid) would be able to mess things up. With a little digging a I did find a solution which is shown as of below:</p><p>By using WSL (Windows Subsystem for Linux):</p><pre>#Type the command below:<br><br>ssh<br><br>#This is to check whether ssh is available</pre><p>You should get something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*BU0ZBX8GfN1qM5N3bbL8lA.png" /><figcaption>SSH command</figcaption></figure><p>Go to the directory wherein you saved your key pairs, which is usually in your <em>~/.ssh/</em> (try to change where you hide it when not in practice) for safe keeping.</p><pre>#Type below:<br><br>eval $(&#39;ssh-agent&#39;)<br><br>#To enable the ssh-agent forwarding<br><br>#Then get a list of your available keys<br><br>ls- l</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*742x3-H9TqIvKKIcWvP_Hw.png" /><figcaption>Eval</figcaption></figure><p>As we can see above, our permissions are too open which others can view. When we log into our instances we will most likely get notified that our permissions on the key file are too permissive. Thus we have to restrict them accordingly and we can do the following below:</p><pre>#Type below:<br><br>chmod 400 &quot;yourkeypair1&quot; &quot;yourkeypair2&quot; &quot;yourkeypair3&quot; <br><br>#This will change the following permission to make it more restrictive to <br>only you.<br><br>#Afterwards check the list again with:<br><br>ls -l</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*ytrVzdD7yXccJ5TXKGpZRw.png" /><figcaption>Change Permission</figcaption></figure><p>Now that our permissions are restricted we should not have any warning messages logging into our instances when the keys are in use.</p><pre>#Add the identities on the ssh-agent<br>#Type below:<br><br>ssh-add &quot;yourkeypair1&quot; &quot;yourkeypair2&quot; &quot;yourkeypair3&quot;<br><br>#Check to see if the keys are added to the agent<br><br>ssh-add -l</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/917/1*B5WRx6i0LL7zoyd6bcR7Cg.png" /></figure><p>Once we have confirmed that they have been added we can now start to log-in to our instances remotely.</p><p>Initially we will be logging in to our Bastion Host.</p><pre>#Get your Public IP from your Bastion Host Instance.<br>#Type in below:<br><br>ssh -A &quot;instance_username@public_ip_address&quot;<br><br>#the purpose of -A is to forward the keys to the instance instead of<br>copying them. Notice that &quot;-i&quot; was not used as we don&#39;t need to identify <br>the key to be used. <br><br>#then we check if keys were forwarded to the Bastion Host with:<br><br>ssh-add -l</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*47xm2APzy0V2BZgetPqV0A.png" /></figure><p>Once we have confirmed that the keys are also present on the Bastion Host, we can then log in to our private instance named “AppInstance1A”</p><pre>#Note down the private IP of your 1st private instance in AZ-1<br>#Note down the private IP of your 2nd private instance in AZ-2<br>#Log in to your private instance in AZ-1 with:<br><br>ssh -A &quot;instance_username@private_ip_address_1st_private_instance_AZ-1&quot;<br><br>#Ping the 1st private instance in AZ-2 with:<br><br>ping &quot;private_ip_1st_instance_AZ-2&quot;<br><br>#You should get replies if successful or a timeout if not.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/1*vwpvUi_QZcSmla-tUH7mtg.png" /></figure><p>Once we have successfully gained a connection with our 1st private instance in AZ-2, it means we have succeeded and have properly configured our Security Group.</p><p>We then log in to our 2nd Private Instance in AZ-1 by checking first if our agent has properly forwarded the keys onto our instance.</p><pre>#Run the list command again to see the keys in the 1st private instance<br><br>ssh-add -l<br><br>#Take note of the private ip address of the 2nd private instance<br>#Log in with the following:<br><br>ssh -A &quot;instance_username@private_ip_address_2nd_private_instance_AZ-1&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*cZ25ynyE7jTqcdswvhuQsw.png" /></figure><p>VOILA!!! We have successfully used SSH Forwarding to gain access to multiple instances with different keys.</p><p>Now we clean things up by terminating the connection and deleting the keys from the ssh-agent.</p><pre>#Exit out of our instances by typing:<br><br>exit<br><br>#Do this for each instance you are in to exit.<br><br>#You should be back to your main WSL console.<br><br>#Use additional command below to delete the keys from your agent:<br><br>ssh-add -D<br><br>#Use command below to kill the ssh-agent connection.<br><br>eval &quot;$(ssh-agent -k)&quot;<br><br><br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*4fBQCgQbHuOIowpOYZdmQg.png" /></figure><h3><strong>KEEP IN MIND</strong></h3><p>By using ssh-agent forwarding (*USE WITH CAUTION*)with different key pairs for logging into different instances, it is also not as safe as its supposed to be as anyone with the know how could actually hi-jack your connection and have access to your keys. This article is only an example of how to use the forwarding agent. Best practices are always key to keeping keys safe.</p><p>An alternative best practice would be to use a Jump Server or ProxyJump which lets you jump to different SSH servers without agent forwarding. There would be other ways to make agent forwarding secure but that is a topic for another time.</p><p>===============================================================</p><p>Join me in my Cloud Journey to be able to soar to new heights!</p><p>Always good to have feedback, if any!</p><p>Add me up ( “ , ) Let’s Connect <a href="http://www.linkedin.com/in/ken-ong9090">www.linkedin.com/in/ken-ong9090</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dc0fdc2365a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Video Hosting Platform — Module 3.3]]></title>
            <link>https://medium.com/@ridlock/designing-a-video-hosting-platform-module-3-3-e32388216753?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/e32388216753</guid>
            <category><![CDATA[cloud-journey]]></category>
            <category><![CDATA[aws-architecture]]></category>
            <category><![CDATA[video-platforms]]></category>
            <category><![CDATA[youtube-diagram]]></category>
            <category><![CDATA[video-architecture]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Wed, 25 Sep 2024 16:49:02 GMT</pubDate>
            <atom:updated>2024-09-26T17:39:48.246Z</atom:updated>
            <content:encoded><![CDATA[<h3>Designing A Video Hosting Platform — Module 3.3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uWM1nIWwIyqgvWg2DVUwJw.png" /></figure><p>Let’s get to it!</p><p>What is a good place to start when we build services? Usually we would like to know the different features and capabilities of what a service is to be used for. Thus we ask certain questions in order for us to create a workflow or system design, then we incorporate the needed services in the most secure, durable, scalable and cost efficient manner be it for personal or commercial use.</p><p>Within this module we will be creating a <strong>Video Hosting Platform</strong> similar to the likes of the YouTube Architecture. Brief concepts will be discussed and the reasons for using such services in the architecture.</p><h3><strong>Features of the platform:</strong></h3><ol><li>Videos need to be uploaded and stored in a durable storage with high availability and able to automatically scale.</li><li>Search function in order to locate videos through tags or metadata for retrieval.</li><li>View video content in different resolutions to cater to appropriate end users.</li><li>Filter adult content to avoid serving it publicly.</li></ol><h3><strong>Architecture:</strong></h3><p>The platform has to be:</p><ol><li>Scalable</li><li>Resilient with high availability</li><li>Cost effective</li><li>Secure</li></ol><h3><strong>Services to be used:</strong></h3><ol><li><strong>AWS S3 —</strong> for durable, scalable and highly available storage for hosting static content and websites.</li><li><strong>AWS Route53 — </strong>highly available and scalable Domain Name System (DNS), domain name registration, and health-checking web services.</li><li><strong>AWS CloudFront —</strong> caches content closer to users for faster access.</li><li><strong>AWS Web Application Firewall —</strong> protect the web application from attacks, to monitor requests and control access to the content.</li><li><strong>AWS Certificate Manager — </strong>provision, manage, and deploy public and private Secure Sockets Layer/Transport Layer Security (SSL/TLS) certificates for use with AWS services and your internal connected resources.</li><li><strong>AWS DynamoDB — </strong>fast and flexible nonrelational database service for any scale that can hold objects metadata.</li><li><strong>AWS OpenSearch — </strong>easily ingest, secure, search, aggregate, view, and analyze data for a number of use cases such as log analytics, application search, enterprise search, and more. To query the metadata from DynamoDB.</li><li><strong>AWS Lambda — </strong>for serverless compute or triggers in the architecture.</li><li><strong>AWS Rekognition — </strong>image recognition service that detects objects, scenes, activities, landmarks, faces, dominant colors, and image quality. Also extracts text, recognizes celebrities, and identifies inappropriate content in images stored in S3.</li><li><strong>AWS Elemental Media Convert — </strong>file-based video transcoding solution processes video files, creating compressed versions of the original content to reduce its size, change its format, or increase playback device compatibility.</li><li><strong>AWS Step Functions — </strong>reliable way to coordinate components and step through the functions of your application. Provides a graphical console to arrange and visualize the components of your application as a series of steps.</li><li><strong>AWS API Gateway — </strong>simple, flexible, fully managed, pay-as-you-go service that handles all aspects of creating and operating robust APIs for application back ends.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7MVoM-Y6DIPawV9u3DeWWw.gif" /><figcaption>Stream Architecture Diagram</figcaption></figure><p><strong>Design Flow:</strong></p><ol><li>User uploads a video to the Stream website wherein the traffic is routed by Route53 to CloudFront with latency-based routing enabled.</li><li>To make the connection secure an added layer of AWS Certificate Manager for TLS/SSL traffic and Web Application Firewall is placed to set up necessary filters and Access Control Lists for users of a certain location.</li><li>The static website is then reached that is hosted in an S3 bucket.</li><li>The video is then uploaded to a durable, scalable, cost-efficient and highly available object storage such as an S3 bucket for further processing.</li><li>Metadata is then sent over to an unstructured database (NoSQL) such as DynamoDB.</li><li>The video is then processed by AWS Rekognition to filter sensitive or adult content. If any such content is found then the video metadata will be flagged and will not be further processed.</li><li>OpenSearch is included in the diagram in order to filter/query the metadata stored in DynamoDB which is often faster with lower latency than querying the data that is directly stored in an S3 bucket.</li><li>The video is then transcoded into different video resolutions/codec with AWS Elemental Media Convert into 480p, 1080p or 4K(The following are supported Codec: <em>AV1, AVC-Intra, AVC (H.264), HEVC (H.265), MPEG-2, Apple ProRes, VC-3, VP8, VP9, XAVC</em>).</li><li>We include AWS Step Functions into the picture in order to have a workflow made to convert the necessary videos according to their format and place them in a separate S3 buckets with the appropriate prefixes for faster querying.</li><li>The appropriate video is then cached on AWS CloudFront once it has been requested for faster accessibility.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*3YmTZvWQNTToah0B0zVDBA.gif" /><figcaption>Cached Content</figcaption></figure><p><strong>User Searching For A Frequently Seen Video</strong></p><ol><li>A request for a frequently seen video is received from the website.</li><li>Routes the traffic to CloudFront which has the cached video.</li><li>It is then sent to the user with the lowest latency for viewing.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R7S10gPhDUXobH5ExrR58g.gif" /><figcaption>Retrieving New Content</figcaption></figure><p><strong>User Searching For A New Video</strong></p><ol><li>When a new request is received and the video is not cached in the Content Delivery Network (CloudFront) a few extra steps will be needed in order to retrieve the content.</li><li>The API Gateway receives the request and routes it to the Lambda Function for logical processing.</li><li>A trigger is then initiated for the function to query the DynamoDB database for the appropriate search being requested by the user.</li><li>The new content is then retrieved from the S3 bucket and cached on the Content Delivery Network for future requests for faster accessibility and delivery of content.</li></ol><p>The above architecture shows just a basic core design of a video platform as we have not dived deep enough in terms of configurations, VPCs, route tables or domain names. This is just to give a birds eye view of a possible Video Streaming architecture that is secure, resilient with high availability, scalable and cost effective.</p><p>===============================================================</p><p>Join me in my Cloud Journey to be able to soar to new heights!</p><p>Always good to have feedback, if any!</p><p>Add me up ( “ , ) Let’s Connect <a href="http://www.linkedin.com/in/ken-ong9090">www.linkedin.com/in/ken-ong9090</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e32388216753" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Passed AWS-Solutions Architect Associate… now what?]]></title>
            <link>https://medium.com/@ridlock/passed-aws-solutions-architect-associate-now-what-4994d8fe0b23?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/4994d8fe0b23</guid>
            <category><![CDATA[udemy]]></category>
            <category><![CDATA[tutorial-dojo]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[passing-aws-saa]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Fri, 20 Sep 2024 04:02:05 GMT</pubDate>
            <atom:updated>2024-09-20T04:02:05.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbbEQEFN4qBkyBJ0vFdGtg.png" /></figure><p>After sleepless nights of understanding and putting the pieces together, I finally made it pass the 1st step of becoming a Cloud Engineer. Yes, you heard it, the 1st baby step aside from learning all the fundamentals of networking, what the cloud is and types of distributed architecture. Though this is the 2nd time I took the exam and finally passed with flying colors it was all worth it. The feeling from the 1st exam was terrible but it wasn’t the end but only the beginning of truly understanding the bigger picture. Took a few days to recover from the shock of seeing FAIL at the time. It was no fault but mine as I truly wasn’t prepared for it and took a shot. I barely passed but missed a couple of questions along the way. Imagining scoring close to 720 but just missing a few points as I ran out of time. It is one thing to fail but what’s worse is giving up. Sure some things are hard, but hardships can always be overcome once you put your head in the game and concentrate.</p><p>During the 2nd exam for some reason I felt a feeling of reluctance and assurance that I did well in the exam. Since you can flag the questions and go back to the ones you weren’t sure of, it helped a lot to know in advance which ones were possible mistakes. In fact it was almost accurate to know exactly how many mistakes there were. With that in mind, I knew I had succeeded this time. After the exam, I already had a huge smile on. Finally, late in the evening I opened my email and I turned to my wife with a big grin and showed her the email “CONGRATULATIONS”. There it was.</p><p>On another note, going back as to why this is a baby step towards a larger puzzle is that there is so much to learn outside of AWS in order to actually piece things together. To fully utilize the service to its maximum potential one has to incorporate different concepts and understanding of other services such as repositories, CI/CD pipelines, BASH, programming language such as Python, Linux, Databases… and the list goes on. Understanding is one thing but actually putting them into practice is another. Hands on, real world situations is what is needed IN addition to certifications. Yes it looks nice to have it and shows that you are well versed in a certain environment but it doesn’t guarantee that you have the skill if you don’t get to use it. As it goes “A Jack Of All Trades, A Master Of None”. If we don’t use it, we lose it. Implementation is the key to mastering a skillset. Once we have that, everything else becomes muscle memory.</p><p>I wouldn’t have been able to succeed by myself, but with the help of resources from <a href="https://medium.com/u/98189c4cef0">Stéphane Maarek</a> through his Udemy course which is one of the best out there, from <a href="https://medium.com/u/c90a38dd4dea">Jon Bonso</a> through <a href="https://tutorialsdojo.com/">Tutorial Dojos</a> for his course, review material and practice exams, from Soleyman Shahir (<a href="http://cloudengineeracademy.io/">cloudengineeracademy.io</a>) for his pathway to becoming a Cloud Engineer. Kudos to all of you!</p><p>On to the next…</p><p>===============================================================</p><p>Always good to have feedback, if any!</p><p>Add me up ( “ , ) Let’s Connect <a href="http://www.linkedin.com/in/ken-ong9090">www.linkedin.com/in/ken-ong9090</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4994d8fe0b23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Project Traditional and Serverless Design — Module 3.2]]></title>
            <link>https://medium.com/@ridlock/cloud-project-traditional-and-serverless-design-module-3-2-d835e5062144?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/d835e5062144</guid>
            <category><![CDATA[anpr]]></category>
            <category><![CDATA[serverless-architecture]]></category>
            <category><![CDATA[anpr-diagram]]></category>
            <category><![CDATA[cloud-project]]></category>
            <category><![CDATA[traditional-architecture]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Mon, 26 Aug 2024 18:17:16 GMT</pubDate>
            <atom:updated>2024-09-25T04:43:30.880Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Project Traditional and Serverless Design — Module 3.2</h3><p>Within this module we will be designing 2 architectures. First as a Traditional Server Scaling Design and the second as a Serverless Scaling Design. Brief concepts will be discussed in the diagram below and a comparison will be made afterwards.</p><p><strong>Traditional Scaling</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*MR3rrM4xQE5HMF6wpkuBaA.jpeg" /></figure><p><strong>Design Overview</strong>:</p><p>The design above is that of a <strong>Vehicle Plate Recognition Application</strong> and its dataflow as a traditional scaling design. The following services in AWS were coupled together.</p><ol><li><strong>AWS S3 —</strong> storage of the image objects for processing.</li><li><strong>AWS Elastic Load Balancer —</strong> to manage the incoming traffic from the number of photos the application receives.</li><li><strong>EC2 instances</strong> — for compute usage which directs data to Rekognition</li><li><strong>Auto Scaling Group</strong> — automatically scales to additional instances for added compute.</li><li><strong>AWS Rekognition</strong> — utilizes the OCR (Optical Character Recognition) to read the vehicle license plate.</li><li><strong>DynamoDB</strong> — license plate information is kept in a NoSQL database.</li><li><strong>Secrets Manager</strong> — where secrets of the 3rd party are kept.</li><li><strong>3rd Party API</strong> — Calls a 3rd Party IoT API for further processing</li></ol><p>By implementing this traditional design, the main drawbacks would be its cost-effectiveness and availability. As the instances are always on you would be charged as long are they are kept in an active state. In order to reduce costs, you can choose reserved instances which would give you a 75% reduction and thus savings for the long term of either 1 or 3 year term.</p><p>Availability is the other concern as we are using the traditional design. In order to have High Availability another Availability Zone or Region would have to be made and thus increasing costs for the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*TBQ-LgHjBYS8aEAR6ePq4A.jpeg" /></figure><p>The Serverless Design above would be a more cost effective and highly available option as most of the services are region specific. Cost effective due to having no instances for computational power which we replace with the Lambda service to execute codes accordingly to the different services.</p><p>Availability and Scalability are better in this design due to their services which are Region based and not only tied to one Availability Zone. By using Lambda, it replaces the instances for serverless compute and will automatically scale</p><ol><li><strong>Security Camera</strong> — detects the car and takes a snapshot of it.</li><li><strong>S3 Bucket</strong> — snapshot is stored in the bucket.</li><li><strong>Lambda</strong> — serverless compute code which directs what each service will be doing.</li><li><strong>AWS Rekognition</strong> — utilizes the OCR (Optical Character Recognition) to read the vehicle license plate.</li><li><strong>DynamoDB</strong> — license plate information is kept in a NoSQL database.</li><li><strong>Secrets Manager</strong> — where secrets of the 3rd party are kept.</li><li><strong>3rd Party API</strong> — Calls a 3rd Party IoT API for further processing</li></ol><p><strong>Performance Under Varying Load</strong></p><p>In Traditional Architecture, as long as the load is within its provisioned architecture it makes things predictable and can be handled. With the provision of additional instances there may also be a delay that will occur when scaling is needed. Also there are more points of failure to look out for within such a design.</p><p>In Serverless Architectures with AWS Lambda, they can scale instantly and automatically to handle thousands of concurrent executions. Applications with consistent traffic, keeping Lambda functions “warm” can eliminate cold starts, resulting in consistent performance.</p><p><strong>Cost Efficiency At Scale</strong></p><p>In Traditional Architecture, there is a baseline cost for maintaining the necessary infrastructure regardless of usage. In the case of instances, it is always wise to use Reserved Instances if you know the application is working 24/7. Though after a certain point, costs add up when scaling in and out with possible over-provisioning and maintenance of idle resources during off-peak times.</p><p>In Serverless Architecture it is on a pay-per-use basis. Costs are tied to usage of the different services as they are used. You pay for the number of executions and the compute time used. For unpredictable workloads, serverless would be the more cost-efficient option as you are not paying for idle capacity.</p><p><strong>Development, Deployment and Maintenance</strong></p><p><strong>Traditional Architecture</strong>:</p><ul><li><strong>Development — </strong>easier to spin up instances but more consideration for server configurations, deployment strategies, and scaling mechanisms.</li><li><strong>Deployment —</strong> Setting up CI/CD pipelines to manage the deployment of applications to various servers.</li><li><strong>Maintenance — </strong>Requires ongoing management of servers, including updates, security patches, and scaling.</li></ul><p><strong>Serverless Architecture:</strong></p><ul><li><strong>Development —</strong> Dev Teams can focus more on application logic and less on the infrastructure side.</li><li><strong>Deployment —</strong> Simplified with IaC (Infrastructure as Code) and integration with serverless frameworks that handle deployment to AWS.</li><li><strong>Maintenance — </strong>Significantly reduced as AWS manages the servers, operating systems, patches and runtime environments.</li></ul><p>In preference, serverless would be the best way to go in terms of flexibility, scalability, availability and maintenance. Though it will always depend on the application’s traffic / load but most of all budget constraints of the project as to decide which type of architecture is suitable.</p><p>===============================================================</p><p>Always good to have feedback, if any!</p><p>Add me up ( “ , ) Let’s Connect <a href="http://www.linkedin.com/in/ken-ong9090">www.linkedin.com/in/ken-ong9090</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d835e5062144" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Time To Focus On Cloud Architecture — Module 3.1]]></title>
            <link>https://medium.com/@ridlock/time-to-focus-on-cloud-architecture-module-3-1-2b9c5ae78996?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b9c5ae78996</guid>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[three-tier-architecture]]></category>
            <category><![CDATA[monolithic]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Fri, 23 Aug 2024 05:27:40 GMT</pubDate>
            <atom:updated>2024-08-24T05:27:33.012Z</atom:updated>
            <content:encoded><![CDATA[<h3>Time To Focus On Cloud Architecture — Module 3.1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_JwU7DODMVkqZRo1BXT3Nw.png" /></figure><p>As we venture further into Cloud Territory we come across these different paths on how to make our backend architecture. A question always comes to mind as to which one would be the best type to have? Does the project entail a scalable architecture with multiple microservices needed? Or one that is of a legacy or monolithic type wherein everything is compacted altogether? Below is a brief discussion for the types of architecture that are present.</p><p>We start with the <strong>Monolithic Architecture</strong>. <strong>Mono</strong> (meaning One) <strong>Lithic</strong> (great stone). In lay man terms, its all bundled together and inseparable. Its a single software tier application that has 3 components that include the User Interface, Business Logic and the Data Interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*OtjhKqxrpUSupvWAp5Ra_Q.jpeg" /></figure><ol><li><strong>User interface</strong> — where users interact with the application, collects the users input and collects data from the system.</li><li><strong>Business Logic</strong> — contains the core computational logic of the application. Processes input and applies relevant rules based on the data provided by the users.</li><li><strong>Data Tier</strong> — otherwise known as the data access layer; responsible for communicating with the database. Updates and stores data performed by the Business Logic.</li></ol><p>This all works as one service. In case of any changes to the code, it will likely affect the whole application and thus may not work properly or worse not work at all.</p><p><strong>Advantages</strong> of a Monolithic Architecture:</p><ol><li><strong>Simplicity </strong>— simple to develop and deploy as all components are in a single codebase. Usually entails a small dev team for this type of architecture.</li><li><strong>Uniformity </strong>— a unified environment for developers to work in.</li><li><strong>High Performance — </strong>since system calls can be made directly to the kernel without the overhead of message passing between user-level processes.</li><li><strong>Lesser Latency — </strong>due to the application being in a single environment.</li><li><strong>Easier to debug</strong></li></ol><p><strong>Disadvantages</strong>:</p><ol><li><strong>Slower development speed —</strong> A large application makes development more complex and slower.</li><li><strong>Less scalability —</strong> is tightly coupled, making it hard to scale but not impossible to scale.</li><li><strong>Inability to adapt to new technologies — </strong>since they are tightly coupled, it can hinder the adoption of new technologies.</li><li><strong>High dependence between functionalities — </strong>Monolithic applications can run into software engineering and downtime difficulties due to their tight dependency.</li></ol><p>Then we go a bit deeper into the <strong>Microservices Architecture.</strong></p><p>What exactly is a microservice? Think of it as each core function or the type of service it offers is built and deployed independently. You would have several teams for each type of data needed which makes the application loosely coupled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*F2WP0GJl88KDiMvLcdaRFA.jpeg" /></figure><p>We have <strong>3 Layers</strong> which consist of:</p><ol><li><strong>User Interface </strong>— where the end user interacts with and is the front end of the application. Communicates with the various independent services.</li><li><strong>Microservices</strong> /<strong>Logic</strong>— each microservice is a single business capability such as user authentication, product catalog management or order processing. Which can be developed, deployed and scaled from each other.</li><li><strong>Database </strong>— each microservice has its own database which ensures loose coupling and independent scalability. Changes to one microservice database does not impact any other microservice.</li></ol><p><strong>Advantages </strong>of Microservices:</p><ol><li><strong>Scalability</strong> — provides granular scalability, and individual services can be scaled separately according to the demand.</li><li><strong>Agility</strong> — teams can work on different services at the same time, using multiple technology stacks and deployment models. Development Teams can perform release and update services in isolation without impacting the whole application</li><li><strong>Resilience /Fault Isolation</strong> — services are independent of one another. If the failure happens in one service, the other parts of the application will remain untouched.</li><li><strong>Technology Diversity </strong>— Development teams can select the best tools and languages to be used for each service to achieve the best performance, scalability, and maintainability.</li></ol><p><strong>Disadvantages</strong> of Microservices:</p><ol><li><strong>Complexity</strong> — Building, running, and governing a microservices-based app demands specialized skills, tools, and advanced monitoring and orchestration capabilities.</li><li><strong>Distributed System Challenges</strong> — communication between services happens via a network, which leads to increased latency, networking overhead, and potential failure points.</li><li><strong>Operational Overhead </strong>— running a large number of microservices in production environments is huge. Ergo, <strong>expensive.</strong></li><li><strong>Data Management</strong> — each service has its data store, and there can be a duplication of data, thereby leading to inconsistency and synchronization issues.</li><li><strong>Service Discovery &amp; Communication</strong> — Microservices have to discover and talk to each other dynamically. Therefore, a strong service discovery mechanism is needed. Managing service endpoints, load balancing, and failover across distributed services is hard.</li></ol><p>Somewhere in the middle we place <strong>Serverless Architecture</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*Sz09_--I51AWuVjuu5STFw.jpeg" /></figure><p>Another Cloud model wherein the Cloud Provider (ie. AWS / AZURE GCP ) directly manages the allocation and provisioning of service. It runs in a stateless compute container that are event triggered and are fully managed by the Cloud Provider. With such an architecture the operational management such as patching, scaling and provisioning are completely handled by the provider. This is why it is <strong>Serverless</strong> not because there aren’t any servers, but because developers don’t have to own, rent or manage them. So they can focus on writing code without worrying about the underlying architecture.</p><p>Below we will briefly differentiate <strong>Serverless</strong> and <strong>Microservice.</strong></p><p><strong>Serverless</strong>:</p><ol><li><strong>Hosted </strong>— no need to think about provisioning of servers.</li><li><strong>Active</strong> — always active only when they are triggered thus reducing cost.</li><li><strong>Scalable</strong> — will scale automatically.</li></ol><p><strong>Microservice</strong>:</p><ol><li><strong>Independent</strong> — applications are broken down into independent services with their own process communicating through lightweight mechanisms.</li><li><strong>Always ON </strong>— services are always on compared to Serverless.</li><li><strong>Managed</strong> — Requires managing the underlying infrastructure including services and networking.</li></ol><p>And Finally the <strong>THREE TIER ARCHITECTURE</strong>:</p><p>Otherwise known as the <strong>Client — Server Architecture</strong> in which User Interface is the <strong>Presentation Tier.</strong></p><p><strong>Business Logic is the Application Tier</strong></p><p><strong>Database storage is the Database Tier.</strong></p><p><strong>Components:</strong></p><p><strong>Presentation Tier </strong>— user interface on our devices that provide interaction between software and the user.</p><p><strong>Application Tier</strong> — business logic or rules of the application. Where functions and calculations and connecting to the database.</p><p><strong>Database Tier</strong> — data management layer responsible for securing and retrieving application data.</p><p><strong>Benefits:</strong></p><p><strong>Scalability</strong> — each tier can be scaled independently allowing more cost effective and targeted scalability.</p><p><strong>Maintainability</strong> — making it easier to manage each tier independently</p><p><strong>Reusability </strong>— business rules can be reused by multiple front end applications.</p><p><strong>Flexibility </strong>— changes or upgrades in the technology without affecting the others tiers.</p><p>Organizations contemplating a move to either architectures need to investigate the trade-offs and invest in the necessary infrastructure, tools, and practices to manage the complexity of of either of these architectures. When correctly planned, implemented, and managed, it gives organizations the competence to create scalable, resilient, and agile applications that cater to the ever changing needs of modern enterprises.</p><p>===============================================================</p><p>Always good to have feedback, if any!</p><p>Add me up ( “ , ) Let’s Connect <a href="http://www.linkedin.com/in/ken-ong9090">www.linkedin.com/in/ken-ong9090</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b9c5ae78996" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Journey Into The Cloud (“ ,) Module 2.2 — Cloud Architecture]]></title>
            <link>https://medium.com/@ridlock/journey-into-the-cloud-module-2-2-cloud-architecture-f5a8b84d7c04?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5a8b84d7c04</guid>
            <category><![CDATA[basic-cloud]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[scalability]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Mon, 19 Aug 2024 20:17:39 GMT</pubDate>
            <atom:updated>2024-08-23T16:37:37.970Z</atom:updated>
            <content:encoded><![CDATA[<h3>Journey Into The Cloud (“ ,) Module 2.2 — Cloud Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*e-wOcqVcdFlFJ3IV.jpg" /></figure><p>How we should be designing our Cloud Architecture?</p><p><strong>System Design Principles</strong>: to ensure that the systems we are building meet users needs, are scalable, cost efficient, maintainable, efficient, and reliable.</p><ul><li><strong>Frontend</strong>: which consists of applications or IOT devices that users interact with and is responsible for sending requests (<strong><em>such as HTTP/HTTPS request</em></strong>) to the Backend to retrieve to data.</li><li><strong>Backend</strong>: this is where the business logic happens with the server and the database to process the request from the Frontend which sends back an appropriate response.</li><li><strong>Scaling</strong>: consists of vertical scaling (<strong><em>scaling up</em></strong>) which increases the processing power (<strong><em>more RAM, CPU, etc.</em></strong>) needed for the servers/instance to handle the web app workload and horizontal scaling (<strong><em>scaling out</em></strong>) which increases the number of servers/instance needed to handle the workload.</li><li><strong>Load Balancing</strong>: network traffic is distributed across multiple backend servers reducing a single server from overloading preventing server failure. The load balancer uses algorithm to evenly distribute traffic to each server which reduces downtime, and the load balancer helps prevent bottleneck on servers.</li><li><strong>High Availability</strong>: this ensures that the server is always available so that our system/application is always up for the users to access without any interruptions. The load balancer helps with this through the distribution of traffic to the servers, so if one server goes down the load balancer reroutes the traffic to another server helping to maintain high availability of our application.</li><li><strong>Fault Tolerance</strong>: this ensures that the system can still operate in the event of some of its components failing and this is done through redundancy. The system is designed with redundant components so if one fails another component can take over. Failovers are also used such as standby clusters that are switched to if the current system experiences failures.</li></ul><p>Below is one of the projects done in Cloud Academy wherein a basic diagram is made for a simple Cloud Architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*zn-W5BYTKP-RyIr1oqMT9A.jpeg" /></figure><p>Core Components of the diagram:</p><ol><li>Route 53 — routing traffic for your domain.</li><li>S3 Bucket — host your static website.</li><li>Elastic Load Balancer — load balance incoming traffic to your instances</li><li>Auto Scaling Group — Scale in / Scale out your instances in relation to the traffic the website receives.</li><li>Elasticache — a memory / cache to keep session records / data.</li><li>RDS Multi-AZ — A SQL Database used to store / retrieve user data/records.</li></ol><p>The architecture is that of a Retail website that is highly available and scalable which has an in-memory cache and its main database.</p><p>Data Flow is as follows towards the Database:</p><ol><li>S3 hosts the static website.</li><li>Clients/users request a certain item from the website, Route 53 routes their traffic accordingly to reach the site.</li><li>Traffic is then forwarded to the Load Balancer to regulate incoming requests. Which are then forwarded to available instances.</li><li>Instances will then check Elasticache if there is an available record/session and send back accordingly the data requested.</li><li>If in case no record was pulled from Elasticache then a request is sent to the RDS database to pull requested data to then be stored in Elasticache memory for a period of time.</li><li>This way, the database is not regularly accessed and frees it up for other required reads.</li></ol><p>Be aware of the different services available in each platform and how to interconnect them, this is only a prelude to what Cloud Architecture is. More to come…</p><p>===============================================================</p><p>Always good to have feedback, if any!</p><p>Add me up ( “ , ) Let’s Connect <a href="http://www.linkedin.com/in/ken-ong9090">www.linkedin.com/in/ken-ong9090</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5a8b84d7c04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Journey Into The Cloud (“ ,) Module 2.1 — What is Git?]]></title>
            <link>https://medium.com/@ridlock/journey-into-the-cloud-module-2-1-what-is-git-bf19318d661a?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf19318d661a</guid>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[simple-git]]></category>
            <category><![CDATA[repositories]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Sun, 18 Aug 2024 05:48:16 GMT</pubDate>
            <atom:updated>2024-08-23T16:39:25.658Z</atom:updated>
            <content:encoded><![CDATA[<h3>Journey Into The Cloud (“ ,) Module 2.1 — What is Git?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*GX44voZ86N2MRqBO.jpg" /></figure><p><strong>Why Git you ask?</strong></p><p>In simple terms, it tracks the history of changes (versions) when a team collaborates on a project together. Useful for debugging and understanding the evolution of a project.</p><p><strong>3 Types of Version Control</strong></p><ol><li><strong>Local Version Control</strong> — all tasks are stored on a single machine.</li><li><strong>Centralized Version Control</strong> — a centralized server repository where people can access data from and is easier to collaborate with team members. i.e. Subversion</li><li><strong>Distributed Version Control</strong> — a main server repository, where each person has their own working repository on their systems offering more collaboration and redundancy. i.e. GitHub</li></ol><p><strong>3 Best Practices in Version Control</strong></p><ol><li><strong>Writing commit messages</strong> — needs to be clear and descriptive to explain what has changed and why.</li><li><strong>Committing changes to a branch frequently</strong> — commit code as often as possible to avoid large and complicated changes in one go.</li><li><strong>Branching Strategy</strong> — always want to use branches effectively for feature development, bug fixes and experimentation.</li></ol><p><strong>What about Repositories?</strong></p><p>Think of it as a type of file system for a certain project wherein all the code changes (commits) are stored which is then organized into different branches to see its development.</p><p>Git repository also allows for: interaction with the history, cloning the repository, creating branches, committing, merging, comparing changes across versions of code, and more.</p><p>This is but only a quick summarization of what Git is. For more information it is always best to refer to their main articles —&gt; <a href="https://about.gitlab.com/topics/version-control/">What is version control? | GitLab</a> .</p><p>===============================================================</p><p>Always good to have feedback, if any!</p><p>Add me up ( “ , ) Let’s Connect <a href="http://www.linkedin.com/in/ken-ong9090">www.linkedin.com/in/ken-ong9090</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf19318d661a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Journey Into The Cloud (“ ,) Module 1]]></title>
            <link>https://medium.com/@ridlock/journey-into-the-cloud-module-1-e01e22269243?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/e01e22269243</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[software-development-life]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[sdlc]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Wed, 14 Aug 2024 19:13:35 GMT</pubDate>
            <atom:updated>2024-08-14T19:13:35.136Z</atom:updated>
            <content:encoded><![CDATA[<h3>Journey Into The Cloud (“ ,) Module 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/0*1beI_5M5WollF0lg" /></figure><p>Why the cloud?</p><ul><li><strong>Cost savings</strong>: It helps reduce IT costs.</li><li><strong>Security</strong>: It enhances security and data protection.</li><li><strong>Scalability</strong>: It allows for easy scaling up or down.</li><li><strong>Increased collaboration</strong>: It enables remote collaboration and access to centralized storage.</li><li><strong>Flexibility</strong>: It adapts to shifting customer needs.</li><li><strong>Innovation</strong>: It allows for faster time to market and incorporation of AI and machine learning.</li></ul><p>Types of Cloud Deployments:</p><p><strong>Public Cloud</strong> is cloud infrastructure available over the internet provided by cloud services providers such as AWS, Azure, and GCP are examples of public clouds. With Public Cloud, hardware, software and all underlying infrastructure are owned and managed by the Cloud Provider.</p><p><strong>Private Cloud</strong> is cloud engineering used by a single business or organization. Private clouds can be located physically on a company’s site data centers. Companies requiring private cloud also pay third-party providers to host their private cloud.</p><p><strong>Hybrid Cloud</strong> which combines public and private clouds, merged by technology, allowing data and applications to be shared. Hybrid cloud gives businesses flexibility, with more deployment options, and can optimize their infrastructure, security and compliance. It gives them the best of both worlds.</p><p><strong>Community Cloud </strong>allows systems and services to be accessible by a group of organizations. It is a distributed system that is created by integrating the services of different clouds to address the specific needs of a community, industry, or business. The infrastructure of the community could be shared between the organization which has shared concerns or tasks.</p><p><strong>Multi Cloud</strong> similar to the hybrid cloud deployment approach, which combines public and private cloud resources. Instead of merging private and public clouds, multi-cloud uses many public clouds. As a result, multi-cloud deployment improves the high availability of your services even more.</p><p>Types of Cloud Service Models:</p><p><strong>IAAS — Infrastructure as a Service </strong>is a virtual service over the internet, such as using Amazon EC2 or S3 storage. The cloud provider handles your hardware, servers, storage and other infrastructure.</p><p><strong>PAAS — Platform as a Service </strong>- Allows users to develop, run and maintain their applications without the requirements of managing the underlying infrastructure and configuration. So, you build your web app, and a cloud platform like AWS will handle everything else for you, such as scaling, maintenance, and patching. AWS Elastic Beanstalk is an example of PAAS.</p><p><strong>SAAS — Software as a Service </strong>- is software distribution where a third-party provider hosts applications and is available to users over the Internet, like renting out software licenses on a subscription model rather than buying it. An example of SaaS is using Netflix. You don’t own any of the content you watch, but you pay to watch it over the Internet on your devices.</p><p>What is <strong>Software Development Life Cycle (SDLC)</strong> ?</p><p>A process that development teams use to create awesome software that’s top-notch in terms of quality, cost-effectiveness, and time efficiency. This process is about creating a detailed plan to guide the development of the product and then breaking down the development process into smaller modules that can be assigned, completed, and measured to make the whole thing more manageable.</p><p><strong>The 7 Phases of the SDLC</strong></p><ol><li><strong>Planning and Analysis</strong></li></ol><p>The first phase of the SDLC is the project planning stage where you are gathering business requirements from your client or stakeholders. This phase is when you <a href="https://theproductmanager.com/topics/how-to-do-a-feasibility-study/">evaluate the feasibility of creating the product</a>, revenue potential, the cost of production, the needs of the end-users, etc.</p><p>2. <strong>Define Requirements</strong></p><p>This phase is critical for converting the information gathered during the planning and analysis phase into clear requirements for the development team.</p><p>3. <strong>Design</strong></p><p>Is where you put pen to paper. The original plan and vision are elaborated into a software design document (SDD) that includes the system design, programming language, templates, platform to use, and application security measures. This is also where you can flowchart how the software responds to user actions.</p><p>4. <strong>Development</strong></p><p>Where the development team members divide the project into software modules and turn the software requirement into code that makes the product. In some cases, the development stage can also merge with the testing stage where certain tests are run to ensure there are no critical bugs.</p><p>5. <strong>Testing</strong></p><p>Before getting the software product out the door to the production environment, it’s important to have your quality assurance team perform validation testing to make sure it is functioning properly and does what it’s meant to do. The testing process can also help hash out any major user experience issues and security issues.</p><p>6. <strong>Deployment</strong></p><p>Your final product is delivered to your intended user. You can automate this process and schedule your deployment depending on the type. For example, if you are only deploying a feature update, you can do so with a small number of users (canary release).</p><p>7. <strong>Maintenance</strong></p><p>Final stage of the SDLC if you’re following the <a href="https://theproductmanager.com/topics/agile-vs-waterfall-methodology/">waterfall</a> structure of the software development process. However, the industry is moving towards a more agile software development approach where maintenance is only a stage for further improvement.</p><p>In the maintenance stage, users may find bugs and errors that were missed in the earlier testing phase. These bugs need to be fixed for better user experience and retention. In some cases, these can lead to going back to the first step of the software development life cycle.</p><p><strong>Common SDLC Models — </strong>which arrange the development process in different ways. These models help organizations implement SDLC in an organized way.</p><ol><li><strong>AGILE Model</strong></li></ol><p>Arranges the SDLC phases into several development cycles, with the team delivering small, incremental software changes in each cycle. The Agile methodology is highly efficient, and rapid development cycles help teams identify issues early on, but overreliance on customer feedback could lead to excessive scope changes or project termination. It’s best for software development projects that <strong>require flexibility</strong> and the ability to adapt to change over time.</p><p>2. <strong>WATERFALL Model</strong></p><p>Arranges all the phases sequentially, with each new phase depending on the outcome of the previous one. It provides structure to project management, but there is little room for changes once a phase is complete.</p><p>3. <strong>ITERATIVE Model</strong></p><p>Team begins development with a small set of requirements and iteratively enhances versions until the software is ready for production. It’s easy to manage risks, but repeated cycles could lead to scope change and underestimation of resources.</p><p>4. <strong>SPIRAL Model</strong></p><p>Combines the iterative model’s repeated cycles with the waterfall model’s linear flow to prioritize risk analysis. It’s <strong>best for complex projects </strong>with frequent changes but can be expensive for smaller projects.</p><p>5. <strong>BIG BANG Model</strong></p><p>Unique approach where developers jump right into coding without much planning. This means that requirements are implemented as they come, without any kind of clear roadmap. If changes are needed, it can require a complete revamp of the software.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e01e22269243" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Journey into the Cloud (“ ,) Lets Start!]]></title>
            <link>https://medium.com/@ridlock/journey-into-the-cloud-lets-start-9a34387ca1bd?source=rss-3997b0aa7259------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a34387ca1bd</guid>
            <category><![CDATA[how-i-got-into-cloud]]></category>
            <category><![CDATA[cloud-engineer]]></category>
            <category><![CDATA[cloud-engineering-academy]]></category>
            <dc:creator><![CDATA[Ken Ong]]></dc:creator>
            <pubDate>Wed, 14 Aug 2024 16:57:22 GMT</pubDate>
            <atom:updated>2024-08-23T16:38:23.748Z</atom:updated>
            <content:encoded><![CDATA[<h3>Journey into the Cloud (“ ,) Lets Start!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u5jm5p3eAPlK_H7g.jpg" /></figure><p>Vaguely remembering the past wherein my interests were in games and the endless hours of going through them cartridge by cartridge then disc by disc till file by file. Later on in life it was always a wonder as how futuristic technology has advanced. Applications of all sorts can now be utilized in the palm of your hands making life somehow simpler and complex at the same time. Communication has widened so much that reaching out to someone can be done with the tip of your fingers on a small screen which is connected to a plethora of services/devices that not much people know about.</p><p>So it got me thinking, how does all this connect now? Diving deep it wasn’t only hardware that was working but in addition to it, a more sophisticated software / application driven focused architecture for the applications to be delivered to anyone around the world. The answer was “The Cloud”. Ever since the adoption of this, technology has skyrocketed with so many advancements especially in this age of machine learning and Artificial Intelligence.</p><p>Now I am not a Computer Science graduate but a Medical Technology graduate that was about to proceed into the field of Medicine. Alas, life happened and things changed. Postponed taking the licensure exam and threw me into the world of tech all at a whim. Back in the Philippines, Call Centers were the rage or go to place to earn a decent income and I believe it still is till now. I was in the hospitality business catering to hotel guests connection issues and troubleshooting truckers connection issues that were based in the US. Ah memories… Till finally Life came calling once again and I decided to finish taking the licensure exam and worked in the hospital Blood Bank for 2 years or so.</p><p>At the same time we also had a family business going on and next thing I know I was out of the medical field and now into managing a couple of convenience stores with a staff of around 50. The most enjoyment I got was tinkering at the devices if anything went wrong either hardware or software configuration. At this point databases and accounting software were being used which gave me an exposure to them. Now I was a previous medical student, with a little background of IT and account managements to reconciling books. Life couldn’t get any better right?</p><p>Again, Life came knocking and my wife and I decided to try our luck in Canada (Yes, I got married in between). It wasn’t easy starting out in a new country but that’s another story for later. Luckily got a job as an Admin Assistant but prior to getting it the position I applied for was for a Network Helpdesk (funny how things turn out). This was a small business so was pretty much hands on for everything. Life called again and told my Boss to train me to be a Real Estate Coordinator which then led me to getting a Real Estate License to sell Real Estate in Canada. Things were good, life was great. Then came COVID.</p><p>Fast forward to 2024, with a bit of time in my hands I finally decided to finish my CCNA (Cisco Certified Network Assurance). AWS CCP — Cloud Practitioner already done. Decided I needed a roadmap to become a Cloud Engineer and I have been subscribed to <a href="https://www.linkedin.com/in/soleyman-shahir-702a24b8/">Soleyman Shahir’s</a> <a href="https://www.youtube.com/@techwithsoleyman">Youtube Channel</a> for quite some time. So I decided to start this new journey into the cloud with help from <a href="https://www.linkedin.com/company/cloud-engineer-academy">Cloud Engineer Academy</a>.</p><p>Lets start…</p><p>===============================================================</p><p>Add me up ( “ , ) Let’s Connect <a href="http://www.linkedin.com/in/ken-ong9090">www.linkedin.com/in/ken-ong9090</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a34387ca1bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>