Problem solve Get help with specific problems with your technologies, process and projects.

Data integration tips

Larry Fulton discusses various ways to avoid data integration headaches when dealing with data representations.

I hear a lot of good things about Relax NG and JSON, but what sorts of data integration problems am I asking for if I use them? Do you have any simple tips for making sure I don't create needless data integration headaches if I use either one?

My answer has very little to do with either technology specifically. If you want to avoid data integration headaches, you have to be consistent, meaning that every developer has to do things in a similar way, rather than defining their own set of data representations. To do this requires a process that is:

A) very easy for developers to use


B) very quickly gives developers consistent representations

A simple example: if developer A and developer B both need to share information about user accounts, and one uses a variable length text field and one uses a fixed-length numeric field, you have created needless inconsistency, through the lack of a clearly defined process.

Taking this one step further, if your clearly defined process has future flexibility baked in, for example by making it possible for some future program to process today's N-digit account codes as well as tomorrow's N+M-digit account codes, you can carry that flexibility along into the specific implementation.

Also, bear in mind that JSON is implemented as JavaScript, and is therefore subject to all of the strengths and vulnerabilities, particularly from a security standpoint, as other uses of JavaScript.

Dig Deeper on Topics Archive

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.