JSON and YAML: When to Use Which
Compares the differences between JSON and YAML and the situations each one suits.
JSON and YAML deal with essentially the same data model (objects, arrays, and values). YAML is a superset of JSON, so every JSON document is also valid YAML. The difference lies in notation and purpose.
JSON has simple rules and is easy for machines to parse, making it strong for programs exchanging data with one another, as in API communication. YAML, on the other hand, is suited to configuration files that people read and edit, thanks to its indentation and comments.
In short, JSON is the safe choice for data consumed by programs, and YAML for configuration that people frequently edit. The two can be converted to each other at any time, so you can move between them as the situation calls for.