<?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[Narasimman Tech - Medium]]></title>
        <description><![CDATA[DevOps, Machine Learning, AI, Cloud, Programming, do any of these topics interest you? If so, then you are at the right place! Our blogs will help you succeed in this technology-driven world by providing carefully curated and updated content on DevOps, Linux, AI, Cloud, and more. - Medium]]></description>
        <link>https://medium.com/narasimman-tech?source=rss----c19b12d3492d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Narasimman Tech - Medium</title>
            <link>https://medium.com/narasimman-tech?source=rss----c19b12d3492d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:21:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/narasimman-tech" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Kubernetes: The Future Of Container Orchestration]]></title>
            <link>https://medium.com/narasimman-tech/kubernetes-the-future-of-container-orchestration-fb81da71bf4b?source=rss----c19b12d3492d---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb81da71bf4b</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[container-orchestration]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Lakshmi Narasimman V]]></dc:creator>
            <pubDate>Thu, 19 May 2022 11:15:10 GMT</pubDate>
            <atom:updated>2022-05-20T15:14:50.145Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*8NdVZsj-NDlWewMDOEnjqg.png" /></figure><h4>Introduction</h4><p>Kubernetes is an open-source system that takes care of everything from deployment, scaling, and management for your applications. It has gained much traction in the past few years, and for a good reason! Kubernetes provides many features and benefits that make it an attractive choice for organisations looking to deploy containerized applications. It is also very popular with developers, who find it easy to use and configure.</p><p>In this blog post, we’ll take a look at some of the features of Kubernetes that make it such an attractive option for container orchestration. We’ll also discuss some of the challenges you may encounter when using Kubernetes. By the end of this post, you should have a good understanding of what Kubernetes is and why it is becoming the standard for container orchestration.</p><h4>History Of Kubernetes</h4><p>Kubernetes was created by Google in 2014. It was designed to orchestrate containers on a large scale, and it quickly became one of the most popular container orchestration tools. In 2015, Google open-sourced Kubernetes, and it became a part of the Cloud Native Computing Foundation (CNCF). It is now used by some of the biggest companies globally, including Amazon, Facebook, and Microsoft. Kubernetes is also becoming the standard for container orchestration in the cloud.</p><h4>What Are The Features Of Kubernetes That Make It So Attractive?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*LHHLfa8lCvKM5bkiKbjKMw.png" /></figure><p>There are many features that make Kubernetes an attractive option for container orchestration. Let’s take a closer look at some important ones here.</p><h4>1. Ease Of Use</h4><p>One of the most significant selling points of Kubernetes is its ease of use. It is designed to be simple to use and configure. Making Kubernetes a great choice for organizations that want to deploy containerized applications quickly and easily. Kubernetes also has excellent documentation. The documentation is very thorough and includes examples that show you how to use the various features of Kubernetes.</p><h4>2. Scalability</h4><p>Kubernetes is designed to be scalable. It can easily handle deployments of hundreds or even thousands of containers. This makes it a great choice for organisations that have large-scale deployments. Kubernetes can also scale down when necessary, which makes it very efficient.</p><h4>3. High Availability</h4><p>Kubernetes is designed to be highly available. This means that it can keep your applications running even if there are problems with the underlying infrastructure. Kubernetes can do this by replicating containers across multiple nodes.</p><h4>4. Self-Healing</h4><p>Kubernetes is designed to be self-healing. This means that it can automatically detect and resolve issues with your applications. This helps to keep your applications running smoothly and prevents outages.</p><h4>5. Automatic Rollbacks</h4><p>Kubernetes can automatically roll back changes that cause issues with your applications. This helps to prevent outages and keep your applications running smoothly.</p><h4>How To Get Started With Kubernetes?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*FO3qIcaJsIwmCLdT8Vei8w.png" /></figure><p>If you’re interested in using Kubernetes, there are a few things that you need to do. First, you need to install Kubernetes. You can do this using a tool called Minikube. Minikube is a tool that helps you install and run Kubernetes on your local machine.</p><p>You can also install Kubernetes on a cloud platform like Amazon Web Services (AWS), Google Cloud Platform (GCP), or Microsoft Azure. There are several ways to do this, and the best way will depend on your specific needs. Once you have Kubernetes installed, you need to create a deployment. A deployment is a group of containers that are deployed together. You can use deployments to deploy your applications.</p><p>Once you have created a deployment, you have to create a service. A service is an entity that provides access to your application. Services are typically used to expose your application to the outside world. You can also use services to load balance traffic between multiple application instances.</p><h4>What Are Some of the Challenges You May Encounter When Using Kubernetes?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2d6KCf0rV6r_lgbUB4mKqw.png" /></figure><p>While Kubernetes is a great tool, there are some challenges that you may encounter when using it. We’ll take a look at some of the most common ones here.</p><h4>1. Complexity</h4><p>Kubernetes can be complex to use. This is because it has numerous features and options. This can make it challenging to learn and configure. Additionally, Kubernetes is designed to be scalable. This means that it can easily handle deployments of hundreds or even thousands of containers. This can make it challenging to manage large-scale deployments.</p><h4>2. Security</h4><p>Kubernetes is a complex system. This complexity can make it difficult to secure. Additionally, Kubernetes is designed to be highly available. This means that it can keep your applications running even if there are problems with the underlying infrastructure. This can make it challenging to protect your data and maintain compliance.</p><h4>3. Upgrades</h4><p>Kubernetes is constantly evolving. This means that new versions are released frequently. This can make it difficult to keep up with the latest version. Additionally, upgrading Kubernetes can be complex and time-consuming.</p><h4>4. Support</h4><p>Kubernetes is a complex system. This complexity can make it difficult to find support when you need it. Additionally, Kubernetes is an open-source project. This means that no company provides official support for Kubernetes.</p><h4>5. Cost</h4><p>Kubernetes can be expensive to use. This is because it requires many resources to run. Additionally, Kubernetes is a complex system. This complexity can make it difficult to manage. This can lead to increased costs.</p><h4>Why Is Kubernetes Becoming The Standard For Container Orchestration?</h4><p>Kubernetes is becoming the standard for container orchestration for a few reasons. DevOps teams find that Kubernetes is easier to use than other container orchestration tools. Kubernetes is also more scalable than other tools, perfect for cloud-based applications. Finally, Docker containers and Kubernetes work well together, making it easy to deploy and manage containerised applications.</p><h4>Who Uses Kubernetes?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*AWTUYX4mICQje-sMY9J6mQ.png" /></figure><p>Kubernetes is used by organisations of all sizes, including some of the world’s largest companies. A few notable users include IBM, Lyft, The New York Times, and Shopify. Kubernetes is also growing in popularity among developers. A 2019 survey found that Kubernetes was the most popular container orchestration tool among respondents. It’s not hard to see why Kubernetes is so popular. The tool offers several advantages over other container orchestration tools. These advantages make Kubernetes the perfect tool for managing containerized applications.</p><h4>Final Thoughts</h4><p>Kubernetes is a great tool for managing containerized applications. It’s easy to use, scalable, and popular among developers. So, if you’re looking for a container orchestration tool, Kubernetes is a great option. Remember to do your research before getting started, as it can be a complex tool. With that said, Kubernetes is the future of container orchestration.</p><p><strong>Follow me on Medium and Subscribe to my Newsletter:</strong></p><p><a href="https://medium.com/subscribe/@narasimman_tech">Get an email whenever Lakshmi Narasimman V publishes.</a></p><p><a href="https://narasimmantech.com/#/portal/signup"><strong>Subscribe</strong></a><strong> to my Weekly Newsletter on my website to get Premium articles straight into your Inbox:</strong></p><p><a href="https://narasimmantech.com/#/portal/signup">Narasimman Tech</a></p><p>Follow me on <a href="https://twitter.com/narasimman_tech"><strong>Twitter</strong></a>.</p><p><strong><em>Additional Resources:</em></strong></p><ul><li>Official Website</li></ul><p><a href="https://kubernetes.io/">Production-Grade Container Orchestration</a></p><ul><li>Source Code:</li></ul><p><a href="https://github.com/kubernetes/kubernetes">GitHub - kubernetes/kubernetes: Production-Grade Container Scheduling and Management</a></p><ul><li>MiniKube:</li></ul><p><a href="https://minikube.sigs.k8s.io/docs/start/">minikube start</a></p><ul><li>K3S:</li></ul><p><a href="https://k3s.io/">Lightweight Kubernetes</a></p><p><strong>Join my Tech Community:</strong></p><p><a href="https://community.narasimmantech.com/">Narasimman Tech Community</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb81da71bf4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narasimman-tech/kubernetes-the-future-of-container-orchestration-fb81da71bf4b">Kubernetes: The Future Of Container Orchestration</a> was originally published in <a href="https://medium.com/narasimman-tech">Narasimman Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Infrastructure as Code and Why?]]></title>
            <link>https://medium.com/narasimman-tech/what-is-infrastructure-as-code-and-why-b87046251cb2?source=rss----c19b12d3492d---4</link>
            <guid isPermaLink="false">https://medium.com/p/b87046251cb2</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Lakshmi Narasimman V]]></dc:creator>
            <pubDate>Sun, 15 May 2022 14:13:42 GMT</pubDate>
            <atom:updated>2022-05-15T18:16:19.011Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*e9o5FxXcS1sJseqH_8cPZw.jpeg" /><figcaption><a href="https://www.freepik.com/free-photo/observation-urban-building-business-steel_1046153.htm#query=infrastructure&amp;position=5&amp;from_view=search">freepik</a></figcaption></figure><h3>Why Should You Learn Infrastructure as Code as a DevOps Engineer?</h3><blockquote>Dynamic Systems for the Cloud Age — Kief Morris</blockquote><p>This blog post introduces you to the concept of Infrastructure as Code, otherwise known as IaC.</p><h4>Introduction</h4><p>Today, companies like Microsoft, Uber, Netflix, and even banks are using cloud infrastructure, but a few years back, major corporations thought the cloud was only for startups and small organizations. Cloud and automation technologies remove barriers to making changes to production systems, but this creates new challenges. It becomes harder day by day to manually manage all the servers as your infrastructure grows, and new services are released frequently. This is where the Infrastructure as Code concept and its tools comes in handy.</p><h4>Infrastructure as Code</h4><p>The infrastructure as Code (IaC) concept is simple, you define your entire infrastructure as code. This approach is based on practices from software development. For example, if you want to deploy an EC2 instance on AWS, traditionally you use AWS console or AWS-CLI, but using a popular IaC tool called Terraform you write a configuration file, which consists of your EC2 configurations written similar to a function defined in programming. You can use automation to test changes to your code before applying them to your systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*ATNMu1nQTnIXauJYXlDDGw.png" /></figure><h4>Should you build first and automate later? No!</h4><p>Getting started with Infrastructure takes a lot of effort and has a steep curve. You have to set up the tools, and services to automate infrastructure delivery, especially if you are adopting a new infrastructure platform. You may think that you can quickly provision the infrastructure manually, and worry about automating it later. But this is a bad idea because automation should enable faster delivery, even for new things. Automation makes it easier and simple to write automated tests, and you can quickly address a problem and rebuild it. The worst part is, that manually configured system are harder to automate.</p><h4>Three Core Practices for Infrastructure as Code</h4><p>According to Kief Morris, the author of the <a href="https://www.oreilly.com/library/view/infrastructure-as-code/9781098114664/">Book Infrastructure as Code</a>, there are three important practices for implementing infrastructure as code:</p><p><strong>Define Everything as Code</strong></p><p>Defining all your stuff “as code” is a core practice for making changes rapidly and reliably. Here are a couple of reasons why:</p><ol><li><strong>Reusability</strong> — If you define something as code, you can build multiple instances of the same. You can share with others, destroy the existing infrastructure, and re-deploy with the same configuration.</li><li><strong>Consistency</strong> — No matter how much time you run, things built from code are built the same way. This makes system behavior predictable, makes testing more reliable and enables continuous testing and delivery.</li><li><strong>Transparency</strong> — Everyone can look at the code and see how the infrastructure is built, and they can learn how to use the code in their infrastructure.</li></ol><p><strong>Continuously Test and Deliver All Work in Progress.</strong></p><p><strong>Build Small, Simple Pieces That You Can Change Independently.</strong></p><h4>Benefits of Infrastructure as Code</h4><ul><li><strong>Rapid Delivery</strong> — Manually configuring infrastructure slows down product delivery time. With Infrastructure as Code, your infrastructure is stable, consistent, and easily modifiable. It is an enabler for the rapid delivery of value.</li><li><strong>Reduced Risks and Errors</strong> — Manually configuring infrastructure is error-prone and risky. But using IaC reduces the effort and risk of introducing changes to your infrastructure.</li><li><strong>Self-documenting</strong> — If you are manually configuring your infrastructure, it is easy to forget, and documenting them can be time-consuming. With Infrastructure as code, it is self-documenting like any other code.</li><li><strong>Visibility</strong> — With IaC, everyone can know the current configuration of the infrastructure. Anyone with permission to access the code can see what the current configuration is.</li><li><strong>Easy to collaborate</strong> — Because your infrastructure is written as a code, it is easy to share and collaborate with other team members, especially when a new member joins the team. You can share your configuration with other teams for them to deploy the same infrastructure.</li><li><strong>Easy to Scale</strong> — With Infrastructure as Code, you can scale your infrastructure easily by just copying the existing code or adding a few extra lines.</li><li>Using IaC enables you or your team to have a reliable, secure, and cost-effective infrastructure and makes governance, security, and compliance controls visible.</li><li>You can use a Version Control System, like git, to easily track changes to your infrastructure and revert if you’d like to.</li></ul><p>There are so many benefits of using Infrastructure of Code tools over manually configuring your infrastructure.</p><h4>Infrastructure as Code Tools</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1afCh7G2XqgQ_BxO4ZnlBw.png" /></figure><ol><li><a href="https://www.terraform.io/">Terraform</a> — Terraform is a popular infrastructure as code (IaC) tool that is used to provision infrastructure. Terraform allows you to provision and manage multiple cloud providers easily. You can use Terraform to provision and maintain Docker Containers, Kubernetes Clusters, and more.</li><li><a href="https://aws.amazon.com/cloudformation/?nc2=type_a">AWS CloudFormation</a> — AWS CloudFormation is a service offered by Amazon Web Services to help you provision infrastructure on AWS. They provide tight integration with their other services.</li><li><a href="https://www.ansible.com/">Ansible</a> — Ansible can be used to provision infrastructure but is best to combine it with Terraform. You can provision infrastructure and maintain the infrastructure using Ansible.</li><li><a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview">Azure Resource Manager</a></li><li><a href="https://cloud.google.com/deployment-manager/docs">Google Cloud Deployment Manager</a></li><li><a href="https://puppet.com/">Puppet</a></li><li><a href="https://www.chef.io/">Chef</a></li><li><a href="https://www.vmware.com/in/support/acquisitions/saltstack.html">SaltStack</a></li></ol><h4>Choosing The Right Tools</h4><p>Depending on the tool, it can be either imperative or declarative.</p><h4>Imperative vs Declarative</h4><ul><li>A declarative approach also keeps a list of the current state of your system objects, which makes taking down the infrastructure simpler to manage. Some tools are Terraform, CloudFormation, SaltStack, and Puppet.</li><li>An imperative approach instead defines the specific commands needed to achieve the desired configuration, and those commands then need to be executed in the correct order. Some tools that use an imperative approach are Chef and Ansible.</li></ul><h4>Why Does IaC matter for DevOps?</h4><p>Infrastructure as code is an important part of implementing DevOps practices and the continuous integration/continuous delivery (CI/CD) cycle. A developer can run a script to have their infrastructure ready. So that application deployments aren’t held up waiting for the infrastructure, and sysadmins aren’t managing time-consuming manual processes.</p><h4>Conclusion</h4><p>To get the value of cloud and infrastructure automation, you need a Cloud Age mindset. This means exploiting speed to improve quality and building quality to gain speed. Automating your infrastructure takes work, especially when you’re learning how to do it. But doing it helps you to make changes, including building the system in the first place.</p><p><a href="https://narasimmantech.com/#/portal/signup">Subscribe to my Weekly Newsletter</a> and Follow for more DevOps, SRE, Linux, Python, Golang, Artificial Intelligence, and Data Science.</p><p><em>References and Resources:</em></p><ul><li><a href="https://amzn.to/3wml2hm">Infrastructure as Code</a> by Kief Morris.</li><li><a href="https://www.redhat.com/en/topics/automation/what-is-infrastructure-as-code-iac">https://www.redhat.com/en/topics/automation/what-is-infrastructure-as-code-ia</a>c</li><li><a href="https://amzn.to/3FKvJyO">Terraform Cookbook</a></li></ul><p><strong>Check out my Website:</strong></p><p><a href="https://narasimmantech.com/">Narasimman Tech</a></p><p><strong>Join my Community:</strong></p><p><a href="https://community.narasimmantech.com/">Narasimman Tech Community</a></p><p><strong>Follow me on </strong><a href="https://twitter.com/narasimman_tech"><strong>Twitter</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b87046251cb2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narasimman-tech/what-is-infrastructure-as-code-and-why-b87046251cb2">What is Infrastructure as Code and Why?</a> was originally published in <a href="https://medium.com/narasimman-tech">Narasimman Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monolithic and Microservices Architecture]]></title>
            <link>https://medium.com/narasimman-tech/monolithic-and-micro-service-architecture-891934f47f1c?source=rss----c19b12d3492d---4</link>
            <guid isPermaLink="false">https://medium.com/p/891934f47f1c</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[monolith]]></category>
            <dc:creator><![CDATA[Lakshmi Narasimman V]]></dc:creator>
            <pubDate>Sat, 14 May 2022 05:36:32 GMT</pubDate>
            <atom:updated>2022-05-13T14:28:21.425Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iAUTRTj8gs5kvp0iajSRXQ.jpeg" /><figcaption><a href="https://hackernoon.com/microservices-are-hard-an-invaluable-guide-to-microservices-2d06bd7bcf5d">Hackermoon</a></figcaption></figure><h3>Monolithic Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*4svp7vMfNuMRQKjbmuljJA.jpeg" /><figcaption><a href="https://microservices.io/patterns/monolithic.html">Monolithic Architecture</a></figcaption></figure><h4>Introduction</h4><p>Monolithic Architecture is a traditional way of developing server-side or client-side applications. These applications have a single large codebase in which the application is developed. For example, a Java application can be deployed from a single WAR file onto the application server. To update the code, add features or make any changes, you have to re-build and re-deploy the entire application. This may break the entire application if something goes wrong.</p><h4>Three-Tire Architecture:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*c0HZgicJwFwp-jnU3dAalQ.png" /></figure><p>The application stack can be broken into three logical and physical computing tiers:</p><ol><li>Presentation Layer</li><li>Application Layer</li><li>Data Layer</li></ol><h4>Presentation Layer</h4><p>This tire is the user interface and communication layer of the application, where the end-user interacts. This layer can run on top of a web browser, as a desktop application, or as a graphical user interface (GUI) and is built using HTML, CSS, and JavaScript. They communicate with the Application Layer using API.</p><h4>Application Layer</h4><p>This is the core of the application. In this tire, data collected from the presentation layer are processed against other information in the data tier — using business logic, a specific set of business rules. This layer is typically developed using Python, Java, Perl, PHP, or Ruby, and communicates with the Data Layer using APIs.</p><h4>Data Layer</h4><p>Data Layer is also called a database layer. The information processed by the Application Layer is stored and retrieved from here. This can be any type of database such as a relational database like MySQL, Postgresql, etc., or a NoSQL database like MongoDB, Cassandra, etc.,</p><p>There are a few benefits of a three-tier architecture, such as,</p><ul><li>Each tier can run on a separate operating system and server platform.</li><li>Faster development.</li><li>Improved scalability.</li><li>Improved security.</li><li>Improved reliability.</li></ul><p>There are quite a few advantages and many disadvantages to this type of architecture.</p><h4>Advantages:</h4><ul><li>Since it is a single application, it is easy to develop, test and deploy.</li><li>Since this method of application development is used for a long time, there are so many tools available and well tested for production use.</li><li>The application can be scaled horizontally, running multiple copies and routing incoming traffic using a load balancer.</li></ul><h4>Disadvantages:</h4><ul><li>The large, monolithic codebase scares developers, especially ones who are new to the team.</li><li>The application can be difficult to understand and modify.</li><li>You must rebuild and redeploy the entire application for minor bug fixes, to add a feature or changes made to the code. This can break the entire application if something goes wrong.</li><li>Continuous Deployment is difficult.</li><li>For a big project, the size of the application can slow down the start-up time.</li><li>The larger the codebase, the slower the IDE. This makes the developers less productive and difficult to make changes.</li><li>Requires a long-term commitment to a technology stack. You cannot change the programming language used to build the application, to do so you have to rewrite the entire application. This makes it difficult when a long-term developer of the project decides to quit.</li></ul><h4>Microservice Architecture</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RF4TRW2hJe1lP5izfMRsVw.png" /></figure><h4>Introduction</h4><p>Rather than building your application as a Monolith, you break the application into independent chunks of individual services, these services have their functions and database with a specific goal. These services are interconnected and would expose a REST, RPC, or message-based API and most services consume APIs provided by other services. When a client wants to access the application, they talk to the API Gateway rather than directly to the services. Changes to a service like updating, bug fixes, and any other changes occur within each service. Microservices do not reduce the complexity of an application but make it visible so that it is more manageable. Adopting microservices often goes hand in hand with DevOps.</p><h4>Advantages:</h4><ul><li>Breaking an application into fragments of manageable services allows you to develop the application and much easier to understand and maintain.</li><li>Microservices allow you to continuously test, deploy and update services independently, which leads to faster deployment and troubleshooting.</li><li>Rather than being committed to a single technology stack, you can use multiple or adopt new technologies based on the requirement, performance, and complexity of the service.</li><li>You can easily upscale or downscale a service individually based on the incoming traffic or application load. This frees up memory and CPU for other services.</li><li>It is easy to make changes, add features, or fix bugs compared to Monolithic Architecture. This reduces the risk of downtime, and developers can roll back an update or introduce changes to a service without needing to redeploy the entire application.</li><li>It is easy to monitor individual services to identify and resolve any cause of performance issues.</li><li>You can use an orchestration framework to manage individual services. Probably the best known of these orchestration frameworks is Kubernetes.</li></ul><h4>Disadvantages:</h4><ul><li>Microservices come with all the disadvantages of a distributed system.</li><li>Architecting a microservice can be complex and challenging. There’s a lot more planning involved.</li><li>There is a higher chance of communication failure between different services. The communication mechanism between services should be based on either messaging or RPC, and write code to handle partial failure.</li><li>Microservices require extra resources, as each microservice comes with its own runtime environment and data storage.</li><li>Deploying a microservice-based application can be complex. In a Monolithic architecture, the application is simply deployed into multiple servers behind a load balancer, whereas a microservice application typically consists of numerous services.</li></ul><h4>Which one is better?</h4><p>Choosing the right architecture for your next project is important, and it’s inherently difficult to develop complex applications. Monolithic architecture is best suited for a small team or small applications. This reduces the unnecessary complexity of designing microservices. The Microservice architecture is a better option for more complex and evolving applications. Getting multiple microservices to reliably function together as a microservices-oriented program is a difficult task. The trade-offs can be substantial, but so can the benefits.</p><p>Thanks for reading, I will cover topics like moving from Monolith to Microservices and Securing Microservices in a future blog post. Subscribe to receive weekly newsletters of my latest blog posts.</p><p><strong>Check out my Website and Subscribe to My Weekly Newsletter:</strong></p><p><a href="https://narasimmantech.com/">Narasimman Tech</a></p><p><strong>Join My Tech Community:</strong></p><p><a href="https://community.narasimmantech.com/">Narasimman Tech Community</a></p><p><strong>Follow me on Twitter:</strong></p><p><a href="https://twitter.com/narasimman_tech">JavaScript is not available.</a></p><p>References:</p><ol><li><a href="https://articles.microservices.com/monolithic-vs-microservices-architecture-5c4848858f59">Monolithic vs. Microservices Architecture</a></li><li>Pattern: Monolithic Architecture</li><li>YouTube: <a href="https://www.youtube.com/watch?v=qYhRvH9tJKw">What is a microservice architecture and it’s advantages?</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=891934f47f1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narasimman-tech/monolithic-and-micro-service-architecture-891934f47f1c">Monolithic and Microservices Architecture</a> was originally published in <a href="https://medium.com/narasimman-tech">Narasimman Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Awesome Modern Unix Command-Line Tools]]></title>
            <link>https://medium.com/narasimman-tech/10-awesome-modern-unix-command-line-tools-af825e0a2941?source=rss----c19b12d3492d---4</link>
            <guid isPermaLink="false">https://medium.com/p/af825e0a2941</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[command-line]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[unix]]></category>
            <category><![CDATA[terminal]]></category>
            <dc:creator><![CDATA[Lakshmi Narasimman V]]></dc:creator>
            <pubDate>Sat, 14 May 2022 05:36:14 GMT</pubDate>
            <atom:updated>2022-05-19T16:00:15.645Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3kZodl-XR1Aum4W3fzRk-A.png" /><figcaption><a href="https://github.com/GitSquared/edex-ui">edex-ui</a></figcaption></figure><p>Are you Using Linux or Terminal in macOS? If so, here are some of the cool Command-Line Tools you can use for better productivity and speed. I have another Post for <a href="https://narasimmantech.com/modern-alternatives-to-common-unix-commands/">Modern Alternatives to Common Unix Commands</a>. Here’s a list of some of the popular command-line tools:</p><ol><li>fzf - Is a general-purpose command-line fuzzy finder, written in Go. It interactively filters the command line that can be used with any list; files, command history, processes, hostnames, bookmarks, git commits, etc. You can do a lot more than you can imagine. This is one of my favorite. Check out the GitHub repo for more.</li></ol><p><strong>Features:</strong></p><ul><li>Portable, no dependencies.</li><li>Batteries included — Vim/Neovim plugin, key bindings, and fuzzy auto-completion.</li><li>Flexible layout.</li><li>Blazingly fast.</li><li>The most comprehensive feature set.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YvHpk0_aAWNRHOuAfWxshg.gif" /></figure><p>GitHub: <a href="https://github.com/junegunn/fzf">https://github.com/junegunn/fzf</a></p><p>2. dive - Is a tool for exploring a docker image, layer contents, and discovering ways to shrink the size of your Docker/OCI image. It is written in Go.</p><p><strong>Features:</strong></p><ul><li>Show Docker image contents are broken down by layer.</li><li>Indicate what’s changed in each layer.</li><li>Estimate “image efficiency”.</li><li>Quick build/analysis cycles.</li><li>Multiple Image Sources and Container Engines Supported.</li><li>Supports CI Integration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84QW780UH3PEKiQ2GuyhRw.gif" /></figure><p>GitHub: <a href="https://github.com/wagoodman/dive">https://github.com/wagoodman/dive</a></p><p>3. tldr- Is a collaborative cheatsheets for console commands. It aims to be a simpler, more approachable complement to traditional &#39;man pages&#39; and is community maintained. It is written in Markdown.</p><p><strong>Features:</strong></p><ul><li>Easy to read.</li><li>Simple to use.</li><li>Colored output.</li><li>Lists only important/most frequently used options.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aVH9tg8ZgAaPI2ylM8IUcQ.gif" /></figure><p>GitHub: <a href="https://github.com/tldr-pages/tldr">https://github.com/tldr-pages/tldr</a></p><p>4. lazygit - A simple terminal UI for git commands, written in Go with the gocui library.</p><p><strong>Features:</strong></p><ul><li>You can add files easily.</li><li>Resolve merge conflicts.</li><li>Easily check out recent branches.</li><li>Squash down and reword commits.</li><li>Quick pushing/pulling.</li><li>Scroll through logs/diffs of branches/commits/stash.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*fhq2fRIfgMzuoF3mzbVfnw.gif" /></figure><p>GitHub: <a href="https://github.com/jesseduffield/lazygit">https://github.com/jesseduffield/lazygi</a>t</p><p><strong><em>Friendly Reminder: Please Consider Following me if you like my article, 😊! Also, </em></strong><a href="https://narasimmantech.com/#/portal/signup"><strong><em>Subscribe</em></strong></a><strong><em> to my Weekly Newsletter on my website to get Premium articles straight to your Inbox!</em></strong></p><p>5. broot- Is an alternative to the tree command used to see and navigate the directory in a tree format. It is written in Rust.</p><p><strong>Features:</strong></p><ul><li>Find a directory then cd to it.</li><li>You never lose track of file hierarchy while you search.</li><li>You can manipulate your files.</li><li>You can preview files.</li><li>You can sort, and see what takes space.</li><li>Can check git statuses.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5aRc6iBPziYpQlKXSOQ83w.gif" /></figure><p>GitHub: <a href="https://github.com/Canop/broot">https://github.com/Canop/broot</a></p><p>6. hyperfine- It is a command-line benchmarking tool. You can run benchmarks on the CLI commands. Example: benchmark between fd vs find commands. It is written in Rust.</p><p><strong>Features:</strong></p><ul><li>Statistical analysis across multiple runs.</li><li>Support for arbitrary shell commands.</li><li>Cache-clearing commands can be set up before each timing run.</li><li>Export results to various formats: CSV, JSON, Markdown, AsciiDoc.</li><li>Cross-platform.</li></ul><p>and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*gcuny3V4FXpG-nx_D2gxpw.gif" /></figure><p>GitHub: <a href="https://github.com/sharkdp/hyperfine">https://github.com/sharkdp/hyperfine</a></p><p>7. procs- A modern replacement for ps written in Rust.</p><p><strong>Features:</strong></p><ul><li>Colored and human-readable output with automatic theme detection based on terminal background.</li><li>Multi-column keyword search.</li><li>Some additional information which are not supported by ps.</li><li>Pager support.</li><li>Tree view.</li></ul><p>GitHub: <a href="https://github.com/dalance/procs">https://github.com/dalance/procs</a></p><p>8. cheat.sh - Unified access to the best community-driven cheat sheets repositories of the world. It is similar to tldrcommand. It is written using Python.</p><p><strong>Features:</strong></p><ul><li>Has a simple curl/browser/editor interface.</li><li>Covers 56 programming languages, several DBMSes, and more than 1000 most important UNIX/Linux commands.</li><li>Provides access to the best community-driven cheat sheets repositories in the world, on par with StackOverflow.</li><li>Available everywhere, no installation is needed, but can be installed for offline usage.</li><li>Ultrafast, returns answers within 100 ms, as a rule.</li><li>Has a convenient command-line client.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*siVIVUW2t2PEJSHzCwPSSQ.gif" /></figure><p>GitHub: <a href="https://github.com/chubin/cheat.sh">https://github.com/chubin/cheat.sh</a></p><p>9. gping- Is a pingcommand replacement, but with a graph. It is written in Rust.</p><p><strong>Features:</strong></p><ul><li>Graph the ping time for multiple hosts.</li><li>Graph the <em>execution time</em> for commands via the --cmd flag.</li><li>Custom colors.</li><li>Windows, Mac and Linux support.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GVhwofpWXDHHKtUHPS2UEw.gif" /></figure><p>GitHub: <a href="https://github.com/orf/gping">https://github.com/orf/gping</a></p><p>10. glances- Glances an Eye on your system. A top/htop alternative for GNU/Linux, BSD, Mac OS, and Windows operating systems.</p><p><strong>Features:</strong></p><ul><li>Present a large amount of monitoring information through curses or a Web-based interface.</li><li>The information dynamically adapts depending on the size of the user interface.</li><li>It can also work in client/server mode.</li><li>Remote monitoring could be done via terminal, Web interface, or API (XML-RPC and RESTful).</li><li>Stats can also be exported to files or external time/value databases.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Ux67DOFGHGIBZWzkTS75w.gif" /></figure><p>GitHub: <a href="https://github.com/nicolargo/glances">https://github.com/nicolargo/glances</a></p><p>If you have not Checked my other Post, Click down below.</p><p><a href="https://narasimmantech.com/modern-alternatives-to-common-unix-commands">8 Modern Unix alternatives for Common Commands</a></p><p>There are a lot of other CLI tools as well but these are my favorite Command-Line Tools. Check these projects on GitHub for more detailed explanations, installation, configurations, usage, and more. If you like these kinds of stuff, check out my other posts, tutorials, and tips. If you want to stay updated, then subscribe to my Newsletter. As always see you in the next post.</p><p>Visit My Website and Signup to My Weekly Newsletter: <a href="https://narasimmantech.com/">https://narasimmantech.com</a></p><p>Join My Community Forum: https://community.<a href="https://narasimmantech.com/">narasimmantech.com</a></p><p>Follow me on Twitter: <a href="https://twitter.com/narasimman_tech">https://twitter.com/narasimman_tech</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af825e0a2941" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narasimman-tech/10-awesome-modern-unix-command-line-tools-af825e0a2941">10 Awesome Modern Unix Command-Line Tools</a> was originally published in <a href="https://medium.com/narasimman-tech">Narasimman Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Try These 8 Modern Alternatives to Common Unix Commands]]></title>
            <link>https://medium.com/narasimman-tech/try-these-8-modern-alternatives-to-common-unix-commands-e0a295ba708d?source=rss----c19b12d3492d---4</link>
            <guid isPermaLink="false">https://medium.com/p/e0a295ba708d</guid>
            <category><![CDATA[unix]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[command-line]]></category>
            <category><![CDATA[terminal]]></category>
            <dc:creator><![CDATA[Lakshmi Narasimman V]]></dc:creator>
            <pubDate>Sat, 14 May 2022 05:35:55 GMT</pubDate>
            <atom:updated>2022-05-19T16:01:20.583Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0SywjMtUl7GSVFYVpbTJow.png" /></figure><p>If you have used any Unix-like operating systems like GNU/Linux or terminal in the macOS, you will be familiar with <strong>cd, ls, grep, find</strong> and other CLI commands. These tools were written using the C programming language in the 90s and were developed for, or are maintained by, the <a href="https://en.wikipedia.org/wiki/Free_Software_Foundation">Free Software Foundation</a> as part of the <a href="https://en.wikipedia.org/wiki/GNU_Project">GNU Project</a>. Since then, there have been no major changes to these tools/packages. So the open-source community decided to re-write modern replacements/alternatives for these commands using modern programming languages.</p><p>Modern programming languages like Rust and Go are fast, and efficient and are designed to make use of multi-core CPU architectures. These languages are considered as the modern C-like programming languages. The following tools/packages are written using Rust or Go and are modern alternatives for the default command-line tools:</p><ol><li>bat - Is a <em>cat </em>command<em> </em>clone with syntax highlighting and Git integration. It is written in Rust.</li></ol><p><strong>Features:</strong></p><ul><li>Supports syntax highlighting for a large number of programming and markup languages.</li><li>Communicates with git to show modifications with respect to the index.</li><li>By default, bat pipes its own output to a pager (e.g. less) if the output is too large for one screen.</li><li>You can use the -A/--show-all option to show and highlight non-printable characters.</li></ul><p><em>Project Source: </em><a href="https://github.com/sharkdp/bat"><em>https://github.com/sharkdp/bat</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YHrzRB0VZ7nLlNWNmyqbow.gif" /></figure><p>2. fd - Is a replacement for the old find command, which is a powerful tool for finding files, and directories and has a lot of options and flags. It is written in Rust.</p><p><strong>Features:</strong></p><ul><li>Intuitive syntax.</li><li>Regular expression (default) and glob-based patterns.</li><li>Very fast due to parallelized directory traversal.</li><li>Uses colors to highlight different file types.</li><li>Ignores patterns from your .gitignore, by default.</li><li>Ignores hidden directories and files, by default.</li><li>The command name is 50% shorter than find</li></ul><p><em>Project Source: </em><a href="https://github.com/sharkdp/fd"><em>https://github.com/sharkdp/fd</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3hxqEd7CKZzrGqvf7VG7-A.gif" /></figure><p>3. exa - Is a modern replacement for ls command, which is used to list all the files and directories. It is written using Rust.</p><p><strong>Features:</strong></p><ul><li>It uses colors to distinguish file types and metadata.</li><li>It knows about symlinks, extended attributes, and Git.</li><li>It can display icons.</li></ul><p><em>Project Source: </em><a href="https://github.com/ogham/exa"><em>https://github.com/ogham/exa</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AECE0qgMLhHQy8jHOQVWYg.gif" /></figure><p>4. delta - A syntax-highlighting pager for git, diff, and grep output. It is written in Rust.</p><p><strong>Features:</strong></p><ul><li>Language syntax highlighting with the same syntax-highlighting themes as bat.</li><li>Word-level diff highlighting.</li><li>Side-by-side view with line-wrapping.</li><li>Code can be copied directly from the diff.</li><li>Improved merge conflict display.</li><li>n and N keybindings to move between files in large diffs.</li></ul><p><em>Project Source: </em><a href="https://github.com/dandavison/delta"><em>https://github.com/dandavison/delta</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AGZE4vac8juUdepmg8bpiQ.gif" /></figure><p><strong><em>Friendly Reminder: Please Consider Following me if you like my article, 😊! Also, </em></strong><a href="https://narasimmantech.com/#/portal/signup"><strong><em>Subscribe</em></strong></a><strong><em> to my Weekly Newsletter on my website to get Premium articles straight to your Inbox!</em></strong></p><p>5. zoxide- Is a Rust implementation to the cd command, which stands for &#39;change directory&#39;.</p><p><strong>Features:</strong></p><ul><li>It remembers which directories you use most frequently.</li><li>It works on all major shells.</li><li>fzf is a command-line fuzzy finder, used by zoxide for interactive selection.</li><li>Instead of typing the full command, instead, you can use the alias z.</li></ul><p><em>Project Source: </em><a href="https://github.com/ajeetdsouza/zoxide"><em>https://github.com/ajeetdsouza/zoxide</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HH6gl6kxdHcHVKym5GaP4A.gif" /></figure><p>6. ripgrep - Is a replacement for grep<strong> </strong>command. It is a file pattern searcher written in Rust.</p><p><strong>Features:</strong></p><ul><li>By default, ripgrep will respect .gitignore rules and automatically skip hidden files/directories and binary files.</li><li>It has first-class support on Windows, macOS, and Linux, with binary downloads available.</li><li>It supports arbitrary input preprocessing filters which could be PDF text extraction.</li><li>It can search specific types of files.</li></ul><p><em>Project Source: </em><a href="https://github.com/BurntSushi/ripgrep"><em>https://github.com/BurntSushi/ripgrep</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A1F9u5CWJxUAbB9FHGzmsA.gif" /></figure><p>7. dust - A more intuitive version of du command which is used to display disk usage statistics. It is written in Rust.</p><p><strong>Features:</strong></p><ul><li>Gives you an instant overview of which directories are using disk space.</li><li>Dust will print a maximum of one ‘Did not have permissions message’.</li><li>The largest subdirectories will be colored.</li><li>Dust will list a slightly-less-than-the-terminal-height number of the biggest subdirectories or files and will smartly recurse down the tree to find the larger ones.</li></ul><p><em>Project Source: </em><a href="https://github.com/bootandy/dust"><em>https://github.com/bootandy/dust</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1BmEXt8O4uhVlqLeTkX1vQ.gif" /></figure><p>8. duf - It is a replacement for <strong>df </strong>command which displays free disk space. It is written in Go.</p><p><strong>Features:</strong></p><ul><li>It is user-friendly with colorful output.</li><li>It can adjust to your terminal’s theme &amp; width.</li><li>Sort the results according to your needs.</li><li>Groups &amp; filters devices.</li><li>Can conveniently output JSON.</li></ul><p><em>Project Source: </em><a href="https://github.com/muesli/duf"><em>https://github.com/muesli/duf</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hkd6A2_hto5pe1oDHBfmUQ.gif" /></figure><p>There are other alternative tools as well but, these are my favorite replacements. Check these projects on GitHub for more detailed explanations, installation, configurations, usage, and more. If you like these kinds of stuff, check out my other posts, tutorials, and tips. If you want to stay updated, then <a href="https://narasimmantech.com/#/portal/signup">subscribe to my Newsletter</a>.</p><p><strong>Checkout My Other Post on my Website:</strong></p><p><a href="https://narasimmantech.com/awesome-modern-unix-command-line-tools">10 Awesome Modern Unix Command-Line Tools</a></p><p><strong>Subscribe to My Weekly Newsletter on my Website:</strong></p><p><a href="https://narasimmantech.com/#/portal/signup">Narasimman Tech</a></p><p><strong>Join the conversation in my Community to talk about Tech:</strong></p><p><a href="https://community.narasimmantech.com/">Narasimman Tech Community</a></p><p><strong>Follow me on </strong><a href="https://twitter.com/narasimman_tech"><strong>Twitter</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0a295ba708d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narasimman-tech/try-these-8-modern-alternatives-to-common-unix-commands-e0a295ba708d">Try These 8 Modern Alternatives to Common Unix Commands</a> was originally published in <a href="https://medium.com/narasimman-tech">Narasimman Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[12 Useful Git Commands for Beginners]]></title>
            <link>https://medium.com/narasimman-tech/12-useful-git-commands-for-beginners-7edce8d62a55?source=rss----c19b12d3492d---4</link>
            <guid isPermaLink="false">https://medium.com/p/7edce8d62a55</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Lakshmi Narasimman V]]></dc:creator>
            <pubDate>Sat, 14 May 2022 05:35:15 GMT</pubDate>
            <atom:updated>2022-05-21T07:25:34.583Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QpKOmsdEIjhsSh_vee9T0A.png" /></figure><p><strong>Introduction:</strong></p><p>Git is a powerful version control system used for tracking changes in a file or directory during any software development process.</p><p>The following commands will help you to use git in your next software development project:</p><ol><li><strong>git init </strong>— to initialize a new git repository.</li><li><strong>git add . — </strong>adds all the files and folders in the current to the staging area to start tracking changes.</li><li><strong>git commit -m ‘a short message’ — </strong>creates a snapshot in the .git directory and starts tracking.</li><li><strong>git status — </strong>to check the status of your files.</li><li><strong>git rm &lt;file name&gt; — </strong>to remove a file from being tracked.</li><li><strong>git clone &lt;remote repository url&gt; — </strong>downloads a copy of the remote repository.</li><li><strong>git remote add origin &lt;remote repository url&gt; — </strong>you add a remote repository to your local repo and push changes to the remote repo.</li><li><strong>git checkout -b &lt;new branch name&gt; — </strong>creates a new branch and switches to the new branch.</li><li><strong>git switch &lt;branch name&gt; — </strong>to switch into a different existing branch.</li><li><strong>git merge &lt;branch to merge&gt; — </strong>to merge changes from a different into the current branch.</li><li><strong>git pull — </strong>update the local version of a repository from a remote.</li><li><strong>git push origin &lt;branch name&gt; — </strong>to push local changes to the remote git repository.</li></ol><p><strong>Additional commands:</strong></p><p><strong>13. git log — </strong>to review and read a history of everything that happens to a repository.</p><p><strong>14. git help &lt;verb&gt; </strong>— to get the comprehensive manual page help for any of the Git commands.</p><p><strong>Check out my Website and Subscribe to My Weekly Newsletter:</strong></p><p><a href="https://narasimmantech.com/">Narasimman Tech</a></p><p><strong>Join My Tech Community:</strong></p><p><a href="https://community.narasimmantech.com/">Narasimman Tech Community</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7edce8d62a55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narasimman-tech/12-useful-git-commands-for-beginners-7edce8d62a55">12 Useful Git Commands for Beginners</a> was originally published in <a href="https://medium.com/narasimman-tech">Narasimman Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 8 DevOps tools for a Beginner DevOps Engineer]]></title>
            <link>https://medium.com/narasimman-tech/top-8-devops-tools-for-a-beginner-devops-engineer-1a6f3e7a0aa8?source=rss----c19b12d3492d---4</link>
            <guid isPermaLink="false">https://medium.com/p/1a6f3e7a0aa8</guid>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Lakshmi Narasimman V]]></dc:creator>
            <pubDate>Sat, 14 May 2022 05:34:23 GMT</pubDate>
            <atom:updated>2022-05-12T10:56:00.341Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KqBlBA2VbJI9NpuYNtgmKg.jpeg" /></figure><p>Even though there are a lot of popular DevOps tools, here are a few to get started in the realm of DevOps:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*yX16nmUvWS5Q4fXDLpcGBA.png" /></figure><ol><li><strong>Git</strong> — Git is a free and open-source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. To get started with git, check out my other post on Git:</li></ol><p><a href="https://medium.com/@narasimman_tech/12-useful-git-commands-for-beginners-7edce8d62a55">12 Useful Git Commands for Beginners</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DBDq2-2hTdIb113ZIvMLNA.png" /></figure><p>2. <strong>Terraform</strong> — Terraform is an infrastructure as code (IaC) tool that allows you to build, change, and version infrastructure safely and efficiently. This includes both low-level components like compute instances, storage, and networking, as well as high-level components like DNS entries and SaaS features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/307/1*4XhkJA_YHIuZsKWwK73eZw.jpeg" /></figure><p>3. <strong>Ansible</strong> — let’s assume you have 100 servers to manage and you have to update the OS in all the servers. One way of approach is you can login into each server and run a script. the other option is you can use Ansible to do a job all at once. Ansible Automation Platform is a foundation for building and operating automation across an organization. The platform includes all the tools needed to implement enterprise-wide automation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/271/1*g4w9u8SDQPNjG3c1BHDv0A.jpeg" /></figure><p>4. <strong>Jenkins </strong>— Jenkins is a self-contained, open-source automation server that can be used to automate all sorts of tasks related to building, testing, and delivering or deploying software. There are other popular tools like Travis CI, Circle CI, GitHub Actions, etc., But Jenkins is still widely used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/354/1*XqYyLihbqShSBVOM2R1qRw.jpeg" /></figure><p>5. <strong>Linux </strong>— Linux is the world’s most popular open-source Operating System. Command-line navigation like changing current working directories, copying or moving files around, deleting files/directories, etc., is one of the basic essential Linux skills to know as a DevOps engineer or for any IT role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/491/1*TKqcLWCVw1ad2vM3Zp6bkg.jpeg" /></figure><p>6.<strong> Amazon Web Services </strong>— Amazon Web Services also known as AWS is the world’s most comprehensive and broadly adopted cloud platform for deploying applications. Knowing how to Create Virtual Machines (EC2) and Networking (VPC) is the most basic skill necessary to start deploying applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*9RxExvS441MEQqwwj0ejWA.jpeg" /></figure><p>7. <strong>Python </strong>— Even though a lot say knowledge of programming is not necessary for a DevOps Engineer, knowing one is so precious. Python and Go are the most popular programming languages to know as a DevOps Engineer. These languages help you to automate a lot of repetitive tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8zDNaWL8nTv9i6TMw0jgTA.png" /></figure><p>8. <strong>Docker </strong>— A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. Docker is a popular containerization platform and is a widely adopted software industry.</p><p>You don’t have to master everything at once, but understanding the basic concepts of each tool and knowing how to integrate them is important. It takes time to learn each tool and integrate it, so one of the best ways to get started is to build a small home lab using Raspberry Pi or old computer(s) and try running self-hosted applications and testing them. Here’s a list of open-source self-hosted services :</p><p><a href="https://github.com/awesome-selfhosted/awesome-selfhosted">GitHub - awesome-selfhosted/awesome-selfhosted: A list of Free Software network services and web applications which can be hosted on your own servers</a></p><p>There are other advanced tools used by DevOps Engineers like Kubernetes for container orchestration, Prometheus and Grafana for monitoring servers and application performance, Selenium for Testing apps, and much more. I will be covering everything individually, sharing tips, tutorials, guides, and much more…</p><p><strong>Check out my Website and Subscribe to My Weekly Newsletter:</strong></p><p><a href="https://narasimmantech.com/">Narasimman Tech</a></p><p><strong>Join My Tech Community:</strong></p><p><a href="https://community.narasimmantech.com/">Narasimman Tech Community</a></p><p><em>Additional Resources:</em></p><ol><li><a href="https://www.docker.com/blog/how-to-dockerize-your-python-applications/">How to “Dockerize” Your Python Applications</a></li><li><a href="https://www.youtube.com/watch?v=6u5NE1GiQDk">https://www.youtube.com/watch?v=6u5NE1GiQDk</a></li><li><a href="https://www.hashicorp.com/blog/products/terraform">https://www.hashicorp.com/blog/products/terraform</a></li><li><a href="https://www.jenkins.io/node/">https://www.jenkins.io/node/</a></li><li><a href="https://www.ansible.com/blog">https://www.ansible.com/blog</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a6f3e7a0aa8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narasimman-tech/top-8-devops-tools-for-a-beginner-devops-engineer-1a6f3e7a0aa8">Top 8 DevOps tools for a Beginner DevOps Engineer</a> was originally published in <a href="https://medium.com/narasimman-tech">Narasimman Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>