Skip to main content
Software Engineering

Return to Question

Post Timeline

Capitalised API acronym and added code formatting for URIs
Source Link
edit approved Feb 7, 2015 at 0:47
Greenonline
edit approved Feb 7, 2015 at 0:47
Greenonline
  • 145
  • 2
  • 2
  • 11

How to design a RESTful apiAPI with good performance

When designing RESTful apisAPIs, one of the rules is: "URI designates exactly one resource" , but in the real world we also like good performance and one thing to kill performance is the N+1 problem.

So how exactly are we supposed to avoid the N+1 problem without making more than one URI for the same resource /api/foos/?page=1/api/foos/?page=1 or /api/foo/1/api/foo/1 where /api/foos//api/foos/ returns a list of foos in order to get decent performance.

How to design a RESTful api with good performance

When designing RESTful apis, one of the rules is: "URI designates exactly one resource" , but in the real world we also like good performance and one thing to kill performance is the N+1 problem.

So how exactly are we supposed to avoid the N+1 problem without making more than one URI for the same resource /api/foos/?page=1 or /api/foo/1 where /api/foos/ returns a list of foos in order to get decent performance.

How to design a RESTful API with good performance

When designing RESTful APIs, one of the rules is: "URI designates exactly one resource" , but in the real world we also like good performance and one thing to kill performance is the N+1 problem.

So how exactly are we supposed to avoid the N+1 problem without making more than one URI for the same resource /api/foos/?page=1 or /api/foo/1 where /api/foos/ returns a list of foos in order to get decent performance.

Source Link
Esben Skov Pedersen
Esben Skov Pedersen
  • 5.2k
  • 2
  • 26
  • 24

How to design a RESTful api with good performance

When designing RESTful apis, one of the rules is: "URI designates exactly one resource" , but in the real world we also like good performance and one thing to kill performance is the N+1 problem.

So how exactly are we supposed to avoid the N+1 problem without making more than one URI for the same resource /api/foos/?page=1 or /api/foo/1 where /api/foos/ returns a list of foos in order to get decent performance.