Managing GitHub Organizations with GitHub GraphQL API
Feb 18, 2021 · 6 min read
I prefer using GraphQL over REST APIs wherever available, primarily because I can avoid overfetching and underfetching data while still enjoying the benefits of contract-based development. For this exercise, assume that you are the DevOps lead of an organization/open-source community that uses GitHub to manage its projects under a GitHub Organization. GitHub Organizations are shared accounts consisting of members and projects with sophisticated security and administrative features. You have been asked to ensure that your organization’s repositories are healthy such that there are no PRs in an unmerged state for more than one week, and every issue is either resolved or updated in 12 hours.
Read more of Managing GitHub Organizations with GitHub GraphQL API
Scheduling Jobs on Heroku with Azure Logic Apps
Feb 05, 2021 · 12 min read
Many times, your application needs to run tasks or jobs on regular intervals. Scheduling might be necessary when polling an API every night, or dispatching emails with reports each week. And sometimes you may find that you need to trigger a host of tasks across multi- or hybrid-cloud and need a way to run these tasks in a reliable, cross-cloud manner. In this article, let’s look at one way to do that using a Heroku dyno for our task, and Microsoft Azure Logic Apps as our scheduler service.
Read more of Scheduling Jobs on Heroku with Azure Logic Apps
Tracing and Profiling a .NET Core Application on Azure Kubernetes Service with a Sidecar Container
Feb 03, 2021 · 11 min read
Imagine running a .NET Core application in Kubernetes, which suddenly starts being sluggish, and the telemetry fails to give you a complete picture of the issue. To remediate performance issues of applications, starting with .NET Core 3, Microsoft introduced several .NET Core runtime diagnostics tools to diagnose application issues. dotnet-counters to view Performance Counters. dotnet-dump to capture and analyze Dumps. dotnet-trace to capture runtime events and sample CPU stacks. dotnet-gcdump to collect Garbage Collector dumps of application.
Background Jobs in Heroku with Azure Service Bus
Jan 14, 2021 · 11 min read
Web applications are optimized for throughput and latency to service a high number of HTTP requests as quickly as possible. For improved performance, web applications defer the CPU intensive, IO intensive, time-intensive, and scheduled processing workloads to background jobs that run independently of the user interface. These background jobs must function without intervention from the user interface and should not block a synchronous user and system interaction. Offloading slow and compute or memory-intensive activity to background jobs improves web applications' performance and throughput.
Read more of Background Jobs in Heroku with Azure Service Bus
Implementing Multi Session Sequential Convoy Pattern with Azure Service Bus and Go
Jan 02, 2021 · 10 min read
In many event-driven applications, preserving the sequence of events is essential. For example, an event-driven eCommerce application might have the following states, transitions, and events. A user adds N items to the basket. This action generates the item added event. The user checks out the basket. This action generates the basket checked out event. The user pays for the items. This action generates the payment made event. Inventory decrements the count of available items by N.
#azure #integration #programming
Read more of Implementing Multi Session Sequential Convoy Pattern with Azure Service Bus and Go
Simplifying ARM Template Deployments with Ansible
Dec 10, 2020 · 6 min read
I discussed how you could use Ansible with Terraform to simplify configuration management in my previous post. If, instead of Terraform, you prefer using Azure Resource Manager (ARM) templates to define the infrastructure and configuration for your project, you can use Ansible for managing parameters that customize each environment by dynamically generating a Resource Manager parameters file. A great thing about using Ansible for your ARM configuration needs is that it includes a suite of modules for interacting with Azure Resource Manager.
Read more of Simplifying ARM Template Deployments with Ansible
Serverless Visitor Counter Badge with Azure Functions
Nov 22, 2020 · 7 min read
We all love web badges. You might have spotted many of them in README of repositories, including the repository of my blog, The Cloud Blog. In general, web badges serve two purposes. They are visually appealing. They display key information instantly. If you scroll to my website’s footer section, you will find GitHub and Netlify badges that display the status of the latest build and deployment. I use them to quickly check whether everything is fine with the world without navigating to their dashboards.
Read more of Serverless Visitor Counter Badge with Azure Functions
Simplifying Terraform Deployments with Ansible - Part 2
Nov 13, 2020 · 10 min read
In this series Motivation & Ansible 101 Terraform & Ansible I am happy to see that many people are enthusiastic about this series and wish to make their IaC applications better with Ansible. What I intend to do is very simple. I will write an Ansible playbook that uses the template module (see Templating with Jinja2) and a little magic of Jinja2 templates to load appropriate variables and configurations for each Terraform environment.
Read more of Simplifying Terraform Deployments with Ansible - Part 2
Simplifying Terraform Deployments with Ansible - Part 1
Nov 03, 2020 · 5 min read
In this series Motivation & Ansible 101 Terraform & Ansible Enterprise developers are responsible for deploying infrastructure to multiple environments, such as development, staging, and production. One core problem with configurations in Terraform is that with the number of environments and variables, the number of “.tfvars” files used to manage configurations will increase. Several tools, such as Puppet, Chef, and Ansible, help simplify the management of configurations.
Read more of Simplifying Terraform Deployments with Ansible - Part 1
Monitoring Health of ASP.NET Core Background Services with TCP Probes on Kubernetes
Oct 24, 2020 · 9 min read
Many microservices applications require background tasks and scheduled jobs to process requests asynchronously. In the .NET Core ecosystem, background services are called Hosted services because a single host, such as a web host or a console host, can run several such services in the background while it is alive. In terms of implementation, a hosted service is required to implement the IHostedService interface. You can implement the IHostedService interface yourself, or even better, leverage the BackgroundService class that implements some common concerns such as cancellation token management and error propagation to the host for you.
Read more of Monitoring Health of ASP.NET Core Background Services with TCP Probes on Kubernetes