Question
Pega Systems
IN
Last activity: 24 Oct 2017 10:21 EDT
Recurring batch of 2000 records - MQ vs REST
We have a requirement where Pega receives 2000 records as a batch from legacy system for every three hours.
We need to send individual responses to those 2000 back to legacy system with the work object ID.
Currently options we are considering:
- Synchronous REST service
- Asynchronous REST service
- Using MQ for queuing
- Batch File Listener
We already have a bunch of REST services that communicate with legacy system - some synchronous and some asynchronous.
What would be an ideal option for scalability, maintainability?
Pegasystems Inc.
IN
I cant comment about the underlying architecture of each of these methods, but considering this is to deal with 2000 odd records, its better you go for an async mechanism . So my vote will go for Async REST.
Pega Systems
IN
Thank you for your response. I am inclined to Async REST.
I was trying to know any reasons not to consider MQ. Customer's legacy system already has MQ configured.
Pegasystems Inc.
IN
Well, I picked up Async REST keeping in mind Performance of the application.
Not sure how impactful MQ will be.
Lets see what others has to say.