Azure Devops Pipelines Basics

In this article we will see what are the different components of Azure Devops Pipelines.

These components are there basic foundation of Azure Devops Pipelines, understanding these plays a key role while working on Azure Devops.

Trigger : As the name suggests it will start the Pipeline execution. Trigger can start a pipeline as per schedule or if any activity happens. In short, when the pipeline should run is defined in a trigger.

Stages : It is the logical separation between different environments like we can a stage for Dev environment, one for QA and so on. A pipeline can have single or multiple stages. By default the stages will run one after another, we can also specify conditions when a stage to run.

Job : A job is collection of single or multiple steps. It is the smallest unit in a pipeline which can be scheduled. Each Stage in a Azure Pipeline will have single or multiple Jobs. Every pipeline will have at least one job.

Job Agent : To build or deploy code we need at least one job agent. Job agent acts as a compute infrastructure for the jobs to run. Note: Few jobs can run without agent also.

Step : Step is the smallest building block of a Azure Pipeline. Each job step will have details of the actual action that needs to be done. Each job will have single or multiple Steps.

Task : A task can be a script or procedure to perform certain action. Action can be building an application, deploy IoT image, push docket images and so on. There are many built-In tasks and custom tasks can be created as well.

#AzureDevOps #AzurePipelines

Azure Devops Common mistakes - 1

One of the most common mistakes people commit in Azure Devops is not having identical Development, Test and Production environments.

The better way to address this is to use infrastructure as code (IaC) tools like Azure Resource Manager (ARM) templates or Bicep to define your infrastructure in a consistent and repeatable way.

This will ensure that all environments are identical, regardless of who created them.

#azuredevops #azurearchitect

Cost of CosmosDB.

Request Units of CosmosDB is like fuel of your car. When you drive your car, it consumes fuel. Similarly, when you use CosmosDB the resources it consumes are measured in Request Units (RUs). You may drive your car on plain road, off-road or anywhere your car consumption is measured in fuel. Similarly, you may perform different actions on CosmosDB it could be a Read query or Write Query the amount of resources consumed is measured in RUs.

Each database operation will have a response header which tracks the number of RUs consumed by the database operation. The cost of your CosmosDB depends on the number of RUs being consumed by it.

#azure #azuresql #azurecosmosdb