Address Verification is developed using the C++ programming language. Address Verification provides different software packages to suit the hardware and software environment in which you install Address Verification. The Address Verification software packages contain C and Java based APIs.

If you call the Address Verification engine through Java, install a Java Development Kit on the machine that hosts the Address Verification engine.

You can install Address Verification on machines with the following configurations:

The device on which you install Address Verification must have a minimum of 512 MB RAM.

Each function server, including standby function servers require 300 MB of RAM. If you enable hot swapping, the total memory usage doubles for Address Verification. For each job, you need a variable amount of memory based on your configuration settings.

Before you finalize the memory requirements, consider the size of the reference address databases that you require. The complete set of worldwide postal reference databases, including supplementary databases for address enrichments, consumes approximately 55 GB of storage space.

Preloading databases into memory significantly improves the performance of Address Verification. The device on which you install Address Verification must have sufficient RAM to preload the databases that you require.

As the total size of the worldwide databases is approximately 55 GB, the RAM required to preload all databases and perform address processing is approximately 60 GB. For smaller file sizes, less RAM is required. For example, the worldwide batch and interactive databases consume approximately 8 GB of space, and the geocoding databases consume an additional 4.5 GB. To preload and run the worldwide batch, interactive, and geocoding databases, the maximum amount of RAM that you require is 12 GB. The enrichment databases require a RAM of 2.3 GB and the quick capture databases require 33.1 GB RAM.

You set the database preloading method in the

IDVEConfig.json

file. For information about the database preloading, see Configuring the Engine.