When comparing Spock vs Apiary, the Slant community recommends Spock for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Spock is ranked 2nd while Apiary is ranked 11th. The most important reason people chose Spock is:
Spock parses request URLs into well-typed data without requiring your routes to be declared at the type level.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Type-safe, function-level routes
Spock parses request URLs into well-typed data without requiring your routes to be declared at the type level.
Pro Small but complete
Unlike scotty it manages to be small and, at the same time, includes all the necessities like sessions and db pool.
Pro Automatically generates API documentation
Apiary generates comprehensive HTML documentation based on your API routes.
Pro Type-level routes
Apiary provides type modeling, down to URL parameters, ensuring type safety.
Cons
Con Mediocre documentation
Users must rely primarily on the example project and auto-generated API documentation (Haddocks). The author of Apiary is not a native English speaker and openly acknowledges this issue.