By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
It is straightforward to take an EDI message data model and produce an XML equivalent. XML makes a variety of things easier than EDI (such as nesting and repetition). On a case by case basis, you might decide to use a more "natural" XML model for you EDI data but, even then, it is a simple enough proposition to convert from these to/from native EDI messages.
Consequently, you can look at mixing'n'matching XML technologies into EDI workflows. On arrival, you might decide to XML-ify an EDI message for internal processing. On the way out, you might do the operation in reverse. The result can be an internal workflow based on XML processing which, to the outside world, appears as EDI.
Dig Deeper on Development implications of microservices architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.