Question3Replies39Views _JVV_Sharma Member since 2011 43 posts PEGA Posted: 2 years agoLast activity: 2 years 10 months ago Closed Recurring batch of 2000 records - MQ vs RESTWe 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 serviceUsing 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? Data Integration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 2 years agoSantanu PEGA replied to _JVV_SharmaI 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. Posted: 2 years ago_JVV_Sharma PEGA replied to _JVV_SharmaThank 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. Posted: 2 years agoSantanu PEGA replied to _JVV_SharmaWell, 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.