top of page
  • Writer's pictureGreat Companies

Aditya Mukhopadhyay, Founder at RecallGraph

Great Companies: How did you get your idea or concept for the business?

Aditya Mukhopadhyay: I started building RecallGraph in Jan 2019, the inspiration for which came from two distinct sources: Prior to RecallGraph, I got the chance to work with graph databases and event stores in two independent projects. Somewhere along the way, it struck me that one could combine the core concepts of both into a single product. In fact, in most projects I had worked on, there was always an underlying problem around data history retention that I felt could be best addressed directly in the DB layer. This is what put me on the path to building RecallGraph. For a detailed introduction, please visit never-lose-your-old-data-again.

Great Companies: What are the various Services provided by RecallGraph

Aditya Mukhopadhyay: RecallGraph is a product company at heart, with support offered for getting up and running within the customer's IT infrastructure, and further consultancy available for best practices in modelling data for temporal storage and access.

Great Companies: What makes RecallGraph different from similar service providers ?

Aditya Mukhopadhyay:

There are few providers globally, who combine data versioning and graph traveral features into a single, seamless package. RecallGraph is proud to be one of them. Graph data versioning is still a nascent market and the concept is yet to achieve mainstream congnizance. In this situation, what makes RecallGraph different from generic data product/service providers is that it is uniquely pushing the boundaries of the core concepts behind data management, and challenging the status quo on what it means to store, process and audit historical data.

Great Companies: What are the struggles and challenges you face?

Aditya Mukhopadhyay: The core challenge is to help C-suite decision makers ascend the "Bi-temporal Maturity Ladder" (a term coined by Rob van Dort from EntityGrid). Basically, it is a process of incrementally upgrading their awareness of a looming problem hidden in plain sight, and the elegant solution that bi-temporality provides. This cognitive ladder can be roughly broken down into the following steps:

1. Basic ignorance - What is bi-temporal?

2. Practical ignorance - Do we need it?

3. Underestimation - Can't be that hard. We can build it in-house.

4. Reality kicks in - This is REALLY complex and extremely difficult to get right!

5. In control - We finally understand. Let's implement!

As evident, a huge part of RecallGraph's marketing/sales effort actually goes into explaining the need for bi-temporal (what does it solve? why do we need it?), followed by the concept itself.

Great Companies: How do you plan to grow in the future? What does 5 years down the line look like for RecallGraph?

Aditya Mukhopadhyay: Hopefully, in 5 years, data-versioning as an idea will reach the critical mass required to become embedded in mainstream IT consiousness as a core component of any enterprise data management solution. RecallGraph sees itself at the forefront of the wave that brings about this paradigm shift in thought process, at the end of which it aims to become synonymous with enterprise data versioning and temporal graph processing.

Great Companies: If you had one piece of advice to someone just starting out, what would it be?

Aditya Mukhopadhyay: Be prepared to take huge risks. Be prepared to face failure. There are no shortcuts, no safe roads, rarely any plan B to fall back on. You must take a leap of faith, so do not do this unless you REALLY believe in what you're setting out to do. Finally, words to live by, by David Lloyd George, "One cannot cross a chasm in two small jumps."



bottom of page