Choosing between REST and GraphQL depends on your specific use case and development requirements.

REST

The following are worthy knowing about REST:

• It relies on standard HTTP methods like GET, POST, PUT, DELETE to perform CRUD operations.
• It is excellent for simple, uniform interfaces between separate services or applications.
• Caching strategies are straightforward to implement.
• It can require multiple API calls to fetch related data, leading to chatty interfaces.

GraphQL

The following are to be consider worthy knowing about GraphQL:

• It provides a single endpoint and lets consumers precisely query for the data they need.
• The clients specify the exact fields required in nested queries, and the server returns optimized payloads containing just those fields.
• It supports _Mutations _for modifying data and subscriptions for real-time notifications.
• It is great for aggregating data from multiple sources and works well with complex frontends that have rapidly changing data needs.
• It shifts complexity to clients and can enable abusive and expensive queries without proper safeguards.
• Caching strategies are less straightforward compared to REST.

Nevertheless, the best choice depends on the application architecture and team preferences.** GraphQL** fits better for fluid or intricate frontend requirements, while REST suits applications needing simple consistent interfaces.

Use Rest for:

1. Simple and consistent interfaces
2. Caching Simplicity

Use GraphQL for:

1. Flexible frontend reuirements
2. Aggregating Data from multiple sources

Conclusively, neither one is a silver bullet but evaluating tradeoffs and limitations is of great significance. Both REEST and GraphQL are solid options for exposing data and powering modern applications.

Carefully analyzing requirements rather than defaulting to one or the other is key to picking the right API approach.