11-19-2021 12:00 AM
Business use case was to flow transaction data between two systems in real time instead batch on any event happened between source vs destination and destination vs source. Challenge are, it was pull model by design and batch and user was not able to get real time info between two system after did some modification, we have to wait until batch complete.
Here we jumped to use SnapLogic as a middle tier to make the system real time, instead pull by batch source and destination system will push the change to SnapLogic on any event. SnapLogic triggered task and different security mechanism available helped us to implement and along with multiple Snaps.
Innovation strategy steps included:
1- How outside system will call SnapLogic since SnapLogic instance was groundplex and under company VPC. Infrastructure change on api gateway(dmz) level.
2- Whether source and destination system has push mechanism available or not on any event.
3- How to authenticate that system in SnapLogic since it was in bound call.
4- How much volume of request we can process looking into current system configuration (cpu and memory and node availability and integrated log gathering for audit). Bottom line is we followed best practice like secure, resilience and low latency.
(Ali Sharifian, asharifian@snaplogic.com) was involved on this to help it out, design we did look into our existing system nature, business request and Infrastructure restriction.
We made the system fully automated and real time data availability to user, it was great result to business and as well as maintenance cost saving to company.
We are going to use similar kind of execution for other use case also, now snapLogic will become key for company to integrate most of the system as a middle tier.