How We Tamed Address Validation in PDP

In PDP, we connected an external service that automatically validates and normalizes an address when creating a real estate object. In other words, fewer “Lenina St./Lenina St./Leniна???” variants and more clean data — in the age of AI automation, that’s just table stakes 🙂

But we did it properly: the integration is optional and controlled by a feature flag. Need it — we turn it on; don’t need it — the system keeps running without it.

The most important part: if the validation service is unavailable, nothing breaks. The user simply enters the address manually. No drama, no “502, come back tomorrow.”

Another challenge was testing. We have multiple optional integrations at once: an external CRM, 1C, and the address service itself. The result is that classic combinatorial complexity, where there are more scenarios than tabs open in a developer’s browser before a release 😅