Falcor vs GraphQL

Overview

Falcor

Stacks27

Followers79

Votes14

GitHub Stars10.6K

Forks449

GraphQL

Stacks34.9K

Followers28.1K

Votes309

Falcor vs GraphQL: What are the differences?

Data Fetching Model: Falcor utilizes a "path" concept to fetch data directly from a JSON-like graph structure, enabling users to request specific data using paths. In contrast, GraphQL uses a declarative data fetching model where clients can specify the exact data needed using queries.
Data Caching: Falcor has built-in caching mechanisms to help reduce network requests by storing fetched data locally, allowing for efficient data retrieval when needed. GraphQL does not have built-in caching mechanisms and relies on the client to manage caching strategies.
Server-Side Implementation: Falcor is typically server-centric, with most of the logic residing on the server to handle data fetching and manipulation. On the other hand, GraphQL puts more emphasis on the client-side, providing flexibility for clients to define their data requirements without server modifications.
Response Structure: Falcor typically returns complete JSON responses containing the requested data along with metadata, which can be tailored to fit specific use cases. In contrast, GraphQL responses mirror the shape of the query, providing precise data requested by the client without additional metadata clutter.
Batching Requests: Falcor allows for batching multiple requests into a single network call, enhancing efficiency and reducing overhead. In contrast, GraphQL inherently supports requesting multiple resources in a single query, minimizing network round trips for complex data requirements.
Type System: GraphQL enforces a strongly typed schema where clients must adhere to predefined types and structures, ensuring consistency and reliability in data fetching processes. Falcor, while providing schema-like capabilities with its JSON graph structure, does not enforce strict types on clients, offering more flexibility but potentially leading to data integrity issues.

In Summary, Falcor and GraphQL differ in their data fetching models, caching mechanisms, server-side implementation, response structures, request batching capabilities, and type system enforcement.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

Falcor	GraphQL
Falcor lets you represent all your remote data sources as a single domain model via a virtual JSON graph. You code the same way no matter where the data is, whether in memory on the client or over the network on the server.	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.
One Model Everywhere;The Data is the API;Bind to the Cloud	Hierarchical;Product-centric;Client-specified queries;Backwards Compatible;Structured, Arbitrary Code;Application-Layer Protocol;Strongly-typed;Introspective
Statistics
GitHub Stars 10.6K	GitHub Stars -
GitHub Forks 449	GitHub Forks -
Stacks 27	Stacks 34.9K
Followers 79	Followers 28.1K
Votes 14	Votes 309
Pros & Cons
Pros 2 Data is the API 2 One Model Everywhere 2 Promotes microservices 2 Small API 1 JSON Graph	Pros 75 Schemas defined by the requests made by the user 63 Will replace RESTful interfaces 62 The future of API's 49 The future of databases 12 Get many resources in a single request Cons 4 Hard to migrate from GraphQL to another technology 4 More code to type. 2 Takes longer to build compared to schemaless. 1 All the pros sound like NFT pitches 1 No support for caching

What are some alternatives to Falcor, GraphQL?

Postman

It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide.

Paw

Paw is a full-featured and beautifully designed Mac app that makes interaction with REST services delightful. Either you are an API maker or consumer, Paw helps you build HTTP requests, inspect the server's response and even generate client code.

Karate DSL

Combines API test-automation, mocks and performance-testing into a single, unified framework. The BDD syntax popularized by Cucumber is language-neutral, and easy for even non-programmers. Besides powerful JSON & XML assertions, you can run tests in parallel for speed - which is critical for HTTP API testing.

Appwrite

Appwrite's open-source platform lets you add Auth, DBs, Functions and Storage to your product and build any application at any scale, own your data, and use your preferred coding languages and tools.

Runscope

Keep tabs on all aspects of your API's performance with uptime monitoring, integration testing, logging and real-time monitoring.

Prisma

Prisma is an open-source database toolkit. It replaces traditional ORMs and makes database access easy with an auto-generated query builder for TypeScript & Node.js.

PostGraphile

Execute one command (or mount one Node.js middleware) and get an instant high-performance GraphQL API for your PostgreSQL database

Insomnia REST Client

Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux.

RAML

RESTful API Modeling Language (RAML) makes it easy to manage the whole API lifecycle from design to sharing. It's concise - you only write what you need to define - and reusable. It is machine readable API design that is actually human friendly.

OData

It is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. It helps you focus on your business logic while building RESTful APIs without having to worry about the various approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, etc.

Related Comparisons

Falcor vs GraphQL: What are the differences?

Data Fetching Model: Falcor utilizes a "path" concept to fetch data directly from a JSON-like graph structure, enabling users to request specific data using paths. In contrast, GraphQL uses a declarative data fetching model where clients can specify the exact data needed using queries.
Data Caching: Falcor has built-in caching mechanisms to help reduce network requests by storing fetched data locally, allowing for efficient data retrieval when needed. GraphQL does not have built-in caching mechanisms and relies on the client to manage caching strategies.
Server-Side Implementation: Falcor is typically server-centric, with most of the logic residing on the server to handle data fetching and manipulation. On the other hand, GraphQL puts more emphasis on the client-side, providing flexibility for clients to define their data requirements without server modifications.
Response Structure: Falcor typically returns complete JSON responses containing the requested data along with metadata, which can be tailored to fit specific use cases. In contrast, GraphQL responses mirror the shape of the query, providing precise data requested by the client without additional metadata clutter.
Batching Requests: Falcor allows for batching multiple requests into a single network call, enhancing efficiency and reducing overhead. In contrast, GraphQL inherently supports requesting multiple resources in a single query, minimizing network round trips for complex data requirements.
Type System: GraphQL enforces a strongly typed schema where clients must adhere to predefined types and structures, ensuring consistency and reliability in data fetching processes. Falcor, while providing schema-like capabilities with its JSON graph structure, does not enforce strict types on clients, offering more flexibility but potentially leading to data integrity issues.

In Summary, Falcor and GraphQL differ in their data fetching models, caching mechanisms, server-side implementation, response structures, request batching capabilities, and type system enforcement.

Falcor vs GraphQL

Overview