axway.com
4
B2B EDI B2B APIs
Technical Attributes
Batch/semi-real time
Real time
Asynchronous
Synchronous
Defined service levels (non-repudiation, security, acknowledgment)
No pre-defined service levels
Hundreds of transactions/sec
Thousands of transactions/sec
Used with messages and large files
Used mainly with small messages
Requires middleware on both B2B ends
Only requires middleware on one end
Communication protocols : AS1/AS2/AS3/AS4, SFTP, FTPS, ebMS
Communication protocols: REST, SOAP WS
Message formats: XML, X12, EDIFACT
Message formats: JSON, XML
Mainly for B2B integration
B2B integration, A2A integration, as well as cloud/on-premise hybrid integration
Governance is entrenched in EDI history
Governance is a new trend, just started to be viewed as a must have
Installations are on-premise hybrid with a migration trend to the cloud
Delivered equally on-premise and in cloud
EDI and API: delivering digital B2B integration
The main differences between EDI and APIs for B2B data
exchange also complement each other and allow for a
digital B2B integration solution.