After REST: Trying Out GraphQL
While solving a real over-fetching problem with GraphQL, I weigh where REST is still sufficient and where GraphQL actually makes sense.
Category
API design, forms, authentication and the server-side features of web applications. (Page 2/4)
This category has 23 posts.
While solving a real over-fetching problem with GraphQL, I weigh where REST is still sufficient and where GraphQL actually makes sense.
How binding API error responses to a consistent contract simplifies client development and debugging.
How Laravel Sanctum solves SPA authentication, and why its cookie-based approach is cleaner than token-based alternatives.
How returning the same response structure from every endpoint simplifies client code and makes errors predictable.
How do you evolve an API without breaking existing clients? A comparison of versioning strategies with their trade-offs, drawn from real-world experience.
How I use Laravel's task scheduler to run many scheduled jobs from a single cron entry, keeping the scheduling logic readable and version-controlled.