aureus-insights_logo

Nitin Purohit

Nitin Purohit

Nitin is CTO and co-founder at Aureus. With over 15 years of experience in leveraging technology to drive and achieve top-line and bottom-line numbers, Nitin has helped global organizations optimize value from their significant IT investments. Over the years, Nitin has been responsible for the creation of many product IPs. Prior to this role at Aureus, Nitin was the Global Practice Head for Application Services at Omnitech Infosolutions Ltd and was responsible for sales and profitability of offerings from application services across geographies.

Recent Posts:

How Event-Driven Processes are Used to Measure Customer Experience

Companies design application processes to provide the best possible experience for their customers. These processes rely on application and customer-originated events to function. These events and their outcome form the basis of the customer’s experience. Therefore, event-driven philosophy is an ideal way for companies to measure customer experience.

Stream-based Data Integration – No Formatting Required

One of the challenges insurers face when implementing any new cloud-based application into their workflow is the integration of both internal and external data. Gaining access and permission to use internal data can be the first hurdle. Adding the requirement to format the data in a specific format can be a show-stopper.

Cheers to Stream-based Data Integration...and to Never Losing a Byte!!

Enterprise applications belong to a vibrant ecosystem and consequently the data they generate is large and varied. Enterprises both benefit and suffer from this nature of application and data.Whenever a new application is to be deployed in an enterprise that integrates with the applications in the ecosystem, the precondition is an 'expansive data definition with referential value' on day 1 to start integration. Traditionally, this approach to data integration involves identifying a target data structure, and force fitting data from all sources into it. This is done to ensure a 'seamless' integration - never mind the loss of data considered irrelevant.

    Related Posts