<?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 Harshit Yadav on Medium]]></title>
        <description><![CDATA[Stories by Harshit Yadav on Medium]]></description>
        <link>https://medium.com/@harshityadav95?source=rss-6136764c2336------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*4fqSrL2tnJwIUebh.</url>
            <title>Stories by Harshit Yadav on Medium</title>
            <link>https://medium.com/@harshityadav95?source=rss-6136764c2336------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:17:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@harshityadav95/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[Terrafo]]></title>
            <link>https://harshityadav95.medium.com/terrafo-f370e4bef8c7?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/f370e4bef8c7</guid>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Mon, 22 Jul 2024 17:19:44 GMT</pubDate>
            <atom:updated>2024-07-22T17:21:09.996Z</atom:updated>
            <content:encoded><![CDATA[<h3>Terraform in Azure</h3><h3>Recap to Terraform</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FtomUWcQ0P3k%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DtomUWcQ0P3k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FtomUWcQ0P3k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fb793facc7922a2935964e35978916cb/href">https://medium.com/media/fb793facc7922a2935964e35978916cb/href</a></iframe><p>Skip Paywall read full Article : <a href="https://harshityadav.in/posts/Terraform-in-Azure/">https://harshityadav.in/posts/Terraform-in-Azure/</a></p><h3>Terraform Installation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/0*340YoG2nEPBOBE71" /></figure><p>Tried official installation instructions but faced some dependency issue on my machine so ended up installing using the brew recipe</p><pre>brew install terraform</pre><h3>Getting Started</h3><ol><li>Set up a Cloud Account on any cloud provider (<a href="https://k21academy.com/amazon-web-services/aws-solutions-architect/create-aws-free-tier-account/">AWS</a>, <a href="https://k21academy.com/microsoft-azure/create-free-microsoft-azure-trial-account/">Azure</a>, <a href="https://k21academy.com/oracle-cloud/video-register-free-oracle-cloud-trial-account/">OCI</a>)</li><li>Install Terraform</li><li>Add a provider — AWS, Azure, OCI, GCP, or others</li><li>Write configuration files</li><li>Initialize Terraform Providers</li><li>PLAN (DRY RUN) using terraform plan</li><li>APPLY (Create a Resource) using terraform apply</li><li>DESTROY (Delete a Resource) using terraform destroy</li></ol><h3>Terraform Providers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NqMaWZOIUo7LgoCL" /></figure><h3>Teraform Configuration Files</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zHqUwWlZhDtAhVVr" /></figure><h3>Importing Existing Infrastructure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/0*sujKhfy53h0weegz" /></figure><h3>Terraform Stages</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5btwV_vjLnl8LP2d" /></figure><h3>Commands</h3><pre>1$ mkdir learn-terraform-azure</pre><pre>$ cd learn-terraform-azure</pre><pre>## Code in the Terraform File</pre><pre>## Az login in between with the correct subscription selected activated</pre><pre>$ terraform init</pre><pre>$ terraform fmt</pre><pre>$ terraform plan</pre><pre>$ terraform apply</pre><h3>Resource :</h3><ul><li><a href="https://formulae.brew.sh/formula/terraform">https://formulae.brew.sh/formula/terraform</a></li><li><a href="https://k21academy.com/terraform-iac/terraform-beginners-guide/">https://k21academy.com/terraform-iac/terraform-beginners-guide/</a></li><li><a href="https://k21academy.com/terraform-iac/terraform-cheat-sheet/">https://k21academy.com/terraform-iac/terraform-cheat-sheet/</a></li><li><a href="https://learn.hashicorp.com/tutorials/terraform/azure-build?in=terraform/azure-get-started">Build Infrastructure — Terraform Azure Example Terraform — HashiCorp Learn</a></li><li><a href="https://learn.hashicorp.com/tutorials/terraform/install-cli">Install Terraform Terraform — HashiCorp Learn</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f370e4bef8c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[High-Level Design HLD & Low-Level System Design LLD]]></title>
            <link>https://harshityadav95.medium.com/high-level-design-hld-low-level-system-design-lld-64cc4dacd6c1?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/64cc4dacd6c1</guid>
            <category><![CDATA[hld]]></category>
            <category><![CDATA[lld]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Mon, 22 Apr 2024 12:57:43 GMT</pubDate>
            <atom:updated>2024-04-22T12:57:43.195Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xrZv8NjVNJjpwCPdKZF0Ww.png" /></figure><p>Read Full Article without paywall : <a href="https://harshityadav.in/posts/HLD-vs-LLD-System-Design-Intro/">https://harshityadav.in/posts/HLD-vs-LLD-System-Design-Intro/</a></p><h3>High-Level Design</h3><p><strong>High-level design</strong> or <strong>HLD</strong> refers to the overall system, a design that consists description of the system architecture and design and is a generic system design that includes:</p><p>The HLD process typically involves a number of steps, including:</p><ul><li>Identifying the system’s requirements and constraints</li><li>Identifying the key components and their interfaces</li><li>Identifying the main algorithms and data structures</li><li>Identifying the system’s overall structure and organization</li><li>Identifying any external dependencies or interfaces</li><li>Identifying any performance or scalability concerns</li></ul><p><strong>Examples:</strong> System architectural documentation, app development flowcharts, and other items are examples of HLD in software development.</p><h3>Pros of High-Level Design</h3><ul><li>It serves as the foundation for the stakeholders’ acceptance of the suggested solution.</li><li>Project planners can determine the project’s cost and evaluate its risk using high-level estimations produced from the HLD.</li><li>It also describes significant limitations and trade-offs of the system.</li><li>The HLD is a fantastic tool for collaboration and communication. It is a forum for exchanging opinions on a difficult system.</li></ul><h3>Common Pitfalls</h3><ul><li><strong>Lack of Clear Requirements:</strong></li><li>Mistake: Designing without clear requirements.</li><li>Solution: Gather and validate detailed requirements from stakeholders.</li><li><strong>Over-Engineering:</strong></li><li>Mistake: Building overly complex solutions.</li><li>Solution: Follow the KISS principle; design for current needs.</li><li><strong>Underestimating Scalability:</strong></li><li>Mistake: Ignoring scalability needs.</li><li>Solution: Plan for scalability; use appropriate architecture.</li><li><strong>Ignoring Security:</strong></li><li>Mistake: Neglecting security concerns.</li><li>Solution: Integrate security practices into the design.</li><li><strong>Tight Coupling:</strong></li><li>Mistake: Creating tightly coupled modules.</li><li>Solution: Aim for loose coupling; use Dependency Injection.</li></ul><h3>Low-Level Design</h3><p>The main aim of LLD is to deliver a comprehensive, step-by-step implementation plan for the system. LLD also provides essential data validation rules and tackles error handling and recovery concerns.</p><p><strong>Examples</strong>: Examples of LLD in software development include cart integration, <a href="https://www.naukri.com/code360/library/security-testing"><strong>security testing</strong></a>, <a href="https://www.naukri.com/code360/library/user-interface-design"><strong>user interface design</strong></a>, etc.</p><h3>Pros of Low-Level Design</h3><ul><li>It consists of a detailed pseudocode or other representation of the algorithms and data structures to be employed. It also includes a step-by-step plan for the system’s implementation.</li><li>LLD provides essential data validation rules. It also tackles error handling and recovery concerns.</li><li>It creates software with little testing and debugging.</li></ul><h3>Common Pitfalls</h3><ul><li><strong>Unoptimized Data Structures:</strong></li><li>Mistake: Using inefficient data structures.</li><li>Solution: Choose data structures based on requirements.</li><li><strong>Premature Optimization:</strong></li><li>Mistake: Optimizing without identifying bottlenecks.</li><li>Solution: Profile first, optimize where needed.</li><li><strong>Lack of Modularity:</strong></li><li>Mistake: Writing monolithic code.</li><li>Solution: Divide into smaller, modular components.</li><li><strong>Ignoring Error Handling:</strong></li><li>Mistake: Not handling errors properly.</li><li>Solution: Implement robust error handling.</li><li><strong>Inadequate Testing:</strong></li><li>Mistake: Skipping testing.</li><li>Solution: Follow a comprehensive testing strategy.</li><li><strong>Not Following Coding Standards:</strong></li><li>Mistake: Inconsistent coding styles.</li><li>Solution: Adhere to coding guidelines, and use linting.</li><li><strong>Ignoring Platform Differences:</strong></li><li>Mistake: Neglecting platform-specific issues.</li><li>Solution: Account for platform variations in design.</li></ul><h3>Detailed-Level Design (DD)</h3><p><strong>Detailed Level Design (DLD)</strong> is the most detailed technical document, which describes user stories, error processing algorithms, state transitions, logical sequences, and others. DLD describes the interaction of every low-level process with each other. As we noted above, DLD is the extension of the Low-Level Design (LLD.)</p><h3>Why are LLD and HLD important for developers?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/0*k0weclVXqaGdAF4_" /></figure><h3>Collaboration:</h3><p>LLD and HLD facilitate effective collaboration among development teams. By having a clear design blueprint, everyone involved can better understand their roles and responsibilities, work cohesively, and reduce the chances of miscommunication or conflicts.</p><h3>Scalability and Maintainability:</h3><p>A well-designed architecture ensures that our software systems can scale smoothly as requirements evolve or user demands increase. LLD and HLD enable us to plan for future enhancements, make informed design decisions, and simplify maintenance tasks. It saves time, effort, and resources in the long run.</p><h3>Code Quality:</h3><p>LLD and HLD promote good coding practices and high-quality code. With a structured approach to design, developers can write clean, modular, and reusable code that is easier to test, debug, and extend.</p><h3>Efficiency:</h3><p>By investing time in thoughtful LLD and HLD, developers can identify potential bottlenecks, optimize performance, and improve overall efficiency. This leads to faster execution, reduced resource consumption, and enhanced user experience.</p><h3>Conclusion</h3><p>High-Level Design documents are like big-picture plans that help project managers and architects understand how a system will work and low-Level Design documents are more detailed and are made for programmers.</p><ul><li>They show exactly how to write the code and make the different parts of the system fit together. Both documents are important for different people involved in making and maintaining the software.</li><li>Creating a High-Level Design is like making a big plan for the software, and it helps find problems early, so the quality of the software can be better assured.</li><li>On the other hand, when Low-Level Design is well-documented, it makes it easier for others to check the code and ensure its quality during the actual writing of the software.</li></ul><p>Both these steps help catch and fix issues early, making the overall software development process smoother and more reliable.</p><h3>Summary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*aB4_ENr8g75hHjrP" /></figure><h3>Reference</h3><ul><li><a href="https://www.geeksforgeeks.org/what-is-low-level-design-or-lld-learn-system-design/">https://www.geeksforgeeks.org/what-is-low-level-design-or-lld-learn-system-design/</a></li><li><a href="https://www.geeksforgeeks.org/what-is-high-level-design-learn-system-design/">https://www.geeksforgeeks.org/what-is-high-level-design-learn-system-design/</a></li><li><a href="https://freedium.cfd/https://medium.com/@yam-yam-architect/hld-vs-lld-10759c63ccae">https://freedium.cfd/https://medium.com/@yam-yam-architect/hld-vs-lld-10759c63ccae</a></li><li><a href="https://www.linkedin.com/pulse/why-lld-hld-essential-developers-shankhadeep-das">https://www.linkedin.com/pulse/why-lld-hld-essential-developers-shankhadeep-das</a></li><li><a href="https://www.scaler.com/topics/high-level-design-and-low-level-design/">https://www.scaler.com/topics/high-level-design-and-low-level-design/</a></li><li><a href="https://softwaredominos.com/home/software-design-development-articles/high-level-solution-design-documents-what-is-it-and-when-do-you-need-one/">https://softwaredominos.com/home/software-design-development-articles/high-level-solution-design-documents-what-is-it-and-when-do-you-need-one/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64cc4dacd6c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Terraform 101]]></title>
            <link>https://harshityadav95.medium.com/terraform-101-b0c8fb704df4?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0c8fb704df4</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Wed, 10 Jan 2024 10:09:31 GMT</pubDate>
            <atom:updated>2024-01-10T10:09:31.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-G3isSfbtnI8ABd9" /></figure><p>Read without Paywall : <a href="https://harshityadav.in/posts/Terraform-101/">https://harshityadav.in/posts/Terraform-101/</a></p><h3>Terraform in a nutshell</h3><p>In its most basic form, Terraform is an application that converts configuration files known as HCL (Hashicorp Configuration Language) into real-world infrastructure, usually in Cloud providers such as AWS, Azure, or Google Cloud Platform.</p><h3>Infrastructure as Code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/0*yranq5zwlE3nqgkS" /></figure><ul><li>This concept of taking configuration files and converting them into real resources is known as IaC (Infrastructure as Code) and is the new hotness in the world of Software Engineering. And the reason it is becoming so hot right now is because this code can live alongside your app code in repos, be version controlled, and easily integrated into your CI/CD pipelines.</li></ul><h3>Why Terraform?</h3><ul><li>Terraform is a state-driven Cloud Platform provisioning engine.</li><li>It leverages abstraction tooling (known as providers and backends) to enable us to write code that can be interpreted and translated into consistent, and deterministic, Cloud provider-specific CRUD API calls, removing a lot of leg work and stress from us.</li><li>Removes the need for in-house custom infrastructure provisioning scripts and/or tooling.</li><li>Terminates human error because automated code deployments remove the human element.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/0*844PagUCvrwfM7gn" /></figure><p>It is important to note that IaC is not a new concept, in fact, it has been around in different guises since the very early days of Cloud Platforms</p><ul><li>AWS had CloudFormation</li><li>Azure had ARM Templates</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*xcgRL6dWGoeiKO9L" /></figure><h3>Terraform Core Concepts</h3><p><strong>1. Variables</strong>:</p><p>Terraform has input and output variables, it is a key-value pair. Input variables are used as parameters to input values at run time to customize our deployments. Output variables are return values of a terraform module that can be used by other configurations.Read our blog on <a href="https://k21academy.com/terraform-iac/variables-in-terraform/"><strong>Terraform Variables</strong></a></p><p><strong>2. Provider</strong>:</p><p>Terraform users provision their infrastructure on the major cloud providers such as AWS, Azure, OCI, and others. A <em>provider</em> is a plugin that interacts with the various APIs required to create, update, and delete various resources.Read our blog to know more about <a href="https://k21academy.com/terraform-iac/terraform-providers-overview/"><strong>Terraform Providers</strong></a></p><p><strong>3. Module</strong>:</p><p>Any set of Terraform configuration files in a folder is a <em>module</em>. Every Terraform configuration has at least one module, known as its <strong><em>root module.</em></strong></p><p><strong>4. State</strong>:</p><p>Terraform records information about what infrastructure is created in a Terraform <em>state</em> file. With the state file, Terraform is able to find the resources it created previously, supposed to manage and update them accordingly.</p><p><strong>5. Resources</strong>:</p><p>Cloud Providers provides various services in their offerings, they are referenced as Resources in Terraform. Terraform resources can be anything from compute instances, virtual networks to higher-level components such as DNS records. Each resource has its own attributes to define that resource.</p><p><strong>6. Data Source</strong>:</p><p>Data source performs a read-only operation. It allows data to be fetched or computed from resources/entities that are not defined or managed by Terraform or the current Terraform configuration.</p><p><strong>7. Plan</strong>:</p><p>It is one of the stages in the Terraform lifecycle where it determines what needs to be created, updated, or destroyed to move from the real/current state of the infrastructure to the desired state.</p><p><strong>8. Apply</strong>:</p><p>It is one of the stages in the Terraform lifecycle where it applies the changes real/current state of the infrastructure in order to achieve the desired state.</p><h3>Terraform States</h3><pre>Everything Terraform does revolves around State. If you don’t understand how Terraform manages and maintains State; you don’t understand how Terraform works</pre><p>let’s imagine you are in a restaurant and when the waiter comes over to your table, you order the following dishes:</p><ul><li>Soup</li><li>Steak</li><li>Side of chips</li><li>Ice cream</li></ul><p>In Terraform terminology this is your “desired state”, in order for you to be satisfied, you want all 4 of those items you’ve ordered.</p><ul><li>Well, Terraform is exactly the same, and in Terraform terminology, when our “desired state” gets manifested into reality, it becomes known as the “actual state”.</li></ul><p>When we tell Terraform to do a deployment, it will do a sequence of steps:</p><p>Terraform, there is a chance that someone has “removed” your resource, so Terraform must first check if our resource first exists in State (AKA has been created previously), and then it must check with Azure to ensure that the actual state matches what it expects to find.</p><p>Please note: The term commonly given to this chain of operations to bring desired and actual state into alignment is: <strong>Reconciliation;</strong> Terraform <strong><em>reconciles</em></strong> desired state into the actual state.</p><h3>CRUD in Terraform</h3><h3>Create</h3><ul><li>A desired resource doesn’t exist in our Terraform State.</li><li>A desired resource exists in Terraform State, but ends up not actually existing in our Cloud.</li></ul><h3>Update</h3><ul><li>A desired resource exists in Terraform State, but is configured differently in our Cloud.</li></ul><h3>Delete</h3><ul><li>A resource gets removed from our desired state, but still exists in our Terraform State.</li></ul><h3>Working of Terraform</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/0*CE1SLjYMaRJw8ESB" /></figure><ol><li>It will parse our HCL configuration/code files.</li><li>Using the information in our HCL, Terraform will build up a graph of all the resources we want to provision <strong><em>(desired state)</em></strong> and figure out any dependencies between them to try and decide a logical order they need to be created.</li><li>Terraform will next inspect its State to better understand what it has and hasn’t deployed (if it is our first deployment, the State will be empty). This is known as the <strong><em>perceived state.</em></strong> It is a perceived state because there is a disconnect between what Terraform “thinks” and what “actually” exists.</li><li>Terraform next performs a logical delta between our <strong>desired state</strong>, and what it knows to be our <strong><em>perceived state.</em></strong> It then decides which CRUD actions it needs to complete, and the order to perform them in, order to bring our <strong><em>perceived state</em></strong> in line with our <strong><em>desired state</em></strong>.</li><li>Terraform next performs all necessary operations to achieve the <strong><em>desired state</em></strong>. The result of this operation will be that resources will likely start to appear in our Azure subscription and this then becomes known as the <strong><em>actual state.</em></strong></li><li>Terraform updates the state to reflect what it has done.</li></ol><h3>What happens when we re-run our Terraform?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/0*Ywtv0vUbBeCMMy6H" /></figure><ol><li>Terraform parses our HCL configuration.</li><li>It sees our desired state is to have a Resource Group</li><li>It checks in our State to see if there is an entry for a Resource Group with the state identifier example (as mentioned before, notice that the resource is identified as “example”, not the name attribute “example-resources”, just like with variables in other languages)</li><li>Terraform sees that the State contains an entry <strong><em>(perceived state)</em></strong>, and so next go to Azure to query the <strong><em>actual state</em></strong> of the Resource Group.</li><li>Azure reports back a 404 that our Provider will interpret as the Resource Group does not exist 😱</li><li>Terraform now performs the delta between <strong><em>“Desired state”</em></strong> and <strong><em>“Actual state”</em></strong> and realizes that the necessary action to perform is to Create it.</li><li>Terraform performs the necessary actions to create the Resource Group</li><li>Terraform updates its State as necessary.</li></ol><h3>What if the State file is lost and Terraform is re-run?</h3><ol><li>Terraform parses our HCL configuration/code files.</li><li>Terraform will build up a graph of all the resources we want.</li><li>Terraform checks the State and finds it empty.</li><li>Terraform does its logical delta between our desired state and what is in its State, and decides it needs to create a resource (remember, Terraform hasn’t queried Azure because the <strong>state file didn’t exist/was empty</strong>)</li><li>Terraform attempts to create a resource group named “example-resources”… <strong>BANG!!! 💥</strong></li><li>We now have a situation where Terraform errors because Azure already has a resource group with that name and we cannot create another one with the same name.</li></ol><blockquote><strong><em>Terraform does not know anything about provisioned resources in your Cloud Provider unless it’s in the State</em></strong></blockquote><h3>Terraform Lifecycle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/0*HWdDXjWelQfEzUkS" /></figure><h3>Initialization</h3><pre>$ terraform init</pre><ul><li>The first command we need to run is initialized.</li><li>This command is used to initialize a working directory containing</li><li>Terraform configuration files and instructs Terraform to interrogate the HCL files, determine the Providers needed, download them, and initialize a State if it doesn’t already exist.</li><li>It is perfectly safe to run init multiple times, and in fact, you will likely need to do so if you add new providers or change any settings within your Terraform block.</li></ul><h3>Planning</h3><pre>$ terraform plan</pre><ul><li>The next command we run is plan .</li><li>This command instructs Terraform to parse our HCL files, build a graph of our resources, check its state and attempt to come up with an execution plan to perform.</li><li>It is perfectly valid for our init to succeed but our plan to fail. This is because init doesn’t really concern itself with trying to determine if any of our resources are valid or if they exist.</li><li>Only when Terraform starts to interpret our “desired state” will we start to find syntax errors in our files.</li><li>The output of the plan command will be a complex list of operations that Terraform has decided to perform.</li><li>It is highly recommended that you review these changes to ensure they match with those you expected to see as destructive operations can be costly</li><li>if they are done in error. Think of this as a “dry run” of all your Terraform.</li><li>It is also worth noting that the output of the plan can be saved into a file and used for the next step apply as this ensures that there can be no confusion/discrepancies between what was planned and that which was applied.</li></ul><h3>Applying</h3><pre>$ terraform apply</pre><ul><li>Simply put this operation tells Terraform to execute all its planned operations.</li><li>This will usually cause Terraform to redo its plan (unless a plan file is provided to the command) and then present you with an “Are you sure?” prompt. This is your point of no return.</li><li>If you say yes then Terraform is going to start really provisioning things for you.</li></ul><p>This is probably the simplest of all the commands, but it does have some interesting abilities, such as “auto approval” and the ability to increase or decrease the parallelization of the execution.</p><pre>1If you are renaming resource identifiers, make sure the change is really really really really necessary!</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KyrGkr7neF4-fQUg" /></figure><h3>TLDR</h3><ul><li>Terraform is a state-driven engine that allows us to provision cloud infrastructure easily and consistently.</li><li>Terraform utilizes code known as HCL (Hashicorp Configuration Language)</li><li>HCL uses the keyword resource to define “resources” we wish to have provisioned in our Cloud.</li><li>HCL allows us to use the configuration/output from one resource as the input for the configuration/attributes of another resource.</li><li>Terraform interfaces with different Cloud technologies using Providers.</li><li>When terraform runs it will parse the HCL files and build a graph of resources we want — known as <strong>Desired State</strong></li><li>By “chaining” resources together, it enables Terraform to make explicit dependencies between objects in its graph.</li><li>Terraform stores knowledge about all the resources it has provisioned previously in a file known as its <strong>State file.</strong></li><li>The contents of the State file are known as <strong>Perceived State</strong> — the state Terraform left the environment the last time it was run using our HCL files.</li><li>Terraform uses Backends to determine how the State should be persisted.</li><li>There are many different Backends that can be used depending on the Cloud Service Provider we use and how we want Terraform to persist State.</li><li>When Terraform wants to provide a resource, and that resource exists in its Perceived State, it will interrogate the Cloud Provider to determine the <strong>Actual State.</strong></li><li>If there are discrepancies between <strong>desired</strong>, <strong>perceived,</strong> and <strong>actual</strong> states, Terraform will determine the corrective action required to bring actual in line with desired.</li><li>Terraform has 3 distinct lifecycle stages: init, plan and apply</li><li>If you rename a resource identifier, Terraform will act as if it is a brand new resource it’s never seen before, and purge everything to do with resources relating to the old identifier.</li></ul><h3>Resource :</h3><ul><li><a href="https://itnext.io/terraform-for-beginners-dd8701c1ebdd">https://itnext.io/terraform-for-beginners-dd8701c1ebdd</a></li><li><a href="https://www.terraform.io/docs/cli/commands/init.html">https://www.terraform.io/docs/cli/commands/init.html</a></li><li><a href="https://geekflare.com/terraform-for-beginners/">https://geekflare.com/terraform-for-beginners/</a></li><li><a href="https://k21academy.com/terraform-iac/terraform-beginners-guide/">https://k21academy.com/terraform-iac/terraform-beginners-guide/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0c8fb704df4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redo, Undo, and Write Ahead Logs WAL in Database]]></title>
            <link>https://harshityadav95.medium.com/redo-undo-and-write-ahead-logs-wal-in-database-0981ef375694?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/0981ef375694</guid>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[database-development]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Mon, 08 Jan 2024 20:14:29 GMT</pubDate>
            <atom:updated>2024-01-08T20:16:21.601Z</atom:updated>
            <content:encoded><![CDATA[<p>Full Article without Paywall : <a href="https://harshityadav.in/posts/Redo-Undo-WAL-Write-ahead-logs-in-Database/">https://harshityadav.in/posts/Redo-Undo-WAL-Write-ahead-logs-in-Database/</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FuHvR7nOu5m4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DuHvR7nOu5m4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FuHvR7nOu5m4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/95af72ce628e49691b5d998e4994832b/href">https://medium.com/media/95af72ce628e49691b5d998e4994832b/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/0*Ay4vgxA6poMfqmE8" /></figure><p>Database logs are a critical part of any database system to ensure</p><ul><li>Durability</li><li>Crash Recovery</li></ul><p>There are different types of Logs such as Write ahead Logs WAL, Redo logs, Undo Logs, etc.</p><p>WAL is identical to Redo logs</p><p>If we think about the durability of the system the vital thing to think about is how do we persist the data in the DB, we know data is stored in tables which is in turn stored using data structures that are stored in the file system or even block system. How we keep these files and implement saving of these files ie storing the index in one file or storing indexes in different files all depends upon the implementation</p><p>When we start making changes or updating the data in the table it will start making changes in indexes, and indexes need to be updated, also the data exists in pages that live in memory and need to be committed</p><h3>What does commit Operation in DB mean?</h3><p>Whatever data is stored in the DB which lies on the page right now should persist and be available in the future with the same value. Whenever we change data the page (~6KB to 8 KB) is fetched in memory and edited or inserted in memory in the same page that exists in the memory and we keep writing it to it when the client tells us to commit we flush the data back to the drive with the changes.</p><p>If we have written a lot of data it will take a long time also to write the data back into the memory, the cost is not the writing time back to the disk but what if the database crash and the data is not written back successfully to the disk or is half-written, should follow and adhere to the ACID transaction (ACIDITY complete or non )</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/0*23X-8u9BkpHpFArK" /></figure><h3>Solution</h3><p>As we are writing the changes we keep a journal/record, so when we are writing back the changes do not send just the single changed value or column for a few bytes we send the entire page, the minimum page/block/sector (set by disk type)size that needs to be written back</p><p>We keep a log of every change and write it to disk and keep it as a source of truth for all the changes and value changes in the database this is called (Write Ahead Log ie knowing ahead in time what is going to change when the page is going to be written ), now with help of these we can keep dirty pages in memory and before commit action, there is already a journal written on disk that has it recorded so in case the page commit is not successful we can replay the whole page write a scenario with data changes.</p><p>In case the commit is false the page with old persistent data can be loaded again by syncing the pages and the WAL log can be used to restore the state. Now the thought process comes why not just read this from the journal and send the data in case the request came (well possible but not feasible to implement as it only has changed)</p><p>We can reconstruct the page with the WAL log and flush it and commit it back to disk again without failing</p><ul><li>How often to Flush Data is configurable by DBA, there is an upper limit on WAL size before it can be purged and started over</li><li>The purpose of WAL is to restore in case of DB flush fails and purged itself when it’s successful</li><li>There are both OS cache and DB cache in the picture (2 Layers of cache in Postgresql)</li><li>Flushing of Pages is called Checkpointing and is random since it is IO and data Intensive and costly as things need to be paused when this is happening as WAL cannot grow when we are purging it</li><li>This Checkpoint can be happening at the most transaction-heavy moments and high resource usage times but are to be done and not much can be done about it</li><li>Glossary: Fsync, WAL parameters</li></ul><p>We also don’t write back the page back to disk, we keep it back in memory anticipating more writes so the more writes a single page receives the better it will be since no new fetching or different page is being fetched from disk</p><h3>Fsync</h3><p>It is disabled by default the changes go to the cache but if it enables all and every single change to be sent to the disk, makes it a write-through cache, and no WAL used so in case of a crash hard to recover</p><h3>Undo Log</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*MtWQGeW-IsG6USNn" /></figure><p>Not every database has it, Postgresql does not have it. It gives the state of the transaction before the change started like another transaction needed the state before we changed it (Oracle and MYSQL have this model, Postgres does not have it since it uses versioning ie when an update happens a new row lies on top of the older row and the old data is present in page) so in this model, if someone needs older value we read this log and undo the changes on the value to see the older state (more work to see older transaction) all this on a transaction that is not committed</p><h3>Redo Log / WAL</h3><p>Is the opposite of Undo Log, it contains the newer state to be restored in case of commit failure</p><p>Why do we have to undo it if we have to redo it? Answer because it does not store which transaction did what change on the value so traveling back to a certain transaction is not possible</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/0*SyIQ84dvj_-8Pvy3" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0981ef375694" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gang of Four Intro to Design Patterns Series 1/24]]></title>
            <link>https://harshityadav95.medium.com/gang-of-four-intro-to-design-patterns-series-1-24-7e4d386fd7f8?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e4d386fd7f8</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[gang-of-four]]></category>
            <category><![CDATA[interview-questions]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Sun, 07 Jan 2024 19:01:17 GMT</pubDate>
            <atom:updated>2024-01-07T19:01:17.487Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*24-Bgqhz58sl29P6" /></figure><p>Full Article without paywall : <a href="https://harshityadav.in/posts/Gang-of-Four-Design-Patterns-Intro/">https://harshityadav.in/posts/Gang-of-Four-Design-Patterns-Intro/</a></p><h3>**What’s a design pattern?**</h3><p><strong>Design patterns</strong> are typical solutions to commonly occurring problems in software design. They are like pre-made blueprints that you can customize to solve a recurring design problem in your code.</p><p>An analogy to an algorithm is a cooking recipe: both have clear steps to achieve a goal. On the other hand, a pattern is more like a blueprint: you can see what the result and its features are, but the exact order of implementation is up to you.</p><h3>**Why should I learn patterns?**</h3><ul><li>Design patterns are a toolkit of <strong>tried and tested solutions</strong> to common problems in software design. Even if you never encounter these problems, knowing patterns is still useful because it teaches you how to solve all sorts of problems using principles of object-oriented design.</li><li>Design patterns define a common language that you and your teammates can use to communicate more efficiently. You can say, “Oh, just use a Singleton for that,” and everyone will understand the idea behind your suggestion.</li></ul><h3>History of GoF</h3><p>Four authors: Erich Gamma, John Vlissides, Ralph Johnson, and Richard Helm.</p><ul><li>In 1994, they published <a href="https://refactoring.guru/gof-book"><strong>Design Patterns: Elements of Reusable Object-Oriented Software</strong></a>, in which they applied the concept of design patterns to programming.</li><li>The book featured 23 patterns solving various problems of object-oriented design</li><li>Due to its lengthy name, people started to call it “The Book by the gang of four” which was soon shortened to simply “the GoF book”.</li></ul><h3>**Criticism of patterns**</h3><ul><li><strong>**Kludges for a weak programming language</strong>**</li><li><strong>**Inefficient solutions</strong>**</li><li><strong>**Unjustified use</strong>**</li><li>If all you have is a hammer, everything looks like a nail</li></ul><h3>Design Pattern Categories</h3><p>There are many other unofficial and undocumented patterns out there that you might find useful in certain situations outside of the classic 23. However, all patterns can be categorized by their intent, or purpose. The book covers three of the main groups of patterns, which I will go into more detail in the next blog.</p><ul><li>Creational Pattern</li><li>Structural Pattern</li><li>Behavioral Pattern</li></ul><h3>Behavioral Design Patterns</h3><ul><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Chain-Of-Responsibility-Pattern">Chain Of Responsibility Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Command-Pattern">Command Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Iterator-Pattern">Iterator Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Mediator-Pattern">Mediator Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Memento-Pattern">Memento Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Observer-Pattern">Observer Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Visitor-Pattern">Visitor Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Strategy-Pattern">Strategy Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-State-Pattern">State Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Template-Method-Pattern">Template Method Pattern</a></li></ul><h3>Creational Design Patterns</h3><ul><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Simple-Factory-Pattern">Simple Factory Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Factory-Method-Pattern">Factory Method Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Abstract-Factory-Pattern">Abstract Factory Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Builder-Pattern">Builder Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Prototype-Pattern">Prototype Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Singleton-Pattern">Singleton Pattern</a></li></ul><h3>Structural Design Patterns</h3><ul><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Adapter-Pattern">Adapter Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Bridge-Pattern">Bridge Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Composite-Pattern">Composite Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Decorator-Pattern">Decorator Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Facade-Pattern">Facade Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Flyweight-Pattern">Flyweight Pattern</a></li><li><a href="https://harshityadav.in/posts/GoF-Design-Patterns-by-Example-Proxy-Pattern">Proxy Pattern</a></li></ul><h3>Reference</h3><ul><li><a href="https://refactoring.guru/design-patterns">https://refactoring.guru/design-patterns</a></li><li><a href="https://www.ashishvishwakarma.com/GoF-Design-Patterns-by-Example/">https://www.ashishvishwakarma.com/GoF-Design-Patterns-by-Example/</a></li><li><a href="https://www.digitalocean.com/community/tutorials/gangs-of-four-gof-design-patterns">https://www.digitalocean.com/community/tutorials/gangs-of-four-gof-design-patterns</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e4d386fd7f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reactive Programming Java]]></title>
            <link>https://harshityadav95.medium.com/reactive-programming-java-a8c635e18f6e?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8c635e18f6e</guid>
            <category><![CDATA[reactive-streams]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[java-stream-api]]></category>
            <category><![CDATA[reactive-programming]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Sat, 06 Jan 2024 11:42:59 GMT</pubDate>
            <atom:updated>2024-01-06T11:42:59.295Z</atom:updated>
            <content:encoded><![CDATA[<p>What? Why? When? Advantages?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FA5nCPqPH3Fc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DA5nCPqPH3Fc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FA5nCPqPH3Fc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/458ca95ce64c91e36d5226dc8caebf30/href">https://medium.com/media/458ca95ce64c91e36d5226dc8caebf30/href</a></iframe><p>Full Article without paywall : <a href="https://harshityadav.in/posts/Reactive-Programming-Java/">https://harshityadav.in/posts/Reactive-Programming-Java/</a></p><h3>Core Feature of Reactive Programming</h3><ol><li>New Programming Paradigm</li><li>Asynchronous and non blocking</li><li>Functional Style code</li><li>Data Flow as an Event-driven stream</li><li>Backpressure on data streams</li></ol><h3>Recap</h3><h3>Synchronous and Blocking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4hatPsf2udbGcqvy" /></figure><ul><li>The restaurant is blocked until the cook completes one dish only then the restaurant takes another order</li></ul><h3>Asynchronous and Non-Blocking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jqodaJEkjIvKJKKA" /></figure><h3>Thread per Request model: Traditional REST API</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s_m8MJdbquISZ310" /></figure><ul><li>One request one per thread, limited by the thread pool</li><li>if more requests come have to wait until more threads are available to start the task</li><li>reactive programming came into the picture</li><li>Horizontal scaling is needed to add more threads</li><li>By default, Tomcat sets maxThreads to 200, which represents the maximum number of threads allowed to run at any given time.</li></ul><h3>Reactive Programming</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rQ3Rh4lBAGyriJCv" /></figure><ul><li>The request comes to application and is assigned to thread 1</li><li>Thread one comes to fetch the value from the database to get the</li><li>The advantage here is it will not wait for the database to respond back to the result, it will inform the database the thread is not waiting</li><li>Whenever the database job is complete and the response is ready, then send that response to the available thread and publish the previous thread a complete event</li><li>In this case, the thread pool and threads are free and accept more events as no thread is blocked in the event loop.</li><li>With this approach, lots of concurrent requests can be handled with significantly fewer threads, which is asynchronous and non-blocking</li></ul><h3>Functional Style code Vs Rest Code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eEyJMH7BXw9DlVQT" /></figure><ul><li>The syntax is similar to JAVA 8 Stream API</li></ul><h3>Data Flow and Event-Driven Stream</h3><h3>REST Approach</h3><ul><li>The client sends the request to the application, the request then goes to the database to process the data, and finally, the request is sent back to the client</li><li>WHAT IF? If there are few records inserted or updated in the middle, then the client will not have the updated value, to get the information the client has to again do a separate REST API call</li></ul><h3>Reactive Programming</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i4kS7u82F8w2nutS" /></figure><ul><li>If there is any change in the database it will immediately publish an event that there is an update in the data, now whoever subscribed to the data will update the data</li><li>Subscriber: Client</li><li>Publisher: Database client</li><li>The connection will be always in the open state</li></ul><p>Ex : Cricket Live score update</p><h3>Backpressure on Data Streams</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rE6C39aCGZynlhij" /></figure><h3>Traditional API</h3><ul><li>If one has to get all the items from the inventory</li><li>The application sends the request to the database</li><li>Database send requests as a large volume of data</li><li>The Application might now be able to handle a large volume of data and crash with a memory error</li><li>No Back pressure feature available with traditional API</li></ul><h3>Reactive Programming</h3><ul><li>There is this feature of backpressure if the database is sending large amount of data and the application cannot handle it</li><li>WE can tell database to slow down the response until processing is done by the application before accepting more data (🤔 Cursor in DB ?)</li><li>implemented by adding a limitation on the database driver configuration on how much data can be expected by slowing down the database driver to slow down the data coming</li></ul><h3>Advantages of Reactive Programming</h3><ul><li>Achieve proper CPU utilization</li><li>No Application downtime</li><li>The flow of execution can be concurrent since code is asynchronous and nonblocking</li><li>Streaming database publisher and subscriber model</li></ul><h3>Reference :</h3><ul><li><a href="https://youtu.be/A5nCPqPH3Fc">https://youtu.be/A5nCPqPH3Fc</a></li><li><a href="https://youtu.be/EExlnnq5Grs">https://youtu.be/EExlnnq5Grs</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8c635e18f6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lightweight directory access protocol LDAP]]></title>
            <link>https://harshityadav95.medium.com/lightweight-directory-access-protocol-ldap-78f7d2cb2294?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/78f7d2cb2294</guid>
            <category><![CDATA[active-directory]]></category>
            <category><![CDATA[ldap-authentication]]></category>
            <category><![CDATA[entra]]></category>
            <category><![CDATA[ldap-server]]></category>
            <category><![CDATA[ldap]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Sat, 06 Jan 2024 11:02:04 GMT</pubDate>
            <atom:updated>2024-01-06T11:02:04.474Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0_4RwDKPgP5-fN-W" /></figure><p><strong>Lightweight directory access protocol (LDAP</strong>) is a protocol that makes it possible for applications to query user information rapidly.</p><blockquote>Full Article without paywall : <a href="https://harshityadav.in/posts/LDAP-Lightweight-Directory-Access-Protocol-LDAP/">https://harshityadav.in/posts/LDAP-Lightweight-Directory-Access-Protocol-LDAP/</a></blockquote><h3>Why need LDAP ?</h3><p>Someone within your office wants to do two things: Send an email to a recent hire and print a copy of that conversation on a new printer. LDAP (lightweight directory access protocol) makes both of those steps possible.</p><h3>What is LDAP ?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/0*_TWDXKbTJXTToWC5" /></figure><ul><li>Companies store usernames, passwords, email addresses, printer connections, and other static data within directories.</li><li>LDAP is an open, vendor-neutral application protocol for accessing and maintaining that data.</li><li>LDAP can also tackle authentication, so users can sign on just once and access many different files on the server.</li></ul><p><a href="https://www.okta.com/integrations/ldap/">LDAP</a> is a protocol, so it doesn’t specify how directory programs work. Instead, it’s a form of language that allows users to find the information they need very quickly.</p><h3>LDAP Examples</h3><ul><li>It is used in Docker</li><li>Jenkins</li><li>OpenVPN</li></ul><h3>Working</h3><ul><li>Works on plain text over TCP IP over port 389</li><li>LDP + SSL/TLS = LDAPS over port 636</li></ul><p>LDAP is vender-neutral, so it can be used with a variety of different directory programs. Typically, a directory <a href="https://tldp.org/HOWTO/LDAP-HOWTO/whatisldap.html">contains data that is</a>:</p><ul><li><strong>Descriptive.</strong> Multiple points, such as name and location, come together to define an asset.</li><li><strong>Static.</strong> The information doesn’t change much, and when it does, the shifts are subtle.</li><li><strong>Valuable.</strong> Data stored within the directory is critical to core business functions, and it’s touched over and over again.</li></ul><p>An LDAP query typically involves:</p><ul><li><strong>Session connection.</strong> The user connects to the server via an LDAP port.</li><li><strong>Request.</strong> The user submits a query, such as an email lookup, to the server.</li><li><strong>Response.</strong> The LDAP protocol queries the directory, finds the information, and delivers it to the user.</li><li><strong>Completion.</strong> The user disconnects from the LDAP port.</li></ul><p>Before any search commences, the LDAP must authenticate the user. Two methods are available for that work:</p><ul><li><strong>Simple.</strong> The correct name and password connect the user to the server.</li><li><strong>Simple Authentication and Security Layer (SASL).</strong> A secondary service, such as Kerber</li></ul><p>Most LDAP communication is sent without scrambling or encryption, and that could cause security problems. Most companies use Transport Layer Security (TLS) to ensure the safety of LDAP messages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/0*QrSg8wphO2aphTGR" /></figure><p>People can tackle all sorts of operations with LDAP. They can:</p><ul><li><strong>Add.</strong> Enter a new file into the database.</li><li><strong>Delete.</strong> Take out a file from the database.</li><li><strong>Search.</strong> Start a query to find something within the database.</li><li><strong>Compare.</strong> Examine two files for similarities or differences.</li><li><strong>Modify.</strong> Make a change to an existing entry.</li></ul><h3>LDAP Terms to Understand</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/0*p5KVpXdJorXHejCj" /></figure><ul><li><strong>Distinguished name (DN).</strong> This is a unique identifier of each entry that also describes location within the information tree.</li><li><strong>Modifications.</strong> These are requests LDAP users make to alter the data associated with an entry. <a href="https://ldap.com/basic-ldap-concepts/">Defined modification types</a> include adding, deleting, replacing, and increasing.</li><li><strong>Relative distinguished name (RDN).</strong> This is a way of tying DNs together while specifying relative location.</li><li><strong>Schema.</strong> The coding that underpins your LDAP is known as schema.</li><li>Domain Component (DC) . part of the LDAP domain name</li><li>Organizational unit (OU). a container for other objects in LDAP</li><li>Common Name (CN) . <a href="https://stackoverflow.com/questions/18756688/what-are-cn-ou-dc-in-an-ldap-search">CN stands for common name, an attribute that identifies the name of an entry in LDAP</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/0*qzgO4iupY6lH12qS" /></figure><h3>LDAP 2024 ?</h3><p>Sometimes, people use LDAP in concert with other systems throughout the workday. For example, your employees may use LDAP to connect with printers or verify passwords. Those employees may then switch to Google for email, which doesn’t rely on LDAP at all.</p><h3>LDAP</h3><ul><li>LDAP stands for <strong>Lightweight Directory Access Protocol</strong>. It’s a software protocol that lets users find information about people, organizations, and other resources on a network. LDAP can be used on the public internet or a corporate intranet.</li><li>LDAP’s main goals are to store data in the LDAP directory and authenticate users to access it. LDAP is not a database, and it doesn’t store data in a table or row format like traditional relational databases</li><li>LDAP is a standard application protocol, while Active Directory (AD) is a proprietary product.</li><li>LDAP is an interface for communicating with directory services, such as AD. AD is a directory server that uses the LDAP protocol.</li><li>LDAP authentication follows a client-server model. The client, usually an application or service, initiates the authentication process by sending a request to the LDAP server. The LDAP server receives the request and verifies the provided credentials against its database</li></ul><h3>LDAP vs Directory Service</h3><ul><li>LDAP is a protocol that defines how to communicate with and query directory services, which are databases of network resources and users.</li><li>Directory service is a generic term for any service that provides such a database, such as Active Directory, which is a Microsoft product that also offers security and management features</li></ul><h3>LDAP vs. Active Directory</h3><ul><li>LDAP = Protocol</li><li>Active Directory is Database</li></ul><p>LDAP is a protocol that can read Active Directory, but you can also use it with other programs, including those based on Linux. As a vendor-neutral protocol, you could use this tool to work with all kinds of products that have nothing to do with Windows.</p><p>So LDAP and Active Directory work together to help users. But they don’t compete with one another, and they don’t do exactly the same thing.</p><h3>Lightweight Directory Service DS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/0*tYxScY68fcE4WcMl" /></figure><ul><li>AD LDS stands for Active Directory Lightweight Directory Services, which is a directory service that supports directory-enabled applications without the dependencies and limitations of AD DS.</li><li>AD LDS can run on any Windows server or client, does not require DNS or domain controllers, and can have multiple instances with different schemas on one server.</li></ul><h3>LDAP vs SAML</h3><ul><li>LDAP and SAML are both authentication protocols, but they have different use cases.</li><li>LDAP is used for accessing on-premises resources, such as servers, applications, or devices, by installing a client on the user’s device and connecting to a directory service.</li><li>SAML is used for accessing cloud-based resources, such as web applications, by exchanging information between an identity provider and a service provider, without storing credentials on the service provider</li></ul><h3>LDAP vs Kerberos</h3><p>Kerberos is a protocol for network authentication, using secret-key cryptography for secure communication. It’s designed for strong authentication and supports Single Sign-On (SSO). <a href="https://www.geeksforgeeks.org/difference-between-ldap-and-kerberos/">On the other hand, LDAP is used for locating and managing directories in a network, optimized for lookups and read operations</a></p><h3>Apache Directory Studio</h3><p>Apache Directory Studio is a complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS.</p><p><a href="https://directory.apache.org/studio/">https://directory.apache.org/studio/</a></p><h3>Reference :</h3><ul><li><a href="https://www.okta.com/identity-101/what-is-ldap/">https://www.okta.com/identity-101/what-is-ldap/</a></li><li><a href="https://www.youtube.com/watch?v=0FwOcZNjjQA">https://www.youtube.com/watch?v=0FwOcZNjjQA</a></li></ul><p><a href="https://harshityadav.in/categories/azure/">Azure</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78f7d2cb2294" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notes FreeCodeCamp Master Behavioral Interviews]]></title>
            <link>https://harshityadav95.medium.com/notes-freecodecamp-master-behavioral-interviews-8cd21d3f0258?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cd21d3f0258</guid>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[faang-interview]]></category>
            <category><![CDATA[notes]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[freecodecamp]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Thu, 04 Jan 2024 20:33:45 GMT</pubDate>
            <atom:updated>2024-01-04T20:33:45.085Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8hpSMnCwCxY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8hpSMnCwCxY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8hpSMnCwCxY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/86074fd6e95efd6393d8273dcdfb716d/href">https://medium.com/media/86074fd6e95efd6393d8273dcdfb716d/href</a></iframe><blockquote>Full Article without Paywall : <a href="https://harshityadav.in/posts/Behavioral-Interviews-STAR-Questions/">https://harshityadav.in/posts/Behavioral-Interviews-STAR-Questions/</a></blockquote><p><strong>Slide Deck : </strong><a href="https://docs.google.com/presentation/d/16DNAiuCC_UohosO61I1UQvIdWFrjlUz7/edit#slide=id.p1"><strong>Google Slides</strong></a></p><h3>**What’s In it**</h3><ul><li>The STAR method.</li><li>How to Prepare, Research, and Present.</li><li>Categories of Behavioral Interviews.</li><li>50 Behavioral Questions and their Answers.</li><li>Dealing with easy and difficult questions.</li><li>Non-verbal communication.</li><li>Resources and follow-ups.</li></ul><h3>Types of Interviews</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*76MMcysp4JN-Mub1" /></figure><h3>Understanding Behavioral Interviews</h3><ul><li>Explanation: Interviews focused on past behavior as a predictor of future performance.</li><li>Purpose: To assess suitability based on real-life examples.</li></ul><h3>Behavioral vs. Traditional Interviews</h3><ul><li>Focus on real-life experiences vs. hypothetical questions</li><li>Assess soft skills and problem-solving abilities</li><li>Example-driven vs. general questioning.</li></ul><h3>Why Behavioral Interviews Matter</h3><ul><li>Accurate predictor of job performance</li><li>Helps identify candidates with the right Mind set.</li><li>Reduces hiring biased</li></ul><h3>The STAR Method Explained</h3><ul><li>Situation</li><li>Task</li><li>Action</li><li>Result</li></ul><h3>Breaking Down the STAR Method</h3><ul><li>Situation: Setting the context for your story,</li><li>Task: Describing the challenge or responsibility.</li><li>Action: Detailing the steps, you took.</li><li>Result: Highlighting the outcomes and learnings.</li></ul><h3>Identifying Your Strengths and Weaknesses</h3><ul><li>Methods to identify personal strengths</li><li>Acknowledging and addressing weaknesses</li></ul><h3>Reflecting on Relevant Past Experiences</h3><ul><li>How to recall and select job-relevant experiences</li><li>Structuring your experiences for interview storytelling</li></ul><h3>Dive Deep into Job Requirements</h3><ul><li>Analyzing the job description</li><li>Matching skills and experiences with job requirements</li></ul><h3>Company Culture and Values</h3><ul><li>How to Research</li><li>How company values align with personal values</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/0*aXu-anyzyXmRtab-" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/0*C0fq9C0UerA5T-fz" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*xJKpsIkWlS1BNuwb" /></figure><h3>Teamwork &amp; Collaboration</h3><ul><li>Cooperation</li><li>Empathy</li><li>Open-Mindedness</li></ul><h3>Problem-Solving</h3><ul><li>Critical Thinking</li><li>Analysis</li><li>Creativity</li><li>Logic</li></ul><h3>Adaptability</h3><ul><li>Resiliency</li><li>Flexibility</li><li>Agility</li></ul><h3>Communication</h3><ul><li>Interpersonal skills</li><li>Listening</li><li>Articulation</li><li>Diplomacy</li></ul><h3>Leadership</h3><ul><li>Responsibility</li><li>Initiative</li><li>Accountability</li><li>Vision</li></ul><h3>Teamwork &amp; Collaboration</h3><ol><li>Give an example of a challenging &amp; successful team project you were a part of. • What made it successful and what made it challenging?</li><li>Tell a time when you had to deal with a difficult client or coworker.</li><li>Can you describe a time when you had to deal with a team member who wasn’t pulling their weight?</li><li>How do you handle a situation where you disagree with a supervisor?</li><li>Describe when you had to use your understanding to lead a team.</li><li>Can you talk about a time when you had to coordinate with different departments to complete a project?</li><li>Tell me about a time when you had to rely on your presentation skills to influence someone’s opinion.</li><li>Describe a situation where you had to resolve an interpersonal conflict at work.</li><li>How do you approach working in a diverse and inclusive team environment?</li><li>Can you give an example of how you have motivated others?</li></ol><h3>Problem Solving</h3><ol><li>Describe a project where you had to use your problem-solving skills.</li><li>Tell about a time when you made a mistake. How did you handle it?</li><li>Describe a situation where you had to be particularly attentive to details. How did you handle that?</li><li>Can you talk about a time when you had to persuade others to see things your way?</li><li>Tell me about a time when you showed initiative at work.</li><li>Describe a situation where you had to take the lead on a project.</li><li>Can you give an example of a time when you went above and beyond your job duties?</li><li>Tell me about a time when you had to innovate to solve a problem.</li><li>Describe a time when you had to make a tough decision quickly.</li><li>How do you approach learning new skills or technologies? Provide an example.</li></ol><h3>Adaptability</h3><ol><li>Tell me about a time you had to adapt to a significant change in the workplace.</li><li>Describe a situation where you had to gather information from multiple sources. How did you determine which information was most relevant?</li><li>Can you talk about a time when you had to work under pressure?</li><li>How do you handle meeting tight deadlines?</li><li>Describe a time when you had to learn something new in a short period. How did you manage?</li><li>Tell me about a time when you had to adapt your communication style to suit a particular audience.</li><li>Describe an instance where you had to work with limited resources.</li><li>Can you talk about a long-term project you managed? How did you keep everything moving along in a timely manner?</li><li>Tell me about a time when you had to balance competing priorities and how you handled it.</li><li>Describe a situation where you had to be patient in order to achieve your goal.</li></ol><h3>Communication</h3><ol><li>Describe a situation where you had to use your communication skills to resolve a conflict.</li><li>Tell me about a time when you had to give critical feedback to someone. How did you approach it?</li><li>Describe a project where you took a creative approach to solve a problem.</li><li>Can you provide an example of a time when you had to juggle several projects at the same time?</li><li>How do you prioritize your work when you have multiple projects to handle?</li><li>Describe a time when you had to use your negotiation skills.</li><li>Tell me about a time when you had to manage conflicting priorities.</li><li>How do you handle constructive criticism?</li><li>Can you describe a time when you had to communicate complex information clearly?</li><li>Describe a situation where you had to actively listen to someone to understand their perspective.</li></ol><h3>Leadership</h3><ol><li>Give an example of a goal you set and how you achieved it.</li><li>Have you ever had to make an unpopular decision? How did you handle the feedback?</li><li>Have you ever worked on a project that failed? What did you learn from that experience?</li><li>Can you give an example of how you have handled a high-stress situation?</li><li>Tell me about a time when you had to take responsibility for an error made by someone else.</li><li>How do you assess the success of a project? Give an example.</li><li>Tell me about a time when you had to decide without all the information you needed.</li><li>Describe a situation where you had to analyze data and make a recommendation. What approach did you take?</li><li>Have you ever faced an ethical dilemma at work? How did you handle it?</li><li>Describe a situation where you took a risk and it paid off.</li></ol><h3>Dealing with Difficult Questions</h3><ul><li>Understanding Difficult Questions:</li><li>Weaknesses or Failures:</li><li>Strategies for Thinking on Your Feet:</li><li>Stay calm and composed.</li><li>Use the pause to organize thoughts.</li><li>Apply the STAR for structure.</li><li>Example</li></ul><h3>Incorporating Emotional Intelligence</h3><ul><li>Importance of Emotional Intelligence</li><li>Demonstrating Empathy and Self-Awareness</li><li>Balancing Professional and Personal Anecdotes</li><li>Emotional Intelligence in Action</li></ul><h3>Non-verbal communication</h3><ul><li>Body Language</li><li>Eye Contact</li><li>Facial Expression</li><li>Use of Space</li><li>Virtual Interview</li></ul><h3>Preparation Strategies</h3><ul><li>Write some stories and experiences.</li><li>Practice STAR.</li><li>Do Mock.</li><li>Be in the moment.</li></ul><h3>Resources</h3><ul><li>Book:</li><li>Cracking The Coding Interview</li><li>101 Great Answers to the Toughest Interview Questions</li><li>Online Courses: LinkedIn learning, Coursera, Udemy</li><li>Website: Levels.fyi, Glassdoor</li><li>Reddit: r/jobs, r/interviews, r/cscareerquestions</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cd21d3f0258" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notes: Azure Front Door]]></title>
            <link>https://harshityadav95.medium.com/notes-azure-front-door-35a2d38da921?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/35a2d38da921</guid>
            <category><![CDATA[azure-services]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[azure-front-door]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Fri, 15 Dec 2023 19:12:43 GMT</pubDate>
            <atom:updated>2023-12-15T19:12:43.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BYvbsAxiAljFUAqa" /></figure><blockquote><em>Navigating Azure Front Door : </em><a href="https://learn.microsoft.com/en-us/azure/frontdoor/"><em>https://learn.microsoft.com/en-us/azure/frontdoor/</em></a></blockquote><p>Full Article : <a href="https://harshityadav.in/posts/Azure-Front-Door/">https://harshityadav.in/posts/Azure-Front-Door/</a></p><h3>What is the difference between Azure Front Door and Azure Application Gateway?</h3><ul><li>Azure Front Door and Azure Application Gateway are both load balancers for HTTP/HTTPS traffic, but they have different scopes.</li><li><strong>Front Door is a global servic</strong>e that can distribute requests across regions, while Application Gateway is a regional service that can balance requests within a region.</li><li>Azure Front Door works with scale units, clusters, or stamp units, while Azure Application Gateway works with VMs, containers, or other resources in the same scale unit.</li></ul><p>also …..</p><h3>Q. When should I deploy an Application Gateway behind Front Door?</h3><h3>Q. Can I deploy Azure Load Balancer behind the Front Door?</h3><blockquote><a href="https://learn.microsoft.com/en-us/azure/frontdoor/front-door-faq#what-is-the-difference-between-azure-front-door-and-azure-application-gateway-"><em>https://learn.microsoft.com/en-us/azure/frontdoor/front-door-faq#what-is-the-difference-between-azure-front-door-and-azure-application-gateway-</em></a></blockquote><h3>Advantages</h3><h3>Layer 7 Load Balancing</h3><ul><li>A Layer 7 load balancer is a network device that distributes traffic based on the content of the messages, such as the URL, cookie, or header.</li><li>It can make smart routing decisions and apply optimizations or transformations to the traffic, such as compression, encryption, or caching.</li><li>It also uses buffering to offload slow connections from the servers, which improves performance.</li></ul><h3>Faster Failover</h3><p>Faster failover in load balancing is a feature that allows the load balancer to quickly detect and redirect traffic from a failed or unhealthy server to a healthy one</p><ul><li>Faster failover can be achieved by using various methods, such as:</li><li>Active health checks: The load balancer periodically sends requests to the servers and monitors their responses</li><li>Passive health checks: The load balancer analyzes the traffic from the servers and detects any errors or anomalies.</li><li>Feedback loops: The load balancer receives feedback from the servers or other components about their status and performance</li></ul><h3>Dynamic Site Acceleration (DSA)</h3><p>Dynamic Site Acceleration (DSA) is a technique used to improve the performance and responsiveness of websites, especially for users located far from the origin server.</p><ul><li>Optimizing the connection between the user and the server, by using techniques like TCP multiplexing, HTTP keep-alive, and SSL offloading.</li><li>Prefetching and caching some parts of the dynamic content, such as images, scripts, or stylesheets, that are common across different pages or users.</li><li>Compressing and minifying the dynamic content to reduce its size and bandwidth consumption</li><li>Routing the dynamic content through the optimal network path, by using techniques like route optimization, edge computing, and anycast.</li></ul><h3>TLS/ SSL offloading</h3><ul><li>TSL/SSL offloading is a technique that reduces the processing load on the web server by delegating the encryption and decryption of the traffic to another device, such as a load balancer or a proxy. This way, the web server can focus on its main tasks and improve its performance and resource utilization</li><li>TSL/SSL offloading can also enable additional features, such as traffic inspection, malware detection, or protocol enhancement</li></ul><h3>Firewall + DDoS protection</h3><ul><li>It is a stateful firewall that can filter traffic based on rules, protocols, ports, and IP addresses.</li><li>A stateful firewall is a kind of firewall that keeps track of and monitors the state of active network connections while analyzing incoming traffic and looking for potential threats</li><li>It also supports threat intelligence, TLS inspection, and intrusion detection and prevention.</li></ul><h3>Cookie-based affinity</h3><ul><li>Cookie-based affinity is a feature that allows a load balancer to direct subsequent traffic from a user session to the same server for processing.</li><li>It works by setting a cookie in the user’s browser that contains a hash value of the server’s identifier. The load balancer can then read the cookie and route the traffic to the same server.</li><li><a href="https://learn.microsoft.com/en-us/azure/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues">This feature is useful when the session state is saved locally on the server and needs to be maintained for the user session</a></li></ul><h3>Caching</h3><ul><li>Caching in Azure Front Door can be configured on a per-route basis, by enabling caching and specifying the query string caching behavior.</li><li>You can also enable compression for Front Door to compress the responses to the client. Caching in Azure Front Door relies on the HTTP headers of the origin responses, such as Cache-Control, Expires, <strong>and ETag</strong>, to determine the caching behavior and validity of the content.</li></ul><h3>Reference :</h3><ul><li><a href="https://learn.microsoft.com/en-us/azure/frontdoor/front-door-overview">https://learn.microsoft.com/en-us/azure/frontdoor/front-door-overview</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35a2d38da921" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redis Conference Bangalore 2023]]></title>
            <link>https://harshityadav95.medium.com/redis-conference-bangalore-2023-ddc002f0e44f?source=rss-6136764c2336------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddc002f0e44f</guid>
            <category><![CDATA[redi̇s]]></category>
            <category><![CDATA[redis]]></category>
            <category><![CDATA[meesho]]></category>
            <category><![CDATA[bangalore]]></category>
            <category><![CDATA[razorpay]]></category>
            <dc:creator><![CDATA[Harshit Yadav]]></dc:creator>
            <pubDate>Sat, 02 Dec 2023 12:09:25 GMT</pubDate>
            <atom:updated>2023-12-02T12:10:15.362Z</atom:updated>
            <content:encoded><![CDATA[<h3>Redis Conference Bangalore 2022</h3><blockquote>Paywall free Link : <a href="https://harshityadav.in/posts/Redis-Confrence-Bangalore-2022/">https://harshityadav.in/posts/Redis-Confrence-Bangalore-2022/</a></blockquote><h3>New in Redis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*THePKH5gWqL1MkUx" /></figure><p>![IMG_202</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hm-ulxAzSXVs2aGV" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*e3ZSe1vH7jvIe9qf" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TjMQBIWVomsy54Lv" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gZeOOYWZG6b9W4h8" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zDSSb7CEkvct0P7O" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6J-ks9McjGucrK3H" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f5d60AW8OHsJ58Xr" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8WLNiOYiC0aASWxQ" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F4AbB79xFI3bhJsp" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fZY2_o9DfVN7HvrC" /></figure><h3>MEESHO</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3DRbhDdOuy97EO6O" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jGayVjbQLwt1dmKT" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IlvRV7r7Rilb8xb-" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eE8CmnTo96mhdSmi" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bl8AHCLIhtb0Vx-e" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hhbxLl8lc5h4pJw7" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ph1lXt-fd2fX0chz" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pkzgccZg3bnxXkBm" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3kS9DLj3Kvn7N17f" /></figure><h3>Razorpay</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7_O0dkscP5Ddj1nX" /></figure><h3>Redis Enterprise</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wS_bR-NPPlB-Ybz6" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H-fw0YiW5exKN3KB" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kpIsKs4LLuvw0_Kl" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddc002f0e44f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>