Greetings to my fellow Technology Advocates and Specialists.
In this Session, I will explain and walk my readers through a debatable topic - Choose Right Tooling for Cloud.
| DISCLAIMER:- |
|---|
| The contents of this article is strictly my way of looking into the subject. However, I am convinced that there are other fascinating opinions to look into this debatable topic. |
| CODE REPOSITORY:- | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Choose Right Tooling for Cloud ?Greetings to my fellow Technology Advocates and Specialists. In this Session, I will explain and walk my readers through a debatable topic - Choose Right Tooling for Cloud.
In every organisation, when you start with cloud, you land up having Hybrid Infrastructure: Part On-Prem, Part Cloud. For the purpose of this session, please consider below -
If we think, which tooling to go for in cloud, it would be a wrong approach. It would also be wrong to compare between Cloud Automation Tooling and On-Prem Automation… |
In every organisation, when you start with cloud, you land up having Hybrid Infrastructure: Part On-Prem, Part Cloud.
For the purpose of this session, please consider below -
| # | KEY | VALUE |
|---|---|---|
| 1. | Cloud | Azure |
| 2. | Cloud Automation Tooling | Azure Devops, Github Actions, Terraform, Biceps, Powershell, AzCLI |
| 3. | On-Prem Automation Tooling | Powershell, Shell Scripting, ... |
If we think, which tooling to go for in cloud, it would be a wrong approach.
It would also be wrong to compare between Cloud Automation Tooling and On-Prem Automation Tooling as usecase, purpose and functionality possible could vary.
| Cloud Automation Tooling can be bifurcated like below:- |
|---|
| # | CATEGORY | TOOLING | NOTES |
|---|---|---|---|
| 1. | Infrastructure | a.) Azure Devops, b.) Github Actions, c.) Terraform, d.) Biceps, e.) Powershell, f.) AzCLI | IaaS and PaaS |
| 2. | Database | a.) Sql DACPAC, b.) Sqlcmd, c.) Azure Pipelines task for Azure Database for PostgreSQL Flexible Server, d.) GitHub Actions to connect to Azure PostgreSQL, e.) Azure Pipelines for Azure Database for MySQL - Single Server, f.) GitHub Actions to connect to Azure MySQL | - |
| 3. | Application | Deploying C#, F#, ASP.NET, React, Python, R, ... on Azure Services. | - |
| 4. | Containers | a.) Build and deploy to Azure Kubernetes Service with Azure Pipelines, b.) Build, test, and deploy containers to Azure Kubernetes Service (AKS) using GitHub Actions, c.) Deploy to Azure Container Apps from Azure Pipelines, d.) Deploy to Azure Container Apps with GitHub Actions, e.) GitHub Actions with Azure CLI in Azure Container Apps. | - |
| 5. | Data Orchestration | a.) Azure Data Factory, b.) Azure Synapse, c.) Python Code running in AKS performing ETL, ... | - |
| 6. | API | Publish APIs using devops. | - |
| 7. | Security | a.) DevSecOps (Security in DevOps), b.) DevSecOps with Github | - |
| On-Prem Automation Tooling can be bifurcated like below:- |
|---|
| # | CATEGORY | TOOLING | NOTES |
|---|---|---|---|
| 1. | Infrastructure | Powershell, Shell Scripting... | IaaS - VM Based Infrastructure |
| 2. | Application | Deploying C#, F#, ASP.NET, React, Python, R, ... on VM Based Infrastructure. | - |
In my opinion, Approach should be below:-
| # | PROJECT TYPE | TOOLING |
|---|---|---|
| 1. | Green Field Project in Azure | Cloud Automation Tooling |
| 2. | Brown Field Project (Re-Factor and Re-Platform) | Cloud Automation Tooling |
| 3. | Brown Field Project (Any Application which cannot be refactored and Operations heavily dependent on On-Prem Automation) | On-Prem Automation Tooling |
| NOTE:- |
|---|
| If later down the year, there is a possibility to refactor the application in a way where Infrastructure can be moved to PaaS, On-Prem Automation Tooling can then be replaced with Cloud Automation Tooling. |
In this way, On-Prem Automation and Cloud Automation Tooling can co-Exists in Azure Cloud.
Hope You Enjoyed the Session !!!
Stay Safe | Keep Learning | Spread Knowledge
Top comments (0)