OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Potential Risks of Migration from XML to JSON

If I were consulting to this project, I think the first questions I would ask are:

* How many producers and consumers are there for this data feed, and are they all under your control?

* Is the data completely transient or do you have persistent data that needs to be migrated?

* Is the data format well documented and understood? How complex is it?

* How good is your test suite? If you break anything, how will you know (and what are the consequences if you don't)?

* What are you hoping to achieve by the change in technology? If there are problems that need to be fixed, is a change in technology going to help fix them, or is it just going to distract from the real issues?

Michael Kay

On 14 Oct 2016, at 09:44, Evan J <maps.this.address@gmail.com> wrote:

I wanted to know about the possible risks that one might encounter while deciding to migrate the messaging format from XML to JSON in a data exchange environment.

What criteria one must take into account before making a decision to pursue such overhaul?

Factors such as: complexity of data structures, validation requirements, security, etc. How would a system architect go about such analysis?

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS