GraphQL VS Due

• Efficient Data Retrieval
  GraphQL allows clients to request only the data they need, reducing the amount of data transferred over the network and improving performance.
• Strongly Typed Schema
  GraphQL uses a strongly typed schema to define the capabilities of an API, providing clear and explicit API contracts and enabling better tooling support.
• Single Endpoint
  GraphQL operates through a single endpoint, unlike REST APIs which require multiple endpoints. This simplifies the server architecture and makes it easier to manage.
• Introspection
  GraphQL allows clients to query the schema for details about the available types and operations, which facilitates the development of powerful developer tools and IDE integrations.
• Declarative Data Fetching
  Clients can specify the shape of the response data declaratively, which enhances flexibility and ensures that the client and server logic are decoupled.
• Versionless
  Because clients specify exactly what data they need, there is no need to create different versions of an API when making changes. This helps in maintaining backward compatibility.
• Increased Responsiveness
  GraphQL can batch multiple requests into a single query, reducing the latency and improving the responsiveness of applications.

Possible disadvantages

• Complexity
  The setup and maintenance of a GraphQL server can be complex. Developers need to define the schema precisely and handle resolvers, which can be more complicated than designing REST endpoints.
• Over-fetching Risk
  Though designed to mitigate over-fetching, poorly designed GraphQL queries can lead to the server needing to fetch more data than necessary, causing performance issues.
• Caching Challenges
  Caching in GraphQL is more challenging than in REST, since different queries can change the shape and size of the response data, making traditional caching mechanisms less effective.
• Learning Curve
  GraphQL has a steeper learning curve compared to RESTful APIs because it introduces new concepts such as schemas, types, and resolvers which developers need to understand thoroughly.
• Complex Rate Limiting
  Implementing rate limiting is more complex with GraphQL than with REST. Since a single query can potentially request a large amount of data, simple per-endpoint rate limiting strategies are not effective.
• Security Risks
  GraphQL's flexibility can introduce security risks. For example, improperly managed schemas could expose sensitive information, and complex queries can lead to denial-of-service attacks.
• Overhead on Small Applications
  For smaller applications with simpler use cases, the overhead introduced by setting up and maintaining a GraphQL server may not be justified compared to a straightforward REST API.

• Simple User Interface
  Due features a straightforward, minimalist user interface that's easy to navigate, making it suitable for all types of users, including those who are not very tech-savvy.
• Effective Time Management
  The app is designed to help users manage their time more effectively by setting reminders and timers that are hard to ignore, ensuring tasks and deadlines are met on time.
• Cross-Device Syncing
  Due allows users to sync their reminders across multiple devices, including phones, tablets, and computers, providing flexibility and accessibility.
• Customizable Reminders
  Users can set up recurring reminders with customizable time intervals, which is useful for managing routine tasks and events.

Possible disadvantages

• Limited Free Version
  The free version of Due has limited features, which may require users to purchase the app or subscriptions to access the full range of functionalities.
• Not Suitable for Complex Task Management
  Due is primarily a reminder app and lacks advanced task management features such as project tracking or collaboration tools, which may not be suitable for users needing these capabilities.
• Manual Entry Requirement
  Tasks and reminders need to be entered manually, which can be time-consuming for users with many tasks or complex schedules.
• Cost
  Some users may find the cost of the app or in-app purchases to be high compared to other apps offering similar features.

REST vs. GraphQL: Critical Look

More videos

Due Date movie review

More videos

• API Development: How to Transition to Modern APIs

  GraphQL is a query language combined with a server-side runtime. It was created by Facebook in 2012, and soon after, they released the specification to the public and made a NodeJS implementation open source. - Source: dev.to / 6 months ago

• Readings in Database Systems (5th Edition)

  Definitely they should include D4M and GraphQL [1],[2]. Not only D4M can cater for structured relational data, it also suitable for sparse data in spreadsheet, matrices and graph. It's essentially a generalization of SQL but for all... - Source: Hacker News / 10 months ago

• Why GraphQL Is Gaining Adoption

  GraphQL is becoming a popular choice, making development easier. - Source: dev.to / about 1 year ago

View more

Tracking Due since Mar 2021.