Hemant Talele

In this project, I worked alongside a MuleSoft product consultant for the client to design and deliver an end-to-end implementation of a data migration/sync solution from scratch. This was the pilot implementation for the client's new MuleSoft-based integration platform; hence, it required a well-experienced small group of MuleSoft developers who could build a production-ready application in a concise period. The project started with an initial understanding of the data migration requirements, where we also analyzed and assessed options to integrate with the source (Microsoft Dynamics) and target (Salesforce). A detailed design followed, where we defined the end-to-end solution and implemented the same, following all standards and best practices. The implementation was completed quickly and was ready for production after a thorough testing phase. This was a pilot implementation, and it pawed the way for all future integration projects on the client's integration platform. The solution and the code are used as a reference for most subsequent projects on the integration platform.

This is one of the most recent Mule 4-based projects I worked on for PHSA. The project is a multi-year ERP system migration project that involves the de-commission of the current on-premise ERP system and the migration to the new Unit 4 cloud ERP system.
I worked on the integration part of the project as a MuleSoft SME/developer to implement all the integration requirements for the migration project. The project involved complex implementations that required integration with various internal systems using databases, RabbitMQ, and file connectors. I have also set-up the mule runtime environments for this project and configured them to connect to the MuleSoft Anypoint Platform in a Hybrid architecture model.

This project's requirements had one of the most common MuleSoft-based integration use cases in days—integrating the on-premise SAP system with a cloud-based Salesforce system.
I joined this project at a later (development stage) as a MuleSoft integration expert to help and expedite the implementation work. I could complete their pending implementation in less than planned by suggesting a solution design that reuses APIs and streamlines the poll processing. The proposed solution provides benefits such as a single point of entry and an interface for SAP outbound data flow, which eventually offers easy tracking and management of data flows and an API-led connectivity approach that helps reuse system APIs.
The implementation involves a hybrid deployment model involving AWS-hosted Mule runtime servers managed by a cloud-based runtime manager using VPC.

This project involved a complete design, development, and roll-out of Mule-based integration with Cvent (a 3rd-party event management system).
The client (Pfizer) wanted to migrate from their current event management provider (starcite) to Cvent. As a starting step, I created a POC demonstrating the feasibility of integrating with Cvent using MuleSoft and Cvent web services. The POC I demonstrated was successful, and the client decided to proceed with a production implementation of the integration solution based on the POC findings.
The production implementation I worked on post-POC involved the creation of multiple functional APIs to create, update, and search meetings and add/remove attendees. It also involves a few batch process implementations between Cvent and the client's internal systems.

This project involved the creation of APIs to facilitate retrieval of data from the client’s SAP system (master data source).
Before this project was implemented, the client was facing a challenge of ver slow response time from the SAP system for data retrievals. Hence the key focus for this Mule project was on improving the response time without compromising the accuracy of data retrieval.
The Mule solution I proposed involved leveraging Mule in-memory caching to improve the response time. The new API resulted in reducing the API response time from 3+ seconds to 200 milliseconds.
In order to ensure accuracy and avoid stale data, I also built a custom cache invalidation mechanism in the solution.
The project is a great success as I knew from the client later and is being used with zero post-production issues.