When comparing Postgrest vs Nested-Routes, the Slant community recommends Postgrest for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Postgrest is ranked 8th while Nested-Routes is ranked 9th. The most important reason people chose Postgrest is:
JSON is handled by PostgreSQL which speed is hard to beat in your own applications. Response times as high as 2000 requests/sec on [Heroku free tier](https://www.slant.co/topics/3478/~platform-as-a-service-providers-that-have-a-free-plan).
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Fast
JSON is handled by PostgreSQL which speed is hard to beat in your own applications.
Response times as high as 2000 requests/sec on Heroku free tier.
Pro Easy to use
Pro Linux, Windows, FreeBSD, OS-X
Linux, Windows, FreeBSD, OS-X versions available.
Pro Embed Attoparsec parsers and regular expressions in a routable url
If you have a data encoding you would like to allow as a path chunk, you can do so by routing with an attoparsec parser or regular expression directly.
Pro Nesting of Handlers
The ability to give a handler child handlers turns a list of handlers into a tree of handlers - much easier to maintain.
Pro Simple and Concise
Routing a RESTful api is very literal in Nested-Routes.
Cons
Con Complicated Types
There is a lot of advanced language extensions in use for the engine - if you have a typo somewhere, the errors are practically impossible to understand.