Are You Aware Of These Hidden Pitfalls To Building Your Own Entity Resolution Solution?
Building high-quality entity resolution capabilities can take years and demands a team with an array of skills spanning statistics, linguistics and performance engineering. Deep knowledge of entity resolution and its many edge cases is also crucial. Watch the video below with Senzing CEO Jeff Jonas talking about the challenges of building entity resolution in-house, so you can better understand just what you would be getting into if you build it in-house.
Building entity resolution in-house is expensive, takes a long time, and is likely to produce inferior results. Few organizations possess the necessary expertise in-house, or the foresight to build in the flexibility needed to adapt to evolving requirements.
Instead of building it yourself, you can add industrial-strength entity resolution to your enterprise applications and data systems with the Senzing® entity resolution API. Right out of the box you’ll get a solution that delivers the most advanced, real-time data matching and relationship detection capabilities available. With the Senzing plug-and-play API, you’ll get a faster time to value, higher-quality results and a lower TCO than building it yourself, or with any other option.
Edited Video Transcript
Timestamps
0:00 Introduction – Can Building Entity Resolution Really Be That Hard?
0:30 Beware of Building Entity Resolution In-House
1:08 Do Not Underestimate the Cost of Building Entity Resolution In-House
1:21 The Purpose of Senzing Entity Resolution
2:03 Senzing: Out-of-the-Box Plug-and-Play Entity Resolution
So, let’s say your organization is right now making a decision about whether you want to buy entity resolution – like a commercial off-the-shelf solution – or if you want to bring together a team and build it. To that, I say…aarrgh!…beware of the build path. It just seems to many people that building it can’t be that hard…can it really be that hard?
0:30 Beware of Building Entity Resolution In-House
Yes, it can, because unfortunately entity resolution has thousands, maybe millions, of edge cases. On this path [of building entity resolution], you will end up with a team. Some of the people on this team will have helped create a rather complicated contraption, and you’ll be beholden to them forever.
And then every time you want to add a new data set, every time you want to make it more scalable, or make it support another language, well…are you going to get some linguists to support the new language? To make it scalable, or to make a lower latency or to not batch, are you going to rewrite the architecture from the bottom up?
1:08 Do Not Underestimate the Cost of Building Entity Resolution In-House
Do not underestimate the cost of doing all this yourself. I kid you not: you could spend 30 million dollars in five years and have something that’s not commercial grade. Building it is just crazy.
1:21 The Purpose of Senzing Entity Resolution
So that’s really the purpose of Senzing entity resolution. In prior incarnations of our team and our technology, we were creating entity resolution technology for the elite. Today, we’ve built technology that’s accessible to everybody. It’s an API, it’s locally hosted, and no data flows to us.
You’re going to download the software, you’re going to compile it into your workflows, into your data quality workflows, your data integrity. You’re going to compile it into your ETL, you’re going to compile it into your anti-money laundering (AML), master data management (MDM), patient record systems, and so on and so on. And basically, right out of the box, you’re going to understand who’s who, and who’s related to who, so you can spend your energy on more important things.
2:03 Senzing: Out-of-the-Box Plug-and-Play Entity Resolution
The Senzing entity resolution API is out-of-the-box plug-and-play so you don’t have to build it yourself.