Identity Resolution: Do I use Transactional or Multi-Process?

D&B Direct+ provides three ways to use Identity Resolution:

  • Transactional
  • Small batches (Multi-Process Match or Extended Match)
  • Large batches (Multi-Process High-Volume Match)

When to use Which

  • If the use case requires an immediate response (e.g., a UI-based application), use the transactional API.
  • If an immediate response is not required, guidelines are as follows:
    • Fewer than 4,000 requests, use transactional.
    • More than 4,000 but fewer than 25,000, use multiprocess API match feature.
    • More than 25,000, use the multiprocess API high-volume match feature.

File Sizes and Response Times

Transactional Multi-Process Match or Extended Match Multi-Process High-Volume Match
Maximum File Size n/a 10 MB 1 GB
SLA 300ms 25,000 records/hr once processing begins 500,000 records/hr once processing begins (for Latin). When submitted, the request is added to a processing queue; once processing begins, approximately 500,000 records will be processed per hour.
Notes Requires additional infrastructure; please contact your D&B representative.