<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sorting on Devops Monk</title><link>https://devops-monk.com/tags/sorting/</link><description>Recent content in Sorting on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/sorting/index.xml" rel="self" type="application/rss+xml"/><item><title>Pagination and Sorting in Spring Boot</title><link>https://devops-monk.com/tutorials/spring-boot/spring-boot-pagination-sorting/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/spring-boot/spring-boot-pagination-sorting/</guid><description>Returning all records from a large table in a single response is a recipe for slow APIs and crashed servers. Pagination is not optional — this article shows how to implement it properly with Spring Data.
The Problem with Returning Everything // Never do this for large datasets @GetMapping(&amp;#34;/api/orders&amp;#34;) public List&amp;lt;Order&amp;gt; getOrders() { return orderRepository.findAll(); // 1 million orders → OutOfMemoryError } Even for &amp;ldquo;small&amp;rdquo; tables, always paginate. Requirements change, data grows.</description></item></channel></rss>