An AWS Lambda integration (Okta & ADP) story of a leading retailer

Continue Reading

The client had a legacy middleware built on Java & on-premises Informatica jobs. These integration points served as a point-to-point interface that connect HRMS (ADP) & identity access management tools (Okta).   

 The employee datasets from HRMS are ingested in PostgreSQL database through Informatica jobs. Further, these employee datasets are synchronized with Okta through legacy middleware application (Java-based, Monolithic architecture).  

To sum up, the challenges in their legacy integration points were:

• Monolithic architecture (Middleware application) that has high coupling and is hard to scale. 
• Excess licensing cost spent on Informatica & infrastructure
• Tiring maintenance activities for middleware & Informatica jobs
• Reluctance to adopt market changes and future innovations.
• Prolonged time to market. 
• Unoptimized code and deployment model. 

Solution: An AWS Lambda integration that connects ADP & Okta with a reduced total cost of operation (TCO)

Our integration experts embarked on and analyzed the ins & outs of the client’s existing integration points that synchronize the HRMS & IAM tool. Based on the business impact, organizational IT landscape & unique business needs, we proposed the modernization of legacy middleware & Informatica jobs with AWS Lambda solutions. 

Eliminating the on-premises Informatica jobs and Java-based applications was paramount in this engagement. We reengineered their integration points as two segments. 

• Data Ingestion
• Data Synchronization

Data Ingestion

Our experts kick-started the transformation by replacing their on-premises Informatica jobs with AWS Lambda service (Data ingestion Lambda).  This integration service extracts the employee datasets from HRMS and ingests them in PostgreSQL transactional database at regular intervals. (For instance, at a cycle of 15 minutes). 

Data Synchronization

Successively, to synchronize employee datasets in PostgreSQL with Okta, we replaced their legacy middleware(Java-based) with another AWS Lambda service(Data synchronization Lambda). We employed AWS Eventbridge triggers for periodical synchronization of datasets (15 minutes cycle). 

For efficient performance, we migrated these datasets as batches to Okta. Also, in case of fallback, we built a separate process for incremental migration of leftover datasets. 

Business Gains 

• Optimized cloud-based integration solutions that connect HRMS & IAM tools.  
• Lightweight integration architecture 
• 100% flexibility to adopt market changes and future innovations 
• Slashed API consumption from HRMS & Okta to 95% 
• 100% reduction in Informatica licensing cost.  
• 75% reduction in deployment efforts & faster time to market 

Tech Stack