If I start an EDI project today, I will use a general purpose language like C#, Java and supporting libraires. Unmatched performance, powerful access to all language / framework features and cost effective (build is expensive but run (support and TCO is cheaper).
Building it out can be alot more expensive in not only money but time. Also if the build is not setup in a flexible way to add on new document types. Too many build their solution just for what is needed now and not for what might be needed. Too many build just for ANSI X12 than need XML or JSON as an example. I do agree the long term cost can be a money saver and time saver.
@EDISupportLLC yeah, the time it takes is obviously dependent on the skillset of the team. Higher skill means higher cost. Your point about other doc types is on point. EDI is about file transfer/translation and enrichment of ANY type... example IDocs, csv etc... modular design will be imperative for this to work.
If I start an EDI project today, I will use a general purpose language like C#, Java and supporting libraires. Unmatched performance, powerful access to all language / framework features and cost effective (build is expensive but run (support and TCO is cheaper).
Building it out can be alot more expensive in not only money but time. Also if the build is not setup in a flexible way to add on new document types. Too many build their solution just for what is needed now and not for what might be needed. Too many build just for ANSI X12 than need XML or JSON as an example. I do agree the long term cost can be a money saver and time saver.
@EDISupportLLC yeah, the time it takes is obviously dependent on the skillset of the team. Higher skill means higher cost. Your point about other doc types is on point. EDI is about file transfer/translation and enrichment of ANY type... example IDocs, csv etc... modular design will be imperative for this to work.