The real advantage of XML is when you can integrate the whole
toolchain into your processing: schema validators, XPath, XSLT, etc.
If you just want to pass a few name value pairs and lists back and
forth, sure, use JSON. But as the documents become complex and you
need to query and transform them, XML is a lot faster and more
relaible to develop for.
On Tue, Aug 1, 2017 at 7:34 AM, Mukul Gandhi <> wrote:
> Hello,
> I don't intend to spark a bitter debate between XML & JSON, where the
> outcome of debate is win of one over other. Rather, I wish to present in a
> friendly manner, according to me, where these two technologies differ.
>
> When talking about designing REST services, JSON seems to clearly win. The
> whole software world seems to be biased in favour of JSON it seems, for this
> criteria. Although I have read, that in many cases REST services can use XML
> instead of JSON. I think, JSON's major use case is in the use within REST.
>
> Having worked quite a bit with Android mobile apps, that framework by
> default relies heavily on XML. I haven't seen JSON being used by default in
> that area. Although, JSON is many times used in feeding and fetching JSON
> data from various kinds of services (remote REST services, local API calls
> etc), in Android apps.
>
> XML when considering other technologies in combination, like XML Schema and
> XML databases, have a scale close to RDBMSs. JSON is no where near this.
>
> Any other thoughts from the experts here?
>
>
>
> --
> Regards,
> Mukul Gandhi
--
Elliotte Rusty Harold
