Apollo DataSource REST vs Hasura

Developers should use Apollo DataSource REST when building GraphQL APIs with Apollo Server that need to aggregate data from multiple RESTful services, as it reduces boilerplate code and improves performance through built-in caching meets developers should use hasura when they need to rapidly prototype or build applications with graphql apis, especially for projects requiring real-time features like live queries or subscriptions. Here's our take.

Apollo DataSource REST

Nice Pick

Developers should use Apollo DataSource REST when building GraphQL APIs with Apollo Server that need to aggregate data from multiple RESTful services, as it reduces boilerplate code and improves performance through built-in caching

Pros

• It's particularly useful in microservices architectures or when migrating from REST to GraphQL, enabling gradual adoption by wrapping existing REST endpoints
• Related to: apollo-server, graphql

Cons

• Specific tradeoffs depend on your use case

Hasura

Developers should use Hasura when they need to rapidly prototype or build applications with GraphQL APIs, especially for projects requiring real-time features like live queries or subscriptions

Pros

• It's ideal for startups, MVPs, or teams looking to accelerate development by leveraging existing PostgreSQL databases without extensive backend coding
• Related to: graphql, postgresql

Cons

• Specific tradeoffs depend on your use case

The Verdict

These tools serve different purposes. Apollo DataSource REST is a library while Hasura is a platform. We picked Apollo DataSource REST based on overall popularity, but your choice depends on what you're building.

The Bottom Line

Apollo DataSource REST wins

Based on overall popularity. Apollo DataSource REST is more widely used, but Hasura excels in its own space.

Related Comparisons