Anatomy of formats: A closer look

Let's start with a simple example to see how both formats store the same information. Imagine we want to save data about a single product from an e-commerce store.

In XML, it could look like this:

In JSON, however, the same set of data would look like this:

Right from the start, you can see that JSON is more concise, while XML, thanks to its use of tags, offers a more extensive structure. This difference in approach translates into their distinct applications in the world of developers.

1. Lightweight and fast: As you can see from the example, JSON code is much more concise. This means a smaller size for the data being transferred, and consequently, a faster transfer between the server and the client. This is crucial in mobile applications, where every kilobyte and half-second counts.

2. Human readability: JSON's concise structure, based on readable key-value pairs and square and curly brackets, is intuitive. Developers can quickly understand the data without having to look at the documentation.

3. Simpler parsing: JSON is based on JavaScript syntax, which makes its processing in that language exceptionally simple and natural. As a result, the process of parsing and generating data is efficient and doesn't require complicated libraries, which significantly speeds up the work of developers regardless of the technology used.

These advantages have made JSON the de facto standard for REST APIs, and it is widely used in modern web and mobile applications.

Despite JSON's dominance, XML has certainly not been forgotten. It may seem that it has lost a lot of popularity, but there's no shortage of applications and use cases where XML still enjoys unwavering trust. It has its niches where its "verboseness" is actually an advantage.

1. Strict data validation: XML was designed for validation from the very beginning. Thanks to schemas (like XSD), you can precisely define what data can be in the file, what type it is, and in what order. This is extremely important in industries where even the smallest error can have serious consequences, for example, in banking, medicine, or aviation.

2. Older systems and protocols: Many older but still-functioning business systems (e.g., based on the SOAP protocol) still communicate using XML. Its stability and reliability have meant there is no reason to change them.

3. Markup languages: XML is a highly universal markup language, which makes it flexible in creating custom formats.

Despite JSON's dominance, XML has certainly not been forgotten. It may seem that it has lost a lot of popularity, but there's no shortage of applications and use cases where XML still enjoys unwavering trust. It has its niches where its "verboseness" is actually an advantage.

1. Strict data validation: XML was designed for validation from the very beginning. Thanks to schemas (like XSD), you can precisely define what data can be in the file, what type it is, and in what order. This is extremely important in industries where even the smallest error can have serious consequences, for example, in banking, medicine, or aviation.

2. Older systems and protocols: Many older but still-functioning business systems (e.g., based on the SOAP protocol) still communicate using XML. Its stability and reliability have meant there is no reason to change them.

3. Markup languages: XML is a highly universal markup language, which makes it flexible in creating custom formats.

Despite JSON's dominance, XML has certainly not been forgotten. It may seem that it has lost a lot of popularity, but there's no shortage of applications and use cases where XML still enjoys unwavering trust. It has its niches where its "verboseness" is actually an advantage.

1. Strict data validation: XML was designed for validation from the very beginning. Thanks to schemas (like XSD), you can precisely define what data can be in the file, what type it is, and in what order. This is extremely important in industries where even the smallest error can have serious consequences, for example, in banking, medicine, or aviation.

2. Older systems and protocols: Many older but still-functioning business systems (e.g., based on the SOAP protocol) still communicate using XML. Its stability and reliability have meant there is no reason to change them.

3. Markup languages: XML is a highly universal markup language, which makes it flexible in creating custom formats.