Question
What's the recommended method to integrate with a stream data set?
The stream dataset help file says the following:
It is recommended that you use a Pega REST connector rule to populate the Stream data set with external data. Besides the Pega REST connector rule, a Stream data set also exposes REST and WebSocket endpoint, however it is recommended that you use a Pega REST connector rule instead whenever possible.
Here, what does Pega REST connector rule mean? Is it recommended to make use of the OoTB REST API (DatasetDetails) that allows to get results from datasets?
In general, websockets seem to have better performance and reliability when compared with REST APIs as they are better suited for stream data. Having said that, why is Pega recommending to make use of REST APIs instead of the web sockets that come along with the stream data sets?
Thanks in advance.
Updated: 4 May 2020 10:06 EDT
Pegasystems Inc.
US
You can use Realtime Data flow or Dataset-Execute API to consume stream dataset. The REST endpoint can be used as well. Check the link: https://community.pega.com/sites/default/files/help_v83/procomhelpmain.htm#rule-/rule-decision-/rule-decision-dataset/dsm-creating-stream-data-set-record-tsk.htm
Areteans Technology Solutions
AU
Hello @KevinZheng_GCS ,
The post does not mention why REST API is recommended when compared to websockets.
Pegasystems Inc.
IN
Hi ,
You can create your own service or you can use the OOTB Rest service of the stream data set
both are having its advantage as well as its disadvantage
Considering the high volume of data I will recommend the OOTB Rest service of the stream data set, I am using that to process high volume of events and not seeing any issue in prod.
Advantage of OOTB
1. Can process High volume of data
2. As it runs on dedicated stream nodes so it has very less downtime or no downtime
3. better response time compared to traditional RESTservice
Disadvantage
1. No data validation (it will accept any valid JSON , it will not check whether the property exists or not )
2. Only returns Raw response
3. Supports only basic auth . (I am using 8.2 )
Thanks,
Rakesh