Need advice about which tool to choose?Ask the StackShare community!
GraphQL vs Nancy: What are the differences?
GraphQL: A data query language and runtime. GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012; Nancy: A lightweight web framework for .NET. Nancy is a lightweight, low-ceremony, framework for building HTTP based services on .NET Framework/Core and Mono. The goal of the framework is to stay out of the way as much as possible and provide a super-duper-happy-path to all interactions.
GraphQL can be classified as a tool in the "Query Languages" category, while Nancy is grouped under "Microframeworks (Backend)".
"Schemas defined by the requests made by the user" is the top reason why over 61 developers like GraphQL, while over 2 developers mention "C#" as the leading cause for choosing Nancy.
GraphQL and Nancy are both open source tools. It seems that GraphQL with 11.7K GitHub stars and 753 forks on GitHub has more adoption than Nancy with 6.8K GitHub stars and 1.46K GitHub forks.
Pros of GraphQL
- Schemas defined by the requests made by the user75
- Will replace RESTful interfaces63
- The future of API's62
- The future of databases49
- Self-documenting13
- Get many resources in a single request12
- Query Language6
- Ask for what you need, get exactly that6
- Fetch different resources in one request3
- Type system3
- Evolve your API without versions3
- Ease of client creation2
- GraphiQL2
- Easy setup2
- "Open" document1
- Fast prototyping1
- Supports subscription1
- Standard1
- Good for apps that query at build time. (SSR/Gatsby)1
- 1. Describe your data1
- Better versioning1
- Backed by Facebook1
- Easy to learn1
Pros of Nancy
- C#3
- .Net2
- Middlewares1
- Sinatra inspired1
Sign up to add or upvote prosMake informed product decisions
Cons of GraphQL
- Hard to migrate from GraphQL to another technology4
- More code to type.4
- Takes longer to build compared to schemaless.2
- No support for caching1
- All the pros sound like NFT pitches1
- No support for streaming1
- Works just like any other API at runtime1
- N+1 fetch problem1
- No built in security1