Get Paged List Example
Overview
Complete Flow Architecture
GET Request → Controller → Service → Query Handler → RESTClient → External System
↓
Response ← Controller ← Service ← Query Handler ← RESTClient ← External SystemDetailed Flow Breakdown
1. GET Request
↓
2. Controller (API Entry Point)
↓
3. Service Layer (Business Orchestration)
↓
4. Query Handler (RESTClient Integration)
├── Internal DTO → Request DTO Mapping
├── RESTClient Call to External System
└── Response DTO → Internal DTO Mapping
↓
5. Response (Paged List with Metadata)Step-by-Step Implementation
1. API Controller - The Entry Point
2. Service Layer - Business Orchestration
3. Query Handler - RESTClient Integration
4. Query Parameters - Input DTO
5. Output DTO - Data Transfer Object
6. AutoMapper Configuration - Data Transformation
Key Differences from Get List
Get Paged List vs Get List Characteristics
Aspect
Get Paged List
Get List
Get Paged List-Specific Features
Common Use Cases
Flow Summary
Synchronous Flow (Data Retrieval)
No Asynchronous Flow
Query Building Patterns
Basic Query Building
Advanced Query Building with Sorting
Pagination Metadata
FlexiPagedList Structure
Frontend Integration Example
Performance Considerations
Optimization Strategies
When to Use Get Paged List vs Get List
Scenario
Use Get Paged List
Use Get List
Error Handling
HTTP Status Codes
Parameter Validation
Key Benefits
Last updated