We can have data from different sources as we want. Reltio is like a database where the data comes from one source and moves through another medium. In our case, we are using MuleSoft as a medium between our systems and Reltio. Sometimes, we send large amounts of data, like 10,000 or 50,000 records. Reltio can handle however much data we send, but there is always a limitation with MuleSoft. While MuleSoft has limitations, Reltio doesn't, and it can process large amounts of data.
Reltio provides three indicators for monitoring performance: green, yellow, and red. If the tenant is working as expected, it shows green. When a high volume of data is processed, it may show yellow, so we should temporarily restrict usage. Once the data load is processed, it turns green, ensuring performance isn't reduced. If the tenant turns red, it’s a high alert state, and we need to contact Reltio.
I’ve worked with Reltio for the past two years and haven’t seen the tenant turn red. It turns yellow when processing around 15,000 to 30,000 records from a source, but it goes back to green after about 30 minutes to an hour. Overall, the data broker works smoothly, and we haven't faced any significant difficulties while handling most of the data.
They have provided something called Reltio Integration. It's a platform they introduced about four to five months ago. It’s AI-based and helps users quickly solve their queries. Newcomers working with Reltio who might have questions or doubts about the UI can easily find answers through the AI or contact the support team. The AI is also configured to create manuals and has been successfully integrated. They are also continuing to work on improving the AI tool further.
It doesn’t require maintenance at our end. During those times, we need to avoid using the system.
I highly recommend it. One major benefit is that they provide custom Java utilities. These utilities allow us to extract or load data in bulk, which would otherwise be difficult to manage individually. With these tools, we can load or extract data as needed.
Overall, I rate the solution an eight out of ten.