<?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 Sumedha Gamage on Medium]]></title>
        <description><![CDATA[Stories by Sumedha Gamage on Medium]]></description>
        <link>https://medium.com/@sumedhagamage?source=rss-98e293672f4d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xmpdWrswzmfVEKqzGJWsLQ.jpeg</url>
            <title>Stories by Sumedha Gamage on Medium</title>
            <link>https://medium.com/@sumedhagamage?source=rss-98e293672f4d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:03:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sumedhagamage/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[Holy Moly, One Year as a Co-founder CTO]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@sumedhagamage/holy-moly-one-year-as-a-co-founder-cto-a2374a78202c?source=rss-98e293672f4d------2"><img src="https://cdn-images-1.medium.com/max/1237/1*btEAxgHQa9Nupnyom8_6VA.png" width="1237"></a></p><p class="medium-feed-snippet">2020 was a dramatic year for all of us. Pandemic hits in all corners and changed lifestyle forever. We all had to re-caliber ourselves to&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@sumedhagamage/holy-moly-one-year-as-a-co-founder-cto-a2374a78202c?source=rss-98e293672f4d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@sumedhagamage/holy-moly-one-year-as-a-co-founder-cto-a2374a78202c?source=rss-98e293672f4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2374a78202c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[sri-lanka]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Sumedha Gamage]]></dc:creator>
            <pubDate>Mon, 26 Apr 2021 18:34:20 GMT</pubDate>
            <atom:updated>2021-04-26T18:34:20.061Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From Infrastructure as Code to Infrastructure is Code with AWS CDK]]></title>
            <link>https://medium.com/analytics-vidhya/from-infrastructure-as-code-to-infrastructure-is-code-with-aws-cdk-6f942af4eb87?source=rss-98e293672f4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f942af4eb87</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws-cdk]]></category>
            <category><![CDATA[aws-lambda-layer]]></category>
            <dc:creator><![CDATA[Sumedha Gamage]]></dc:creator>
            <pubDate>Sun, 14 Jun 2020 06:23:12 GMT</pubDate>
            <atom:updated>2020-07-06T04:21:16.125Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fskmf0uRIJE0QioRJYA8YA.png" /></figure><blockquote>I though I love YAML until I had to maintain more than 1000 line YAML to deploy AWS infrastructure.</blockquote><p>The declarative form is the best way to define and deploy cloud infrastructure until the platform gets complex. With the complexity of infrastructure, this will become the biggest nightmare. Its time to have some kind of abstraction on how we define our cloud infrastructure.</p><p>AWS CDK enables us to have infrastructure as part of the application code. That enables incremental changes and integrates with CI/CD pipeline. In the ever-changing ownership model of application development, deployment, and maintenance this can empower the application development team to manage its infrastructure in a more meaningful way.</p><blockquote>YBYO — You Build it You Own it</blockquote><p>YBYO is the way to have a smaller and effective team in the rapid development and maintenance of the application. AWS CDK enables the team to easily code the infrastructure and monitoring in the familiar development language. Especially no more giant YAML.</p><p>This article will demonstrate building a picture uploading application in AWS as showing in the following figure and monitoring with Cloudwatch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*qmcnE0Hj6Gz3_HIw8YOzMA.png" /></figure><p>Static web hosting in S3 and distribute via Cloufront to upload an image, API exposes through API Gateway, the route through Route53 DNS, listened by AWS Lamda that will save the picture to S3 and persist the metadata into DynamoDB. Lastly, wrap up with monitoring with Cloudwatch.</p><p>Let’s start with the project structure</p><pre>cdk init -l python #Generate CDK files<br>ng new ThumbnailMaker --style scss #Generate Angular front-end<br>mkdir code #Directory for labmda code<br>mkdir .layers #Directry to keep external dependecies for lambda function to create layers</pre><pre>#Some git clean up<br>cat ThumbnailMaker/.gitignore &gt;&gt; .gitignore<br>rm ThumbnailMaker/.gitingore</pre><pre>#Open VSCode<br>code .</pre><pre>#active venv <br>source .env/bin/activate<br>pip install -r requirement.txt</pre><p>Add the following dependencies in setup.py</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d029d87ae763a08d505a3529343bb40b/href">https://medium.com/media/d029d87ae763a08d505a3529343bb40b/href</a></iframe><p>We can have separate constructs for each service. In this case web_construct lambda_api_construct and route53.</p><p>web_contruct:</p><p>This will create s3 static web hosting for the Angular content. Get the binary from the angular project and upload it to S3. Connect Cloudfront CDN for S3 source, attach the certificate, and at the end create the Arecord in Route53.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1dedd15d0519b4533b8541e1b656183f/href">https://medium.com/media/1dedd15d0519b4533b8541e1b656183f/href</a></iframe><p>lambda_api_construct</p><p>CDK makes it easy to work with Lambda functions. Specially environment variables and grants for other AWS resources. A single line of code can take care of the creation of all IAM roles and policies.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a05810f7139498fc615689c4fabf9a5e/href">https://medium.com/media/a05810f7139498fc615689c4fabf9a5e/href</a></iframe><p>One of the critical features is how to inject third-party libraries to the runtime environment. In this case, I’m using Lambda Layers to create dependencies for the runtime environment.</p><pre>pip install request -t .layers</pre><pre>layer = _lambda.LayerVersion(self, “python-layer”, code=_lambda.Code.from_asset(“.layer”) )</pre><p>Finally the lambda function. It is a simple function to receive binary data from API Gateway and save the image into S3.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/09ec988bdb626d40bb94162ae463cb8d/href">https://medium.com/media/09ec988bdb626d40bb94162ae463cb8d/href</a></iframe><p>One note that LambdaRestApi creates a proxy in API Gateway. Even though CORS config been added to the CDK stack still lambda function should return the CORS headers for PROXY API Gateway type.</p><p>In the code, we can handle the state of our infrastructure as part of the application code. It can be versioned managed and can introduce incremental changes as the need for the application. No more cumbersome YAML. Application and infrastructure automation can be part of the same CI/CD pipeline that makes the developer’s life easy and faster adaptation to new changes.</p><p>then the stack</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/93749f1d5edeffea892ff2d77a25a76a/href">https://medium.com/media/93749f1d5edeffea892ff2d77a25a76a/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/554b95dc0f5cf5c73280e54b181b20d9/href">https://medium.com/media/554b95dc0f5cf5c73280e54b181b20d9/href</a></iframe><p>At last, let’s deploy the stack.</p><p>For third-party libraries, we can have separate requirement.txt file under .layers directory and run following to generate all third-party libraries</p><pre>pip install -r .layer/requrements.txt -t .layers</pre><p>then run build the angular project</p><pre>ng build</pre><p>If you have multiple profiles in AWS configuration use — profile to specify which profile to be used by CDK.</p><pre>cdk deploy --profile myprofile</pre><p>We will discuss how to build monitoring for this application in the next article. Till that have fun :).</p><p>source code: <a href="https://github.com/sumedha1101/cdk-stack-demo">https://github.com/sumedha1101/cdk-stack-demo</a></p><p>Thanks</p><p>Sumedha</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f942af4eb87" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analytics-vidhya/from-infrastructure-as-code-to-infrastructure-is-code-with-aws-cdk-6f942af4eb87">From Infrastructure as Code to Infrastructure is Code with AWS CDK</a> was originally published in <a href="https://medium.com/analytics-vidhya">Analytics Vidhya</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technology is not the biggest hurdle to overcome in Test Automation]]></title>
            <link>https://medium.com/@sumedhagamage/technology-is-not-the-biggest-hurdle-to-overcome-in-test-automation-f4bae51de2cf?source=rss-98e293672f4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4bae51de2cf</guid>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Sumedha Gamage]]></dc:creator>
            <pubDate>Thu, 12 Apr 2018 05:37:05 GMT</pubDate>
            <atom:updated>2018-04-12T06:03:54.056Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*odstHeuu4epA2Qe7bFVBXg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/3BK_DyRVf90?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel.com</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It is interesting to see how Test Automation plays a big role in software development life cycle. When organizations introduce Test Automation they follow common approaches.</p><blockquote>Cost Driven</blockquote><blockquote>Quality Driven</blockquote><blockquote>Time Driven</blockquote><blockquote>Technology Driven</blockquote><p>As we see most of the organizations follow the first category. Cost Driven approach.</p><blockquote>Test Automation will reduce the manual effort and that can save some bucks :).</blockquote><p>This is the worst approach to start with. Because the first approach will define the longterm goals, that is crucial to success in Test Automation. In Cost Driven approach, the team always focus on how to add more and more automation test and reduce the manual overhead. It will soon lead to a massive maintenance nightmare. This mindset blindside the basic aspect of Test Automation approach “What to Automate”.</p><p>Quality Driven approach by far the most favorable approach to start with but they can cost in other three categories.</p><blockquote>How to build a Test Automation framework that can capture all the bugs in the application code ?.</blockquote><p>This mindset definitely adds more cost, it can take more time to cover all the test cases and execution time can be lengthy also that will bring the technology dilemma. For an example, if we have three tire application what weight we gonna assign to each tier ?. Do we have to cover 100% test automation for UI and Service tier ? or can we give more weight to Service tier ?. Do we need to validate all bit and pieces in UI using automation?</p><p>Time-Driven approach comes in to picture with an Agile environment.</p><blockquote>How to release new change as fast as possible without breaking existing functionalities ?</blockquote><p>This mindset focus on what are the most crucial and critical functionalities to be tested. Finish all the development including manual and automation testing within the sprint. Integrating test automation in CI/CD pipeline and nightly execution can introduce third-party dependency as well. The quality will be compromised over the lifecycle time.</p><p>Technology-driven approach is controversial. Selecting correct tools can be a never-ending discussion.</p><blockquote>Can I use one tool and framework to automate all my needs ? or do I have to use multiple tools ?</blockquote><p>There are plenty of open source frameworks and tools can be used in Test Automation. There is no concept of “ Correct Tool” and definitely no one tool can handle all test automation needs. Easy to adopt, self-explanatory (can understand the test easily) and support multiple languages can be some good points to look when it comes to tool selection.</p><p>The biggest hurdle to overcome all these odds and implement a game-changing Test Automation is the “<strong>CULTURE</strong>”.</p><blockquote><strong>Cultural Driven Test Automation approach.</strong></blockquote><p>It should start as a Cultural change. All the stakeholders should align with Test Automation approach. Client, Architect, Developers, QA and Management should change their mindset to align with it. <strong>“Automatable Architecture”</strong> should be a design point for new applications. That can simplify the approach to Test Automation. Adaptation and continuous improvement within the team members can bring more and more value to the process. Test Automation code should be treated as important as application code. Continuous code quality inspection, unit test coverage, code review and all the best practice should be adhered by the Test Automation code implementation as well.</p><blockquote><strong>“Culture eats strategy for breakfast” — </strong>Peter Drucker</blockquote><p>If you still confused why Test Automation is not working then it’s time to change the CULTURE.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4bae51de2cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>