<?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 Buddhi Vikasitha on Medium]]></title>
        <description><![CDATA[Stories by Buddhi Vikasitha on Medium]]></description>
        <link>https://medium.com/@buddhiv?source=rss-b0c1de35f53f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6KIsPtmVgGxgytY0529q6Q.jpeg</url>
            <title>Stories by Buddhi Vikasitha on Medium</title>
            <link>https://medium.com/@buddhiv?source=rss-b0c1de35f53f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:45:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@buddhiv/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[My Pool of AWS SOA Resources]]></title>
            <link>https://buddhiv.medium.com/my-pool-of-aws-soa-resources-5c06e839e603?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c06e839e603</guid>
            <category><![CDATA[aws-cloudops-engineer]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[study]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 15:31:36 GMT</pubDate>
            <atom:updated>2026-11-15T15:33:06.574Z</atom:updated>
            <content:encoded><![CDATA[<p>List of resources that can be helpful in achieving the AWS CloudOps Engineer — Associate certification.</p><blockquote>As I recently achieved the AWS CloudOps Engineer — Associate certification, I thought it would be nice and wise to keep the resources noted down for my future references or for the reference of any other enthusiast of the same certification.</blockquote><blockquote><a href="https://www.credly.com/badges/79845d6f-cbba-40eb-88b3-01e31f83fcb1/public_url">https://www.credly.com/badges/79845d6f-cbba-40eb-88b3-01e31f83fcb1/public_url</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*InrmOGlU39YSdE4I7jFNOg.png" /></figure><h4>Main Course</h4><p>Main course I followed to cover up all the fundamentals.</p><ul><li><a href="https://www.udemy.com/course/aws-certified-cloudops-associate">https://www.udemy.com/course/aws-certified-cloudops-associate</a></li></ul><p>The course coordinator is a AWS associated trainer. The syllabus is well-covered in this.</p><h4>Mock Exams</h4><p>Following mock exams set provide the exam experience.</p><ul><li><a href="https://www.udemy.com/course/practice-exams-aws-certified-cloudops-engineer">https://www.udemy.com/course/practice-exams-aws-certified-cloudops-engineer</a></li><li><a href="https://skillcertpro.com/product/aws-cloudops-engineer-associate-exam-questions/">https://skillcertpro.com/product/aws-cloudops-engineer-associate-exam-questions/</a></li></ul><h4>Helpful Content</h4><p>AWS cheat sheets.</p><ul><li><a href="https://tutorialsdojo.com/aws-cheat-sheets/">https://tutorialsdojo.com/aws-cheat-sheets/</a></li></ul><p>Last but not the least, the AWS documentation.</p><ul><li><a href="https://docs.aws.amazon.com/">https://docs.aws.amazon.com/</a></li></ul><p>Drop a response and let everyone know about any important resources that you find helpful for the AWS SOA certification.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c06e839e603" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setup a Code Quality Checker in Your Project Today]]></title>
            <link>https://javascript.plainenglish.io/setup-a-code-quality-checker-in-your-project-today-5bca7f16484d?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bca7f16484d</guid>
            <category><![CDATA[code-quality]]></category>
            <category><![CDATA[sonarqube]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[sonar]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 13:36:11 GMT</pubDate>
            <atom:updated>2026-01-12T06:58:47.491Z</atom:updated>
            <content:encoded><![CDATA[<p>explaining why it is important using my experience with SonarQube for years.</p><p>I am compiling a list of pointers about using code quality checkers in software development and explain them from my experience.</p><blockquote>Disclaimer: I will mostly explain my experience using SonarQube but there are a lot of alternatives out there for you to check out.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*brpd3E_gDw5RaC-nw7iySg.png" /></figure><p><strong>1 Code Quality Checkers in Software development are important tools that play a huge role in detecting possible issues in code. But usually, our projects have no Code Quality Checker because we do not understand their importance.</strong></p><p>You may have heard of SonarQube, Codacy, Veracode, etc. which are popular tools for code quality checking. These are crucial for detecting bugs early, improving code readability and maintainability, and reducing technical debt in the projects. Ultimately saving time and money in the long run by catching issues before they become costly problems in real runs in production.</p><ul><li>Improving code quality by detecting common mistakes and anti patterns. Also, they eliminate bad code by pointing out idle imports, declarations and duplicates.</li><li>Finds errors and security flaws early in development and prevent major issues later.</li><li>Standardized and mistake-free code enhance better collaboration between developers.</li><li>Fixing an issue earlier in the software development process mean time and cost savings.</li><li>Reduced technical debt help plan more features that actually benefit the stakeholders and the application itself.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_FlO2Bq2Zfwmy6Ek8NddQ.png" /></figure><p><strong>2 Based on the nature on the project and your budget, the tool that we are going to use can be subjective. Do a little research beforehand.</strong></p><p>You do not need to go to the same popular code quality checker all the time. There are multiple products out there that can help check your code quality.</p><ul><li>Check if you can reach the pricing tiers with your needs. Usually the tools check for the number of lines in the repository, amount of repositories, etc.</li><li>Do not excessively grant permissions for members that do not need access. Eg: Quality assurance, delivery manager., etc.</li><li>Check what configuration you need in your software delivery process such as CI/CD integration.</li><li>Explore if the types of code quality checks match your need. They can offer static code analysis, vulnerability analysis, test coverage analysis, etc.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gDCSqopx5qiTV2dV3kM07Q.png" /></figure><p><strong>3 Get and understanding of the configuration in the tool and tailor them according to your needs.</strong></p><p>There are different configuration in each tool and you can fix them according to your project nature. For example, in SonarQube we can create quality gates, switch rulesets and define our own quality standard in the tool.</p><ul><li>Unwanted quality checks are not needed. They result in over-engineering your code.</li><li>We can define custom rulesets if the default ones do not cater to our requirement, so exploring the available options is surely needed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s1FefK4H9Aujswi3K5B9Eg.png" /></figure><p><strong>4 Setup the tool for all your repositories. Think about improving the quality of all the components in your system.</strong></p><p>In my experience, I strongly advice against only scanning your code in only a few of your components. This is just a buildup of the overall technical debt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VmkyYTAuYxkgeRwfDIrHkw.png" /></figure><p><strong>5Ignoring code smells can do more harm than we think. Fixing them as early as possible is beneficial in the long term. Its easy to not introduce them than to fix them in future iterations.</strong></p><p>Technical debt is the added cost of future rework caused by choosing a quick, easy solution instead of a better, more robust approach. Technical debt may accumulate due to intentional decisions as well as unintentional decisions. By having a code quality checker tool we will be notified of places where technical debt may accumulate.</p><p><strong><em>Remember that this will not help you get rid of all the technical debt in your code.</em></strong></p><p>What kind of code quality indicators can lead to technical debt in my code?</p><ul><li>Unwanted imports, making your bundle size large.</li><li>Dependancies, methods close to deprecation.</li><li>Increased cognitive complexity of functions, slowing down the execution for advanced logic.</li><li>Version indicators with wildcards. These will update your dependancies into unknown future versions with broken changes.</li><li>Application vulnerabilities, exposing your application. You will have a hard time if your application is attacked.</li><li>Anti patterns, proven for their disadvantages will affect your system stability and performance.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pw2GayLXO0OkEAVnjVjzig.png" /></figure><p><strong>6 Best way to integrate a code quality check is to automate it within the deployment pipelines.</strong></p><p>I have worked in projects where SonarQube was configured in different ways and I personally find when the quality checker is configured in the CI/CD with no skip options it yields best results. We also had forced SonarQube quality check to be passed before proceeding to merge with any pull request.</p><p>This made sure that no new code was pushed to the main branches without a successful analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UqlwF3j21147uma2DeJ2JQ.png" /></figure><p><strong>7 Code quality enhance engineer collaboration and application presence. These are the indirect impacts of maintaining good code quality.</strong></p><p>Developers love good code. They find it interesting to work on repositories that mirror great quality and attention to detail. This is another reason that we need to make our repositories clean.</p><p>Also, good code means less bugs, more performance and smooth experience. Stakeholders love it when our systems return with less issues. Maintaining good code quality can have so many good returns like this.</p><p><strong><em>I am an AWS, Linux and Scrum Master certified Software Engineer at Fcode Labs (Pvt) Ltd. I am interested in all the ways to make software development better.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bca7f16484d" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/setup-a-code-quality-checker-in-your-project-today-5bca7f16484d">Setup a Code Quality Checker in Your Project Today</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Styling AWS Cognito Managed Login with ‘Own’ Branding]]></title>
            <link>https://aws.plainenglish.io/styling-aws-cognito-managed-login-with-own-branding-703d3e9c9380?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/703d3e9c9380</guid>
            <category><![CDATA[oauth2]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cognito]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[web-app-development]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 05:14:19 GMT</pubDate>
            <atom:updated>2026-01-12T07:14:23.878Z</atom:updated>
            <content:encoded><![CDATA[<p>and automate it with AWS CDK.</p><h4>AWS Cognito</h4><p>AWS Cognito is one os the hundreds of AWS services which is used for user sign-up, sign-in, and access control in applications. It is a a fully managed identity service that can provide a secure user directory, authentication server, and authorization service, allowing you to easily add features like social logins, MFA, and custom branding.</p><p>Cognito can provide all the above while scaling to millions of users and providing top security. This has been a popular choice between application developers for the versatility it provide.</p><p>Cognito can be used with web apps, mobile apps, desktop apps, etc. One way that the application developers configure Cognito in their applications is the OAuth2 Authorization Code Flow. This redirects the application user to the Cognito login page and redirects the user back to the application after a successful login. The application trusts the Cognito service for its services and depends on its security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*rcyddzMFw9ksjLxz.png" /><figcaption>Image from <a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/choose-an-amazon-cognito-authentication-flow-for-enterprise-applications.html">https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/choose-an-amazon-cognito-authentication-flow-for-enterprise-applications.html</a></figcaption></figure><p>These are the advantages that Cognito bring:</p><ol><li>The application developers do not have to implement everything in the login flow. Cognito handles most of the flow, verifying users against their credentials and storing the available login information on the service.</li><li>Cognito is scalable. It can support millions of users at once without issue.</li><li>Cognito supports OAuth2 authentication.</li><li>Supports other features like multi factor authentication, reset/forget password, user registration, password strength controls, etc. which can control additional security of the application.</li><li>Application developers can integrate Cognito with other AWS services (Eg: AWS Lambda) for advanced use cases.</li></ol><h4>AWS Cognito Default Login Page</h4><p>If an application is configured with Cognito, the user will be redirected to the AWS Cognito provided login page for the application credentials. The default login page will look something like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RHD6K8MzKcsw6AcTeSCa2w.png" /></figure><p>Usually application developers want their login page to contain branding information such as logos, theme colors, etc. Lets see how we can achieve that with AWS Cognito.</p><h4>AWS CDK</h4><p>First, lets explore the AWS CDK script to create a Cognito client.</p><p>AWS CDK, (AWS Cloud Development Kit)<strong> </strong>is an open-source framework that allows you to define cloud infrastructure using familiar programming languages. AWS CDK can provision resources in AWS CloudFormation, but provides a higher level of abstraction for the developers to control the resources using common programming languages such as TypeScript, Python, Java, etc.</p><p>Since AWS Cognito can be provisioned through AWS CloudFormation and is supported by AWS CDK we can define our Cognito resources as follows.</p><pre>// Code to setup user pool and app client<br><br>import * as cdk from &quot;aws-cdk-lib&quot;;<br>import { Construct } from &quot;constructs&quot;;<br>import * as cognito from &quot;aws-cdk-lib/aws-cognito&quot;;<br><br>interface CognitoPoolsStackProps extends cdk.StackProps {<br>  applicationDomain: string;<br>}<br><br>export class CognitoPoolsStack extends cdk.Stack {<br>  constructor(scope: Construct, id: string, props: CognitoPoolsStackProps) {<br>    super(scope, id, props);<br><br>    const newUserPool: cognito.UserPool = new cognito.UserPool(this, &quot;UserPool&quot;, {<br>      userPoolName: &quot;my-user-pool&quot;,<br>      selfSignUpEnabled: false,<br>      signInAliases: {<br>        email: true,<br>        username: false,<br>      },<br>      autoVerify: { email: true },<br>      standardAttributes: {<br>        email: {<br>          required: true,<br>          mutable: false,<br>        },<br>      },<br>      passwordPolicy: {<br>        minLength: 12,<br>        requireLowercase: true,<br>        requireUppercase: true,<br>        requireDigits: true,<br>        requireSymbols: true,<br>        passwordHistorySize: 5,<br>      },<br>      mfa: cognito.Mfa.REQUIRED,<br>      mfaSecondFactor: {<br>        sms: false,<br>        otp: true,<br>      },<br>    });<br>    <br>    newUserPool.addClient(&quot;my-app-client&quot;, {<br>      accessTokenValidity: cdk.Duration.minutes(5),<br>      idTokenValidity: cdk.Duration.minutes(5),<br>      refreshTokenValidity: cdk.Duration.hours(12),<br>      userPoolClientName: &quot;my-user-pool&quot;,<br>      authFlows: {<br>        userSrp: true,<br>        userPassword: true,<br>        adminUserPassword: true,<br>      },<br>      generateSecret: true,<br>      enableTokenRevocation: true,<br>      preventUserExistenceErrors: true,<br>      oAuth: {<br>        callbackUrls: [`https://${props.applicationDomain}/login-handler/`],<br>        logoutUrls: [`https://${props.applicationDomain}/login/`],<br>        flows: {<br>          authorizationCodeGrant: true,<br>        },<br>        scopes: [cognito.OAuthScope.OPENID, cognito.OAuthScope.COGNITO_ADMIN],<br>      },<br>    });<br>  }<br>}</pre><p>An AWS Cognito User Pool is a managed user directory and identity service for client applications.</p><p>An AWS Cognito App Client is a unique resource within a the Cognito User Pool that represents a specific application congifuration, acting as the face of the secure connection point. The users can interact with the App Client’s interface to sign up, sign in, and then receive tokens for authentication and authorization.</p><p>Visiting the AWS Cognito App Clients list and selecting the newly created app client will allow the developers to manage the login page styles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zd2EyPZpkkOgU6E2v9pv_w.png" /></figure><p>The style options will not be 100% flexible but it provide a decent set of options to control the page appearance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZVlq1L9GVnAQ4n58yc7mw.png" /></figure><p>We can change the styles in the style options but lets see how we can use AWS CDK to change the styles.</p><h4>AWS CDK script</h4><p>First define the Cognito branding configuration in our code. Cognito branding config require two main options to be defined, <strong>assets</strong> and <strong>settings</strong>.</p><p><em>More on the branding options can be found in the </em><a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-cognito-managedloginbranding.html#cfn-cognito-managedloginbranding-settings"><strong><em>AWS documentation</em></strong></a><em>.</em></p><pre>// Managed login branding assets and settings<br><br>export const managedLoginBrandingAssets = [<br>  {<br>    bytes: PAGE_FOOTER_LOGO_BASE64,<br>    category: &quot;PAGE_FOOTER_LOGO&quot;,<br>    colorMode: &quot;LIGHT&quot;,<br>    extension: &quot;PNG&quot;,<br>  },<br>  {<br>    bytes: PAGE_HEADER_LOGO_BASE64,<br>    category: &quot;PAGE_HEADER_LOGO&quot;,<br>    colorMode: &quot;LIGHT&quot;,<br>    extension: &quot;PNG&quot;,<br>  }<br>];<br><br>export const managedLoginBrandingSettings = {<br>  categories: {<br>    form: {<br>      displayGraphics: true,<br>      instructions: {<br>        enabled: false,<br>      },<br>      languageSelector: {<br>        enabled: false,<br>      },<br>      location: {<br>        horizontal: &quot;CENTER&quot;,<br>        vertical: &quot;CENTER&quot;,<br>      },<br>      sessionTimerDisplay: &quot;NONE&quot;,<br>    },<br>    global: {<br>      colorSchemeMode: &quot;LIGHT&quot;,<br>      pageFooter: {<br>        enabled: true,<br>      },<br>      pageHeader: {<br>        enabled: true,<br>      },<br>      spacingDensity: &quot;REGULAR&quot;,<br>    },<br>  },<br>  componentClasses: {<br>    buttons: {<br>      borderRadius: 4,<br>    },<br>    focusState: {<br>      darkMode: {<br>        borderColor: &quot;304166ff&quot;,<br>      },<br>      lightMode: {<br>        borderColor: &quot;304166ff&quot;,<br>      },<br>    },<br>    input: {<br>      borderRadius: 4,<br>      darkMode: {<br>        defaults: {<br>          backgroundColor: &quot;ffffffff&quot;,<br>          borderColor: &quot;C5C7CCff&quot;,<br>        },<br>        placeholderColor: &quot;5C5F65ff&quot;,<br>      },<br>      lightMode: {<br>        defaults: {<br>          backgroundColor: &quot;ffffffff&quot;,<br>          borderColor: &quot;C5C7CCff&quot;,<br>        },<br>        placeholderColor: &quot;5C5F65ff&quot;,<br>      },<br>    },<br>  },<br>  components: {<br>    primaryButton: {<br>      darkMode: {<br>        defaults: {<br>          backgroundColor: &quot;304166ff&quot;,<br>          textColor: &quot;ffffffff&quot;,<br>        },<br>        hover: {<br>          backgroundColor: &quot;033160ff&quot;,<br>          textColor: &quot;ffffffff&quot;,<br>        },<br>        active: {<br>          backgroundColor: &quot;033160ff&quot;,<br>          textColor: &quot;ffffffff&quot;,<br>        },<br>        disabled: {<br>          backgroundColor: &quot;ffffffff&quot;,<br>          borderColor: &quot;ffffffff&quot;,<br>        },<br>      },<br>      lightMode: {<br>        defaults: {<br>          backgroundColor: &quot;304166ff&quot;,<br>          textColor: &quot;ffffffff&quot;,<br>        },<br>        hover: {<br>          backgroundColor: &quot;033160ff&quot;,<br>          textColor: &quot;ffffffff&quot;,<br>        },<br>        active: {<br>          backgroundColor: &quot;033160ff&quot;,<br>          textColor: &quot;ffffffff&quot;,<br>        },<br>        disabled: {<br>          backgroundColor: &quot;ffffffff&quot;,<br>          borderColor: &quot;ffffffff&quot;,<br>        },<br>      },<br>    },<br>    secondaryButton: {<br>      darkMode: {<br>        defaults: {<br>          backgroundColor: &quot;ffffffff&quot;,<br>          borderColor: &quot;304166ff&quot;,<br>          textColor: &quot;304166ff&quot;,<br>        },<br>        hover: {<br>          backgroundColor: &quot;f2f8fdff&quot;,<br>          borderColor: &quot;033160ff&quot;,<br>          textColor: &quot;033160ff&quot;,<br>        },<br>        active: {<br>          backgroundColor: &quot;d3e7f9ff&quot;,<br>          borderColor: &quot;033160ff&quot;,<br>          textColor: &quot;033160ff&quot;,<br>        },<br>      },<br>      lightMode: {<br>        defaults: {<br>          backgroundColor: &quot;ffffffff&quot;,<br>          borderColor: &quot;304166ff&quot;,<br>          textColor: &quot;304166ff&quot;,<br>        },<br>        hover: {<br>          backgroundColor: &quot;f2f8fdff&quot;,<br>          borderColor: &quot;033160ff&quot;,<br>          textColor: &quot;033160ff&quot;,<br>        },<br>        active: {<br>          backgroundColor: &quot;d3e7f9ff&quot;,<br>          borderColor: &quot;033160ff&quot;,<br>          textColor: &quot;033160ff&quot;,<br>        },<br>      },<br>    },<br>    pageBackground: {<br>      darkMode: {<br>        color: &quot;f5f7f9ff&quot;,<br>      },<br>      image: {<br>        enabled: false,<br>      },<br>      lightMode: {<br>        color: &quot;f5f7f9ff&quot;,<br>      },<br>    },<br>    pageFooter: {<br>      backgroundImage: {<br>        enabled: false,<br>      },<br>      darkMode: {<br>        background: {<br>          color: &quot;69bbe9ff&quot;,<br>        },<br>        borderColor: &quot;d5dbdbff&quot;,<br>      },<br>      lightMode: {<br>        background: {<br>          color: &quot;69bbe9ff&quot;,<br>        },<br>        borderColor: &quot;d5dbdbff&quot;,<br>      },<br>      logo: {<br>        enabled: true,<br>        location: &quot;CENTER&quot;,<br>      },<br>    },<br>  },<br>};</pre><p>Next, we modify the class that will create the user pool and app client. After the creation of the user pool and app client, we initiate the BrandingConstruct to set the branding configuration.</p><pre>// Code to setup user pool and app client<br><br>import * as cdk from &quot;aws-cdk-lib&quot;;<br>import { Construct } from &quot;constructs&quot;;<br>import * as cognito from &quot;aws-cdk-lib/aws-cognito&quot;;<br>import { CognitoBrandingConstruct } from &quot;./cognito-branding-construct&quot;;<br><br>interface CognitoPoolsStackProps extends cdk.StackProps {<br>  applicationDomain: string;<br>}<br><br>export class CognitoPoolsStack extends cdk.Stack {<br>  constructor(scope: Construct, id: string, props: CognitoPoolsStackProps) {<br>    super(scope, id, props);<br><br>    const newUserPool: cognito.UserPool = new cognito.UserPool(this, &quot;UserPool&quot;, {<br>      userPoolName: &quot;my-user-pool&quot;,<br>      selfSignUpEnabled: false,<br>      signInAliases: {<br>        email: true,<br>        username: false,<br>      },<br>      autoVerify: { email: true },<br>      standardAttributes: {<br>        email: {<br>          required: true,<br>          mutable: false,<br>        },<br>      },<br>      passwordPolicy: {<br>        minLength: 12,<br>        requireLowercase: true,<br>        requireUppercase: true,<br>        requireDigits: true,<br>        requireSymbols: true,<br>        passwordHistorySize: 5,<br>      },<br>      mfa: cognito.Mfa.REQUIRED,<br>      mfaSecondFactor: {<br>        sms: false,<br>        otp: true,<br>      },<br>    });<br>    <br>    const newAppClient = newUserPool.addClient(&quot;my-app-client&quot;, {<br>      accessTokenValidity: cdk.Duration.minutes(5),<br>      idTokenValidity: cdk.Duration.minutes(5),<br>      refreshTokenValidity: cdk.Duration.hours(12),<br>      userPoolClientName: &quot;my-user-pool&quot;,<br>      authFlows: {<br>        userSrp: true,<br>        userPassword: true,<br>        adminUserPassword: true,<br>      },<br>      generateSecret: true,<br>      enableTokenRevocation: true,<br>      preventUserExistenceErrors: true,<br>      oAuth: {<br>        callbackUrls: [`https://${props.applicationDomain}/login-handler/`],<br>        logoutUrls: [`https://${props.applicationDomain}/login/`],<br>        flows: {<br>          authorizationCodeGrant: true,<br>        },<br>        scopes: [cognito.OAuthScope.OPENID, cognito.OAuthScope.COGNITO_ADMIN],<br>      },<br>    });<br><br>    // Create Construct to do branding<br>    new CognitoBrandingConstruct(this, &quot;CognitoBranding&quot;, {<br>      userPool: newUserPool.userPoolId,<br>      appClientId: newAppClient.userPoolClientId,<br>    });<br>  }<br>}</pre><p>Class to set the branding configuration.</p><pre>// Code to set branding<br><br>import * as cognito from &quot;aws-cdk-lib/aws-cognito&quot;;<br>import { Construct } from &quot;constructs&quot;;<br>import {<br>  managedLoginBrandingAssets,<br>  managedLoginBrandingSettings,<br>} from &quot;./common&quot;;<br><br>export interface CognitoBrandingConstructProps {<br>  userPoolId: string;<br>  appClientId: string;<br>}<br><br>export class CognitoBrandingConstruct extends Construct {<br>  constructor(<br>    scope: Construct,<br>    id: string,<br>    props: CognitoBrandingConstructProps<br>  ) {<br>    super(scope, id);<br><br>    // Create managed login branding for app client with the given ID<br>    new cognito.CfnManagedLoginBranding(this, `ManagedLoginBranding`, {<br>      userPoolId: props.userPoolId,<br>      clientId: props.appClientId,<br>      useCognitoProvidedValues: false,<br>      assets: managedLoginBrandingAssets,<br>      settings: managedLoginBrandingSettings,<br>    });<br>  }<br>}</pre><p>This will set the AWS Cognito App Client branding in your application after your next resource deployment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eMi7PUjfOQWUJeb1Z59rnw.png" /></figure><p>Our approach makes sure of the following:</p><ol><li>Cognito branding is manual since the default login page is something that AWS setup for us. With the AWS CDK script, the app clients do not need the manual setup every time.</li><li>Easy to track changes through code.</li><li>We still get the AWS Cognito existing features and its security, scalability and robustness through this approach.</li></ol><p><strong><em>I am an AWS, Linux and Scrum Master certified Software Engineer at Fcode Labs (Pvt) Ltd. I am interested in all the ways to make software development better.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=703d3e9c9380" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/styling-aws-cognito-managed-login-with-own-branding-703d3e9c9380">Styling AWS Cognito Managed Login with ‘Own’ Branding</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Idempotent APIs Explained]]></title>
            <link>https://javascript.plainenglish.io/idempotent-apis-explained-013ab5bf9ae2?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/013ab5bf9ae2</guid>
            <category><![CDATA[scalable-architecture]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[idempotency]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[api-design]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Fri, 05 Sep 2025 19:58:25 GMT</pubDate>
            <atom:updated>2025-09-15T00:27:41.677Z</atom:updated>
            <content:encoded><![CDATA[<h4>The secret ingredient for writing reliable APIs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5wrYZkkVXHO4nDQJdcmcBw.jpeg" /></figure><p>Idempotency in APIs is one of those subtle but super important software engineering concepts.</p><p><em>No idea?</em> Lets look at the meaning of the word <strong><em>Idempotency</em></strong> first.</p><blockquote>Idempotency is the property of an operation where executing it multiple times produces the same result as executing it once. — Google</blockquote><p>In software engineering terms, idempotency can be described as follows.</p><blockquote>An HTTP method is <strong>idempotent</strong> if the intended effect on the server of making a single request is the same as the effect of making several identical requests. — MDN</blockquote><p>Basically, an operation is idempotent, if it generates the same outcome if performed multiple times.</p><p>In APIs,</p><ul><li>If a client sends the <strong>same request multiple times</strong>, the result should not change between requests.</li><li>The same response may be returned multiple times, but the <strong>state of the system shall remain consistent</strong>.</li></ul><h3>Examples for Idempotency</h3><p>Where idempotency is present:</p><ul><li>GET — /api/user/2 — No matter how many times we fetch the user with id: 2, the result is always the same, and the state of the database should not be changed.</li><li>DELETE — /api/user/2 — No matter how many times we perform a delete operation for the user with the id: 2, the user should deleted after the first call and stay deleted.</li><li>If we need to turn a configuration off through an API, no matter how many times that we call the API to turn the configuration off, the value should always be off.</li></ul><p>In the following cases we do not see idempotency:</p><ul><li>POST — /api/user — Each request will save a new user to the database.</li><li>If there is an API to increment a value in the database, multiple calls will continue to change the value in the database. Thus not making it idempotent.</li></ul><h3>The Importance of Idempotency</h3><p>Lets look at why idempotency is important and why engineers focus a lot in this area.</p><ul><li><strong>API Reliability</strong> — APIs should always perform what they are intended to do. If an API that is not supposed to alter data in the database alters data, we end up with a problematic state in the database.</li><li><strong>Scalability</strong> — Modern application sit behind complex architecture comprised of load balancers, and distributed systems. In these architectures, event based communication and retries are common. Also, some resources are shared across multiple other resources (Ex: databases). We have to design our APIs such that we avoid the side effects of retries, shared resources, etc.</li><li><strong>User experience</strong> — User experience is something that matter most in modern applications. If a user’s action is repeated due to a slow response or an accidental retry, we should prevent any negative effects.</li></ul><h3>Example</h3><p>Lets look at the following examples.</p><h4>Example 1</h4><pre>const setSwitch () {<br>  const currentValue = getCurrentValue();<br>  const newValue = await setNewValue(!currentValue);<br><br>  return newValue;<br>}</pre><h4>Example 2</h4><pre>const setSwitch (value) {<br>  const newValue = await setNewValue(value);<br><br>  return newValue;<br>}</pre><p>We can see that, the code in example 1 is not idempotent. Multiple retries can definitely make the database end up with an indeterministic state.</p><p>But the code in example 2 is idempotent. The database state always end up in the same state even if there are multiple retries.</p><p><strong><em>Just like no matter how much you try to switch a light bulb off, it should stay off at the end.</em></strong></p><h4>How Do We Achieve Idempotency?</h4><p>Lets look at what to remember.</p><ul><li><strong>Careful Logic</strong> — Like in the previous example, always make sure that the logic does not do anything that it is not supposed to do.</li><li><strong>Careful Design</strong> — Note that some HTTP methods are meant to safeguard the idempotency.<br>- GET for example, should not alter the database state.<br>- DELETE should always return the same after the first call.<br>- PUT should also end up returning the same result when given same input.<br>- POST can have no idempotency.</li><li><strong>Idempotency Keys</strong> — A new HTTP header called Idempotency-Key is used by complex applications to maintain the quality between retries. One of the main applications that have this adapted is Stripe, that recognise duplicate requests to avoid charging users multiple times.</li></ul><p>In summary, regardless of what language and framework that we use, we should always make sure that we follow idempotency as necessary in building our logic and API design. This is something that makes any application a great application.</p><p><strong><em>I am an AWS, Linux and Scrum Master certified Software Engineer at Fcode Labs. I am interested in all the ways to make software development better. Please stop by the website </em></strong><a href="https://buddhiv.io/"><strong><em>buddhiv.io</em></strong></a><strong><em> to see my profile.</em></strong></p><h3>A message from our Founder</h3><p><strong>Hey, </strong><a href="https://linkedin.com/in/sunilsandhu"><strong>Sunil</strong></a><strong> here.</strong> I wanted to take a moment to thank you for reading until the end and for being a part of this community.</p><p>Did you know that our team run these publications as a volunteer effort to over 3.5m monthly readers? <strong>We don’t receive any funding, we do this to support the community. ❤️</strong></p><p>If you want to show some love, please take a moment to <strong>follow me on </strong><a href="https://linkedin.com/in/sunilsandhu"><strong>LinkedIn</strong></a><strong>, </strong><a href="https://tiktok.com/@messyfounder"><strong>TikTok</strong></a>, <a href="https://instagram.com/sunilsandhu"><strong>Instagram</strong></a>. You can also subscribe to our <a href="https://newsletter.plainenglish.io/"><strong>weekly newsletter</strong></a>.</p><p>And before you go, don’t forget to <strong>clap</strong> and <strong>follow</strong> the writer️!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=013ab5bf9ae2" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/idempotent-apis-explained-013ab5bf9ae2">Idempotent APIs Explained</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serverless Framework v4 Offline with Lambda]]></title>
            <link>https://buddhiv.medium.com/serverless-framework-v4-offline-with-lambda-5d4ddaf5e66f?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d4ddaf5e66f</guid>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[serverless-framework]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Thu, 04 Sep 2025 18:11:35 GMT</pubDate>
            <atom:updated>2025-09-04T18:11:35.695Z</atom:updated>
            <content:encoded><![CDATA[<h4>AWS with Serverless Framework v4.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*imiMtL_B6C-R2IdrwZ2Vgw.png" /></figure><p>The Serverless Framework helps you develop and deploy AWS infrastructure. You can start reading and development with Serverless Framework from the below link if you are not familiar with the stack. 👇</p><p><a href="https://www.serverless.com/framework/docs">Serverless Framework Documentation</a></p><p>If you are coming from a different Serverless version, visit this link to see what is new. 👇</p><p><a href="https://www.serverless.com/blog/serverless-framework-v4-a-new-model">Serverless Framework V4: A New Model</a></p><blockquote>New Serverless Framework v4 guarantees absolutely no breaking changes even though it has a number of new changes compared with v3.</blockquote><p>The Serverless Framework provides us a lot of flexibility in building AWS infrastructure.</p><ul><li><strong>Almost all the possible configuration options and different commands to run, deploy, verify the stack.</strong></li><li><strong>Fast development with less time spent on infrastructure management.</strong></li><li><strong>Ability to run the stack offline while development.</strong></li><li><strong>Language agnostic development support.</strong></li><li><strong>Wide community support.</strong></li></ul><p>I am going to build an infrastructure which consists of AWS Lambda and show you the configuration.</p><p>Lets get to work.</p><h4>Setup the environment and the Serverless Framework</h4><p>Assuming that you have npm and nodejs setup, lets first install Serverless Framework and start setting up the project.</p><pre>npm i serverless -g<br>serverless # or &quot;sls&quot; for short to start creating the project</pre><p>The command serverless will start setting your project up. For more information you can visit this <a href="https://www.serverless.com/framework/docs/getting-started/">link</a>. Following is the default serverless.yml file.</p><pre>org: my-org<br>app: my-app<br>service: my-service<br><br>provider:<br>  name: aws<br>  runtime: nodejs20.x<br><br>functions:<br>  hello:<br>    handler: handler.hello<br>    events:<br>      - httpApi:<br>          path: /<br>          method: get</pre><h4>Run sample Lambda function</h4><p>Run serverless dev to run the code in the dev mode. This will bundle our functions and deploy them into our account, exposing the endpoint to access them.</p><pre>Dev ϟ Mode<br><br>Dev Mode redirects live AWS Lambda events to your local code enabling you to develop faster without the slowness of deploying changes.<br><br>Docs: https://www.serverless.com/framework/docs/providers/aws/cli-reference/dev<br><br>Run &quot;serverless deploy&quot; after a Dev Mode session to restore original code.<br><br>[!] Your local machine is using Node.js v22, while at least one of your functions is not. Ensure matching runtime versions for accurate testing.<br><br>Functions:<br>  hello: my-test-dev-hello (103 kB)<br><br>Endpoints:<br>  GET - https://1q2w3e4r5t.execute-api.us-east-1.amazonaws.com/</pre><p>The dev mode will run the code locally, but the requests will be proxied through the cloud at the exposed endpoint in the console. This can give us a faster feedback loop, great debugging support and parity with production.</p><h4>Deploy the stack to the cloud</h4><p>With serverless deploy we can deploy the stack to the cloud. In a real world application, you have to use the cloud infrastructure to actually run the code. Serverless Framework uses AWS CloudFormation to create/update cloud services after you run the command with necessary permissions to your AWS account.</p><h4>Serverless Offline</h4><p>Now lets see how we can run this offline. This is an extension to the Serverless Framework that help us run the stack offline, further improving the speed of development.</p><p>You don’t get the command by default to run the stack offline (With serverless help you can see all the commands that is supported by the framework). We have to install a new plugin in our stack before trying this.</p><blockquote>Serverless Framework has a great plugin ecosystem.</blockquote><pre>npm install serverless-offline --save-dev</pre><p>add the following to the root level of the configuration to enable the new plugin support.</p><pre>plugins:<br>  - serverless-offline</pre><p>Run serverless offline to run the stack offline. Following will be the output. We can see our Lambda function exposing an endpoint (Use serverless offline --disableCookieValidation if you encounter problems with cookies).</p><pre>Starting Offline at stage dev (us-east-1)<br><br>Offline [http for lambda] listening on http://localhost:3002<br>Function names exposed for local invocation by aws-sdk:<br>           * hello: test-dev-hello<br><br>   ┌─────────────────────────────────────────────────────────────────────────┐<br>   │                                                                         │<br>   │   GET | http://localhost:3000/                                          │<br>   │   POST | http://localhost:3000/2015-03-31/functions/hello/invocations   │<br>   │                                                                         │<br>   └─────────────────────────────────────────────────────────────────────────┘<br><br>Server ready: http://localhost:3000 🚀</pre><p>Access http://localhost:3000 to get the following.</p><pre>{&quot;message&quot;:&quot;Go Serverless v4! Your function executed successfully!&quot;}</pre><p>Our stack is now similar to this kind of AWS infrastructure. And it runs OFFLINE with Serverless! See how little we had to write this setup? Serverless Framework saves us time from a lot of underlying AWS configurations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*6V_yeNVhg2eHcLgt54tIxQ.png" /></figure><h4>What else do we get?</h4><p>Serverless framework supports every AWS service that is available via CloudFormation. Above is a simple example with Lambda and you will be able to incorporate any service into your application with right configuration.</p><p>Following are some services that CloudFormation support:</p><ul><li><strong>Compute: </strong>EC2 instances, ECS services, ELB, Lambda functions, Auto Scaling groups.</li><li><strong>Networking:</strong> VPCs, security groups, subnets, route tables, network ACLs, Elastic IPs, AWS Transit Gateway.</li><li><strong>Storage:</strong> S3 buckets, EBS volumes, EFS.</li><li><strong>Databases:</strong> RDS instances, DynamoDB tables, Redshift clusters, Aurora instances.</li><li><strong>Analytics:</strong> Kinesis streams, Athena.</li><li><strong>Security, Identity, &amp; Compliance:</strong> AWS IAM roles and policies, KMS keys, WAF, GuardDuty.</li><li><strong>Management &amp; Governance:</strong> CloudWatch alarms and dashboards, CloudTrail, Config rules, AWS Systems Manager.</li><li><strong>Application Integration:</strong> SNS topics, SQS queues, Step Functions.</li><li><strong>Developer Tools:</strong> CodePipeline, CodeBuild, CodeDeploy.</li></ul><p>…and many more can be there in ever-growing AWS world.</p><h4>How to scale the solution</h4><p>We need to scale the solution once our application grows. We have the full flexibility to add multiple endpoints and/or queries and mutations to our stack.</p><p>We just have to keep adding endpoints and events for them in the YAML configuration. AWS API Gateway, Lambda and AppSync are services that can adapt to the incoming load because they are fully scalable.</p><p>We can also use Lambda Layers to include common logic so the Lambda endpoints can get reduced in size and have faster execution.</p><h4>Advantages of using the Serverless Framework</h4><p>Lets contrast on what the process could have been if we did not use the Serverless Framework.</p><ul><li><strong>We could write our entire infrastructure as code without manually setting up everything in the AWS console. This made the development faster and provided a reusable code.</strong></li><li><strong>We were running the whole stack offline. The process could have been very painful if it were to deploy the actual stack after each small modification.</strong></li><li><strong>We could visualise the final infrastructure through our code.</strong></li><li><strong>This helps us same time by automatically managing low level configurations such as permissions.</strong></li><li><strong>Debugging is very easy.</strong></li></ul><h4>References</h4><ul><li><a href="https://www.serverless.com/framework/docs">https://www.serverless.com/framework/docs</a></li><li><a href="https://www.serverless.com/framework/docs/getting-started/">https://www.serverless.com/framework/docs/getting-started/</a></li><li><a href="https://fahram.dev/article/full-list-of-aws-services">https://fahram.dev/article/full-list-of-aws-services</a></li></ul><p><strong><em>I am an AWS, Linux and Scrum Master certified Software Engineer at Fcode Labs. I am interested in all the ways to make software development better. Please stop by the website </em></strong><a href="https://buddhiv.io/"><strong><em>buddhiv.io</em></strong></a><strong><em> to see my profile.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d4ddaf5e66f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unspoken React rules for all]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/unspoken-react-rules-for-all-40fe264f56c0?source=rss-b0c1de35f53f------2"><img src="https://cdn-images-1.medium.com/max/2600/0*2xtcf-4z_J5BSQUU" width="4515"></a></p><p class="medium-feed-snippet">Ask from yourself whether you are doing React right</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/unspoken-react-rules-for-all-40fe264f56c0?source=rss-b0c1de35f53f------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/unspoken-react-rules-for-all-40fe264f56c0?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/40fe264f56c0</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Sat, 23 Aug 2025 18:48:24 GMT</pubDate>
            <atom:updated>2025-09-12T00:18:59.225Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Inferred Type Predicates with TypeScript 5.5]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://buddhiv.medium.com/inferred-type-predicates-with-typescript-5-5-73d480a623fc?source=rss-b0c1de35f53f------2"><img src="https://cdn-images-1.medium.com/max/876/1*QmQkHf0kkHG9HE15dBMxbA.png" width="876"></a></p><p class="medium-feed-snippet">This have made TypeScript more intelligent</p><p class="medium-feed-link"><a href="https://buddhiv.medium.com/inferred-type-predicates-with-typescript-5-5-73d480a623fc?source=rss-b0c1de35f53f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://buddhiv.medium.com/inferred-type-predicates-with-typescript-5-5-73d480a623fc?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/73d480a623fc</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[type]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Sun, 23 Jun 2024 18:20:44 GMT</pubDate>
            <atom:updated>2024-06-23T18:20:44.747Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Improve Your HTML Tables with react-virtuoso]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://buddhiv.medium.com/improve-your-html-tables-with-react-virtuoso-ac5d5c64238d?source=rss-b0c1de35f53f------2"><img src="https://cdn-images-1.medium.com/max/2600/1*uYjfUsAWk8aRqWYzsolfbA.jpeg" width="5951"></a></p><p class="medium-feed-snippet">Have you ever built a table listing a lot of information? Then here is how to make it perfect.</p><p class="medium-feed-link"><a href="https://buddhiv.medium.com/improve-your-html-tables-with-react-virtuoso-ac5d5c64238d?source=rss-b0c1de35f53f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://buddhiv.medium.com/improve-your-html-tables-with-react-virtuoso-ac5d5c64238d?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac5d5c64238d</guid>
            <category><![CDATA[virtual-table]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react-virtuoso]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Sat, 08 Jun 2024 16:51:09 GMT</pubDate>
            <atom:updated>2024-07-13T08:11:07.910Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why You Can’t Just Modify an Index of a String]]></title>
            <link>https://buddhiv.medium.com/why-you-cant-just-modify-an-index-of-a-string-0c277a9e27c9?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c277a9e27c9</guid>
            <category><![CDATA[arrays]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[string]]></category>
            <category><![CDATA[data-structures]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Sun, 24 Dec 2023 16:24:47 GMT</pubDate>
            <atom:updated>2024-06-08T17:11:30.446Z</atom:updated>
            <content:encoded><![CDATA[<h4>Difference between a String and an Array in Javascript, even though they behave alike.</h4><p>I recently forgot an important Javascript fundamental and tried the following.</p><pre>myString[0] = &#39;s&#39;; //myString is a String</pre><p>I embarrassed myself by running the code and expecting to modify the index of a string like this. But we cannot modify a string this way because Javascript has different ways of treating different values.</p><p>In most cases we can treat strings and arrays in Javascript similarly. It is even easier to visualize them with similar data structures to better understand our code but there is an important thing to remember.</p><blockquote>Arrays are Objects</blockquote><blockquote>Strings are Primitive Values</blockquote><p>In Javascript, there are 7 primitive values and strings are one of them.</p><ol><li>string</li><li>number</li><li>bigint</li><li>boolean</li><li>undefined</li><li>symbol</li><li>null</li></ol><p>There are not objects and has no methods or properties. Hence these are immutable. Most of the time, a primitive value is represented directly at the lowest level of the language implementation. Arrays in the other hand are treated as objects in Javascript so that they expose methods and properties, and they are also mutable.</p><p>But if strings have no methods or properties, how can we do the following in our code?</p><pre>let stringVariable = otherStringVariable.substring();<br>console.log(stringVariable.toUpperCase());</pre><p>When a primitive is accessed, most of the time Javascript auto-boxes the primitive into a wrapper object. In this scenario the <strong>string</strong> primitive is wrapped with a <strong>String</strong> object. Then Javascript can call the methods on that object.</p><p>Check this example as well.</p><pre>let a = 10;<br>console.log(a.toString());<br>console.log(a.toExponential());</pre><p>Even the N<strong>umber</strong> wrapper has some methods that we can call after initializing a <strong>number</strong> variable.</p><h4>References</h4><ul><li><a href="https://developer.mozilla.org/en-US/docs/Glossary/Primitive">https://developer.mozilla.org/en-US/docs/Glossary/Primitive</a></li></ul><p><strong><em>I am an AWS, Linux and Scrum Master certified Senior Fullstack Software Engineer at Telzee.io. I am deeply interested in architecture concepts for the Javascript world. Please stop at the website </em></strong><a href="https://buddhiv.io/"><strong><em>buddhiv.io</em></strong></a><strong><em> to visit my profile.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c277a9e27c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microservices or Monolith? How To Pick the Right One]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://buddhiv.medium.com/microservices-or-monolith-how-to-pick-the-right-one-08286c5f0fc6?source=rss-b0c1de35f53f------2"><img src="https://cdn-images-1.medium.com/max/2600/1*hdwqBAr99d1UOhVZXSaoeA.jpeg" width="3615"></a></p><p class="medium-feed-snippet">There is a lot of discussion going about the microservices architecture and monolithic architecture. This is how to determine what do you&#x2026;</p><p class="medium-feed-link"><a href="https://buddhiv.medium.com/microservices-or-monolith-how-to-pick-the-right-one-08286c5f0fc6?source=rss-b0c1de35f53f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://buddhiv.medium.com/microservices-or-monolith-how-to-pick-the-right-one-08286c5f0fc6?source=rss-b0c1de35f53f------2</link>
            <guid isPermaLink="false">https://medium.com/p/08286c5f0fc6</guid>
            <category><![CDATA[microservice-architecture]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[monolithic-architecture]]></category>
            <dc:creator><![CDATA[Buddhi Vikasitha]]></dc:creator>
            <pubDate>Sat, 23 Dec 2023 18:46:30 GMT</pubDate>
            <atom:updated>2024-07-13T10:49:01.060Z</atom:updated>
        </item>
    </channel>
</rss>