Skip to main content

Asynchronous Processing

Batch Processing (PPN)

High-throughput asynchronous address normalization and geocoding via SFTP for massive enterprise datasets.

Architecture & Integration Model​

Egon Polling Process Normalization (PPN) is an automated, file-based engine optimized for processing millions of records without per-row API overhead. Compare the integration models to choose the right approach for your workload:

Architectural DimensionBatch PPN EngineReal-Time REST API
TransportSFTP (paired .zip + .trk files)HTTPS REST (JSON / GET / POST)
Primary Use CaseDatabase cleanups, ERP migrations, data warehousesCheckout forms, CRM single lookups, web apps
ExecutionAsynchronous daemon polling the input folderSynchronous request-response with low latency
ThroughputHundreds of thousands to millions of rows per batchOptimized for individual and small burst calls
Data PreservationZero data loss: source columns 0..N kept intactNormalized JSON payload structure

The 3-Step Lifecycle​

Processing follows an automated lifecycle between your integration and the Egon server:

PhaseActor / LocationAction
1. DepositClient → ./input/Upload <filename>.zip (containing <filename>.csv) and its <filename>.trk, which can stay on the server for later runs.
2. ProcessDaemon EngineA background worker polls ./input/, picks up each archive with its descriptor, and enriches the records.
3. DeliveryClient ← ./output/Engine deposits <filename>_output_<timestamp>.gz with 32 appended fields (27 with NOR;) ready for retrieval and cleanup.

Documentation Guide​

Explore the technical specifications and operational workflows: