JSON to YAML

JSON uses curly braces and brackets with strict syntax, while YAML uses indentation-based formatting that is more human-readable. JSON requires quotes around keys and string values, while YAML usually does not. JSON supports fewer data types natively, but is more widely supported by programming languages and APIs.

YAML uses indentation (spaces, not tabs) to denote structure. Key-value pairs are written as "key: value". Lists use a dash followed by a space ("- item"). Nested objects are indented under their parent key. Strings generally do not need quotes unless they contain special characters.

YAML is preferred for configuration files (Docker Compose, Kubernetes, CI/CD pipelines) because it is easier to read and write by hand. JSON is better for data exchange between services and APIs because it is faster to parse and has stricter syntax that reduces ambiguity.

YAML requires consistent indentation using spaces (tabs are not allowed). The number of spaces per level is flexible but must be consistent throughout the document. Two spaces per level is the most common convention. Incorrect indentation will cause parsing errors.

Docker Compose uses YAML files (docker-compose.yml) to define multi-container applications with services, networks, and volumes. Kubernetes uses YAML manifests to define resources like deployments, services, and config maps. Both rely on YAML for its readability when managing complex infrastructure configurations.