Paging in ASP.NET Core Web API
►► Check out our courses: https://bit.ly/cdmz-courses
►► Support us on Patreon and get the source code: / codemaze
In this video, we are going to learn how to create Paging functionality in ASP.NET Core Web API. We are going to show the initial implementation, apply the pagination, and then show you how to improve even more the solution.
LINKS MENTIONED IN THE VIDEO:
To visit the whole article and download the source code visit:
►► https://code-maze.com/paging-aspnet-c...
To learn more about the ASP.NET Core Web API development, visit:
►► https://code-maze.com/net-core-series/
To watch the repository pattern video, visit:
►► • Repository Pattern In ASP.NET Core We...
To visit our site:
►► https://code-maze.com/
FOLLOW US ON SOCIAL MEDIA!
►► / marinko-spasojevic
►► / codemazeblog
►► / codemazeblog
VIDEO SUMMARY:
In this video, we’re going to learn how to implement paging in ASP.NET Core Web API. Paging (pagination) is one of the most important concepts in building RESTful APIs.
As a matter of fact, we don’t want to return a collection of all resources when querying our API. That can cause performance issues and it’s in no way optimized for public or private APIs. It can cause massive slowdowns and even application crashes in severe cases.
The source code for this video can be found on the GitHub repo. If you want to follow along with the article, you can use the start branch and if you want to get the final solution or if you get stuck, switch to the end branch.
NOTE: Some degree of previous knowledge is needed to follow this article. It relies heavily on the ASP.NET Core Web API series on Code Maze, so if you are not sure how to set up the database or how the underlying architecture works, we strongly suggest you go through the series.
What is Paging?
Paging refers to getting partial results from an API. Imagine having millions of results in the database and having your application try to return all of them at once.
Not only that would be an extremely ineffective way of returning the results, but it could also possibly have devastating effects on the application itself or the hardware it runs on. Moreover, every client has limited memory resources and it needs to restrict the number of shown results.
Thus, we need a way to return a set number of results to the client to avoid these consequences.
Let’s see how we can do that.
We’ll discuss what paging is, the easiest way to implement it, and then improve on that solution some more to create a more readable and flexible codebase.
Смотрите видео Paging in ASP.NET Core Web API онлайн без регистрации, длительностью часов минут секунд в хорошем качестве. Это видео добавил пользователь Code Maze 21 Июль 2020, не забудьте поделиться им ссылкой с друзьями и знакомыми, на нашем сайте его посмотрели 28,078 раз и оно понравилось 451 людям.