POC exploration
Hybrid Property Enrichment Pipeline
40% cache hit rate · First details ~1.5s
Architecture diagram
Hybrid property enrichment pipeline
Fast address feedback and slower full enrichment are split into staged paths with normalization and Redis caching.
Borrower input
Address and property details
Raw address
Address normalization
Canonical address hash
Lookup key
Redis + memory cache
40% cache hit rate
Miss or stale
Third-party APIs
Deeper property enrichment
Full enrichment
Photo requirements
Submission-stage completeness
Submission ready
Lending workflow
Fast details first, complete package later
- The pipeline separated first response speed from full submission completeness.
- Normalization made caching materially useful instead of cosmetic.
- Partial data was treated as an explicit workflow state.
This POC came from a lending flow where property data had to be enriched using a mix of manual input and third-party APIs. The tension was familiar: users wanted fast initial feedback, but the business also needed richer data before submission, including mandatory photos and cleaner property details.
If everything happened synchronously, the form would feel heavy. If everything was deferred, the product would feel vague and underpowered. So the question was whether a hybrid enrichment model could give us enough speed up front without sacrificing the data quality the later workflow depended on.
We split the flow. Early property details could come back in roughly 1.5 seconds. The fuller submission path, including required photos and deeper enrichment, could complete closer to five seconds when needed. Address normalization and Redis-backed caching were big parts of the experiment because property lookups repeat more often than teams first assume, just under slightly messy variants of the same address.
The roughly 40% cache hit rate was one of the best outcomes from the POC. Not because it looked pretty on a slide, but because it told us the data hygiene work had real payoff. Normalization was not busywork. It materially changed both responsiveness and cost.
The trade-off was a less tidy pipeline. Hybrid systems mean partial data, staged completion, and more careful thinking about freshness. Some users will see faster responses than others. Some values can be trusted immediately. Others need slower validation. That is more complicated than a single blocking flow, but it is often much closer to how the business actually works.
The POC was useful because it replaced a vague speed-versus-completeness debate with a concrete pattern we could reason about.