Tips & Best Practices in Application Development.

Short Forms – Abbreviations in any domain or industry is very common. As the industry is technology and it is popular there are weird abbrevations like SaaS (Software as a Service), PaaS (Platform as a Service), IaaS (Infrastructure as a Service) which all deal with cloud technology as these are services offered on pay as you use basis. You can read more of these here which gives some details on the abbreviations and their meaning.

How about i18n? What is that? It is an abbreviation for internationalization where between the first letter and the last there are 18 letters.

How about n8n? That is for nodemation which is combination of the node JavaScript framework and the word automation. It is a workflow automation tool which automates tasks and moves data between different application using a node-base interface. Here are some others which you come across:

n8n – nodemation

i18n —> internationalization

l10n – > localization

c14n —> canonicalization, which is a lot of syllables and an XML specification

a11y —> accessibility, but looks like the word ally

k8s —> Kubernetes, the distributed application framework used for cloud orchestration

***********************July 8th 2025************************

Dev/Prod Parity – 10th Factor of Cloud Native Application states that to keep the application deployed in development environment and production environment, differ minimally. Basically, it says that your code is extremely close to what is deployed in production. From a developer perspective, check in often to version control system and deploy often. This is the 10th factor in the 12 factors we discussed last week.

This can be accomplished by implementing CI/CD – Continuous Integration & Continuous Deployment. Details on CI/CD can be found here. The dev/prod parity can be accomplished by utilizing a deployment strategy which works for your team and company. Here are some deployment strategies:

1. Blue/Green Deployment
2. Canary Deployment
3. Feature Flag Deployment
4. Rolling Deployment
5. Shadow Deployment
6. Hybrid Deployment

A robust cloud native application, which utilizes the 12 factors & others, will not only leverage the features of the cloud but also be resilient to issues in production.

Dev/Prod Parity should be minimal as stated in factor 10 can be accomplished with implementing a deployment strategy.

****************************June 10th 2025*****************************

Factors for Cloud Native Applications initially started with 12 factors as shown below:

However, over time while implementating these twelve factors developers and architects increased the number to 15, 16 and in some cases even 21. However, it is widely accepted that these 12 factors along with API First, Authentication & Authorization and Circuit Breaker form the core of the Factors of Cloud Native Application. On this blog, I expound on these factors and suggest implementation tools which can be found here.

****************************June 3rd 2025*****************************.

Continuous Integration & Continuous Deployment (CI/CD) in Cloud computing. CI/CD is also sometimes referred to as Continuous Integration and Continuous Delivery which means we create the application to be deployed to the environment and it is then manually deployed.