Terraform CI-CD With Azure DevOps

Let’s consider a scenario in which you are deploying your infrastructure using a Terraform code (infrastructure-as-code) which is stored in a remote git repository. Now working in an organization you need to make sure that all your deployments are always tracked without an exception, an add-on to that whether your Terraform code is following your security and compliance policies or not. Or maybe what is the monthly cost that you can expect with that infra and whether it lies under your budget or not. You may also want to take note that all your resources are being created in the same region… etc… etc.

Sounds magical right !!! We all know that these concerns are very important when you’re looking for a highly consistent, fully tracked, and automated approach. That’s why in this article we are going to look for a simple step-by-step way to automate and streamline our Terraform code using Azure DevOps (ADO).

Soo… Let’s Get Started !!!

Continue reading “Terraform CI-CD With Azure DevOps”

What Is the Difference Between CloudOps And DevOps?

Most business managers get confused between CloudOps and DevOps easily. And it is a way too common problem so here we are drawing a line between CloudOps and DevOps that can help the business managers understand the basic difference between CloudOps and DevOps.

As the name proposes, DevOps is a mix of ”Development” and ”Operations”, and depicting it as “specialized deft” appears to be shockingly exact. A bunch of practices and processes assist associations with making a spry, cooperative climate that unites software development, IT tasks, and quality designing to fulfill the basic business operations such as:

Continue reading “What Is the Difference Between CloudOps And DevOps?”

What is a Bare Git Repository?

A Git bare repository is a specialized version of a Git repository that serves a different purpose than a regular Git repository. Many platforms, such as GitHub, rely on bare repositories stored on their servers. When you clone a repository from GitHub, you’re actually accessing one of these bare repositories. They’re designed for server-side use, helping to securely and efficiently manage and distribute code, without the ability to directly modify files like a normal repository. Here’s a simple explanation:

  • Lack of a working directory: Unlike standard Git repositories, bare repositories don’t have a working directory. This means you can’t view or edit files directly. You also won’t be able to run Git commands that typically require a working directory.
  • Only contains Git data: A bare repository only contains the .git folder data you’d find in a normal repository. This includes version history, configuration, branches, etc., but it doesn’t include the actual project files that you can edit.
  • Used for Sharing: Bare repositories are typically found on servers where multiple developers share code. Instead of working directly in the bare repository, developers clone it to their local computers, make changes, and then push those changes back to the bare repository. Services like GitHub use a similar process.
  • Prevents direct editing: By not having a working directory, there’s no risk of users directly editing files on the server. This helps avoid conflicts and maintain version control.
  • Simplifies management: If you’re managing a server-side repository and only need to monitor history and branches, a bare repository is a more efficient and secure option.

By understanding these details, you can appreciate the role of bare repositories in a collaborative coding environment.

Continue reading “What is a Bare Git Repository?”

AWS Gateway LoadBalancer: A Load Balancer that we deserve

Nowadays, LoadBalancing is one of the basic needs for the application systems to perform optimally while considering some important factors like- scalability and high availability. Every cloud is providing LBaaS (LoadBalancing as a Service) as an offering so the consumers don’t have to worry about the setup and management of load-balancers by themselves.

But it’s not like that cloud is offering a single type of load balancer for every use case because for different use-case we require a different type of load balancer. For example- we have different load-balancers for Layer4 and Layer7 level traffic.

Recently AWS had a new family member in their load-balancer family and they named it “Gateway Load Balancer“. So gateway load-balancer is a load-balancing service provided by AWS to send traffic to the different appliances, applications, firewalls, etc. that are not part of the current VPC.

Continue reading “AWS Gateway LoadBalancer: A Load Balancer that we deserve”

Learn everything about Amazon Cloudfront

Before going to Cloudfront functionality, we need to understand the CDN (Content delivery network) first, as Cloudfront is nothing but just a FAAS  (functions as a service) platform provided by AWS, which we generally relate to the content delivery network(Cloudfront) in AWS cloud service provider.

CDN(Content Delivery Network)

A CDN is kind of a geographically distributed group of servers that are attached so that they can communicate with each other and provide fast delivery of any content such as HTML pages, images, videos, etc. The popularity of CDN services is continuously growing among organizations such as Netflix, Facebook, and Amazon as their major web traffic is served through CDN.

Now, let’s take a deep understanding of how CDN works in the AWS Cloudfront service.

We could think of a CDN as an ATM. Having a cash machine on practically every corner makes it fast, immediate access, and efficient to get money. There’s no wait time in long bank lines to get our money in hand.

In today’s time, a large portion of all internet content is delivered through CDNs. Here is a simple example:

Continue reading “Learn everything about Amazon Cloudfront”