Question
Bank Of America
US
Last activity: 10 Oct 2019 2:26 EDT
Keyed DataPage
How is Keyed DataPage different from Node level datapage in terms of server trips.
Node level data page refresh strategy is once in a day and same is with keyed data page. How is it different???
Pegasystems Inc.
IN
Hi,
Node level Data page specifies the scope of a data page. The scope handles who and how it will be accessed.
Keyed Page is an access strategy, and applicable for Pagelist structure only.
You can check below post where it discuss about Keyed Page
https://collaborate.pega.com/question/data-page-keyed-reference
You can also check our CSSA course for data page details.
Thank You
Bank Of America
US
Hi Shubham,
Have gone through the keyed data page course and it was mentioned "Using a keyed data page when retrieving data for application use can make processing more efficient by reducing the no of server trips."
Now my question is if node level data page is loaded without keyed access pattern, it will also have single server trip to pull the data unless we add efresh strategy. So how is it different from keyed pattern access with respect to server trips?
Pegasystems Inc.
US
More information about Keyed Data Page, see attached document.
Bank Of America
US
Hi Susan ,
Have gone through the keyed data page course and it was mentioned "Using a keyed data page when retrieving data for application use can make processing more efficient by reducing the no of server trips." . Also gone through the example you have provided.
Now my question is if node level data page is loaded without keyed access pattern, it will also have single server trip to pull the data unless we add efresh strategy. So how is it different from keyed pattern access with respect to server trips?
Pegasystems Inc.
US
Keyed data page reducing the server trips in terms of how we use the data page
Example -->
Ecommerce website receiving number of requests for a particular product catalog.
So now to solve this server load we would load the Product in first query and then its pre-loaded into memory else we had to have a server trip every time.
It all about the number of request before the data is stale. Its simple if data is frequently accessed and not changed with user defined keys then we go for keyed data page.
So we will have just one List Structured Data page but we can have lots of keys, "so each key will NOT generate a difference instance of Data page"
Now how node level data page is different.
Node level data page is all about data not being changed for a long time. But how to solve the same problem of number of request which are even specific to number of user defined keys?? Here we would have lots of Node level Data pages with user defined keys.