Hi Vishal,
The size of the pages of your request and the side of the pages on the UI
doesn't need to be in sync. There is no issue in caching a couple of
thousands of rows in your frontend services.
it takes some planning and calculation. for example, if you keep 10 pages
of data in the
I would go with redis caching.
https://redis.io/topics/introduction
--
You received this message because you are subscribed to the Google Groups
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
There are no wildcard searches. The search is based on selecting proper
values from over 12 dropdown list. Sql Server is the database. I dont
really have an issue except that i dont like current approach of hitting
database for every 10 records. I want to be able to hold 1000+ records in
Answer this first.
1. Are you doing any wild card searches.
2. What backend is it?
Your issue most probably is not angular. Sounds like backend issue
--
You received this message because you are subscribed to the Google Groups
"Angular and AngularJS discussion" group.
To unsubscribe from
Its a search based on parameters selected by the user. There are about 10
parameters. Not all searches lead to 2 million but worse case scenarios
does. It uses restful API to pull records based on offset so it fetches
only 10 records at a time based on page user is on and if user has clicked
