JSON and XML are two human-readable text formats that have emerged as rivals over the years. XML’s purpose is storing and defining documents and data through the optional use of a schema. JSON was almost the exact opposite – a serialization format with requirements so simple they fit on the back of a credit card. But, when should you use one or the other? We have to take into account that XML and JSON have similarities and differences that can affect your application’s performance. In this article, we will outline what’s going on, and what you need to know about JSON and XML.
[Tweet “Do you know how JSON and XML compare? Read on in this post by @evan_glazer via @codeship”]
Comparing JSON and XML
- Both are human readable.
- Both are hierarchal with a values within values format.
- Both can be parsed and used by a number of languages.
- Quicker to parse
- Uses arrays
- Data interchange format
- Needs an XML parser.
- Longer to parse.
- Doesn’t use Arrays!!
Which should I consider?
Everyone has their own opinion about JSON and XML. As a developer, I more or less stick to JSON in my projects unless an API requires XML parsing.
XML is still being used actively in web publishing to create interactive pages. It’s also used for searching the web, metadata and pervasive computing, which is another way to say wireless devices, like cell phones.
Depending on the type of application, it will vary based on what best fits your application to access information.
What’s going on
As applications and platforms evolved, efficiency and performance have been the status quo in priority. APIs evolved over the years to become leaner, and JSON has overtaken XML as the preferred format among developers and technology stacks.
- Learn how to work with the Jenkins JSON API
- Listen in on the latest trends in open source and DevOps
[Tweet “What’s better? JSON or XML? Learn the differences by @evan_glazer via @codeship”]