This is part of a blog about some of the components on the Microsoft Azure platform such as Azure YAML, Azure Xcloud, Azure Webjobs, Azure Virtual Desktop, Azure app service, Azure storage, databases, databricks, Event Hubs, Functions, Gateways, Networking, IoT, Linux, containers, Azure Kubernetes Service, compute, security, Azure Resource Manager, Azure Templates, Azure Users and many more. I am using all the letters of alphabet to do this. This is twenty five of twenty-six.
Y for YAML
What is YAML?
YAML stands for “Yaml Ain’t Markup Language”. Back in 2001 when it was first launched, they called it “Yet Another Markup Language”. The reason for the change was to highlight that the language was to be designed and used with data and not used for documents. YAML is a data serialization language that humans can easily read and it is similar to XML and JSON formats. YAML is frequently used for configuration files and with applications where data is transmitted or stored. YAML can also be used alongside most programming languages, for example sending messages between applications. Here are some examples of configuration files written in YAML; Docker, Kubernetes, Ansible, Prometheus and other devops tools. Examples of the code are shown below and you can see the difference in the YAML format and how it compares to XML and JSON.