Looking for the FullContact Address Book App? You can now find it at Contacts+

Learn More

{ Developer Blog }

Dealing with Failure in a Distributed System

FullContact uses a microservice architecture both internally and for our customer-facing APIs. While microservices have a lot of benefits, one major drawback compared to a monolithic architecture is that there are a lot of additional potential points of failure. Given the nature of this architecture, our team tries to anticipate issues to ensure success for…

Continue reading

Real-time Analytics with Apache Druid at FullContact

Jeremy Plichta, Director of Engineering at FullContact; Janis Dancis, Sr. Software Engineer at FullContact; and Gian Merlino, co-founder and CTO of Imply talk all about Druid in their latest meet-up on September 17, 2019. Watch the replay below and see what the hype about Apache Druid is all about! Download the Slides FullContact Talk Summary…

Continue reading

Our Process of Deploying, Running and Maintaining Druid

FullContact is a people company and a data company. We believe that businesses can deliver higher quality products through better relationships and 1-1 customized service. Our Identity Resolution products (both batch and API) are what enables that to happen. We have several different APIs but they can be boiled down to two simple use cases:…

Continue reading

Never Put Secrets in URLs and Query Parameters

URLS and query parameters aren’t secure. They should never contain sensitive or important information (passwords, static shared secrets, private information, etc). It is asking for trouble, something we here at FullContact have discovered first-hand. Recently, a security researcher came to us with 75 of our customer’s API keys, and noted that they could get many…

Continue reading
Migrating from MongoDB to Cassandra

Migrating from MongoDB to Cassandra

We were a young startup and made a few crucial mistakes. MongoDB was not a mistake. It let us iterate rapidly and scaled reasonably well. Our mistake was when we decided to put off fixing MongoDB’s deployment, instead vertically scaling to maintain the Person API product while working on other technologies such as the FullContact Address Book and our ‘secret sauce’ behind the Person API.

Continue reading