Paginated Angularjs Posts Application Performance Issue

Paginated AngularJS posts application performance issue I have made a small application that displays an posts JSON in the form of cards, with the help of AngularJS and Twitter Boo

Solution 1:

What if there ware 10 or 100 times as many posts, woud the application have a performance (page load) problem?

Yes, if you load on front-end a lot of data browser could be go down. You can dimostrate it, need only create a series of stress test. Try to return hundred of hundred of data from your back-end (not jsonplaceholder), the browser will freeze

Is there a better way to paginate the application; one that would load as many items from posts.json as there are displayed on one page (24 items), instead of the entire JSON file?

In my experience I did pagination using a collaboration between front-end and back-end side.

front-end: you can choose different kind of pagination (infinity scroll, standard pagination etc.) in base of your features.

back-end: you can create rest service that take in input the items per page and an offset (your page).

When on browser you change page you will demande the back-end the honer to call a pageable query.

In base of my experience I gained a good performance with a lot of data.