Azure Access Tiers in Azure storage

There are various types and nature of data we store in Azure storage. All kinds of blob data have different accessibility requirements. Sometimes data accessibility reduces over time, whereas accessibility remains the same for some blob data types. There is no point in paying the same price for data that is rarely being accessed or not accessed at all. Azure provides Access Tiers property to address such scenarios and optimize the cost on blobs with less accessibility.

Continue reading Azure Access Tiers in Azure storage

Environment Strategy


Businesses should believe that every team is in the business of creating great customer experiences.

To achieve that, the application must do more than just provide control, reporting and audibility. The business needs to tap into data signals from across its business and use them to drive ongoing improvements in the products, services, and experiences they intend to deliver to its customers.

Continue reading Environment Strategy

End of the Road For Azure DevOps?

With Microsoft now owning GitHub, the technical teams have been integrated, resulting in Azure DevOps and GitHub having the same leadership and personnel. The long-term strategic direction will be GitHub, but there is no plan for Azure DevOps to go into maintenance/sunset; therefore, choosing Azure DevOps is entirely OK in short to (undefined) medium term. Azure DevOps is currently in the early stages of development. When migration tools are needed, Microsoft will give them.

Continue reading End of the Road For Azure DevOps?

Deployment Strategies

There are a variety of techniques to deploy new updates for environments to production, so choosing the right strategy is an important decision, weighing the options in terms of the impact of change on the system and the end-users.
The following strategies need to be considered:

  • Recreate: Version A is terminated then version B is rolled out.
  • Ramped (also known as rolling-update or incremental): Version B is slowly rolled out and replacing version A.
  • Blue/Green: Version B is released alongside version A, then the traffic is switched to version B.
  • Canary: Version B is released to a subset of users, then proceed to a full rollout.
  • A/B testing: Version B is released to a subset of users under specific condition.
  • Shadow: Version B receives real-world traffic alongside version A and doesn’t impact the response.
Continue reading Deployment Strategies

GitHub Naming Repositories

As part of our customer engagement, we have defined a naming convention for GitHub repositories. 

We have ideas around what conventions made sense, although the type of work influences these. As we tend to spend some of your engineering time working with different languages, conventions around naming formats make sense to the engineers. These, of course, might not make sense to individuals in other fields. 

Continue reading GitHub Naming Repositories


GISTS – engage in chat or gossip. 
“I need a good friend I can always gist with.” 

It is always good to chat with others, which is how we learn from each other. So why don’t project teams chat with each other? In this day and age of working from home, it is becoming more and more critical to form a social network, which helps not only with mental health but also work-related ideas and time. 

Continue reading gists

this and that