Design Patterns (Integration)

The following content reflects the Pricefx design pattern best practices approach for inbound and outbound data integration processes.

Integration Choices by Tier

The following tables represent the different types of integration options available for Pricefx projects, use the following key to decipher who is performing these activities:

GREEN = Can be done by partners/customer

ORANGE= Unlikely to be done by partners/customers

RED = Cannot be done by partners/customers

GOLD STANDARD for Integration Projects:

Route Type	Frequency	Amount of Data	Near Realtime, Scheduled, and/or Big Data	Realtime/API (always small data)	Archiving

Route Type

Frequency

Amount of Data

Near Realtime, Scheduled, and/or Big Data

Realtime/API (always small data)

Archiving

Inbound

daily updates to Master Data
weekly updates to Transactions

initial up to 20 millions of rows
daily hundreds of thousands of rows
up to 1 million or rows per file

CSV files put in SFTP area, using IM Templates and .done files:

Industry Standard
Can be done by anyone who’s received training.
Can be modified by anyone, including customer post-go-live.
Easily monitored (out of the box)
Documentation for Inbound
Documentation for Outbound

Customer uses PriceFX Open API:

Implemented by customer so they can do whatever, modify whenever, and monitor however they please.
Documentation for Open API

only failed files

Outbound

daily exports to files

100s of thousands
100 thousands per file

CSV files exported to SFTP area
Rows exported by a timestamp on schedule

hundreds of calls to simple REST endpoints

only failed files

SILVER STANDARD for Integration Projects:

Route Type	Frequency	Amount of Data	Near Realtime, Scheduled, and/or Big Data	Realtime/API (always small data)	Archiving

Route Type

Frequency

Amount of Data

Near Realtime, Scheduled, and/or Big Data

Realtime/API (always small data)

Archiving

Inbound

daily updates

initial over 50 millions or rows
daily millions rows
up to 1 million or rows per file

CSV files put in SFTP area, with abnormal formatting and/or small changes to Integration Template code:

Modifications will likely require a Pricefx Integration Engineer.
Can be modified by anyone, including customer post-GoLive.

Non-CSV Integration Templates:

Not industry standard
Can be done by anyone who’s received training.
Can be modified by anyone, including customer post-GoLive.
Easily monitored (out of the box)
All available Integration Templates can be found here

Customer uses PriceFX Open API:

Implemented by customer so they can do whatever, modify whenever, and monitor however they please.
Documentation for Open API

only failed files

Outbound

daily exports to files

100 thousands
100 thousands per file

CSV or XML files exported to SFTP area
Rows exported by a timestamp on schedule or on an event

hundreds of calls to simple REST endpoints

only failed files

BRONZE STANDARD for Integration Projects:

Route Type	Frequency	Amount of Data	Near Realtime, Scheduled, and/or Big Data	Realtime/API (always small data)	Archiving

Route Type

Frequency

Amount of Data

Near Realtime, Scheduled, and/or Big Data

Realtime/API (always small data)

Archiving

Non-template interfaces:

Made completely by Pricefx IE.
Monitoring difficult, will require more budget + time to implement.
Dependent on Pricefx for adjustments post-go-live.

Heavily Modified Integration Template:

Will almost certainly require a Pricefx Integration Engineer.
Monitoring difficult, will require more budget + time to implement.
Dependent on Pricefx for adjustments post-go-live.

Custom Endpoints:

Made completely by Pricefx IE.
Monitoring difficult, will require more budget + time to implement.
Dependent on Pricefx for adjustments post-GoLive.
Will always be slower than directly using the Open API.