Which scenario best illustrates REST's suitability for extensive back-and-forth messaging?

Which scenario best illustrates REST's suitability for extensive back-and-forth messaging?

• A. A static homepage load
• B. A batch file transfer that runs overnight
• C. A mobile app requiring a lot of back-and-forth messaging
• D. A real-time streaming service using persistent connections

Answer: (C)

REST works best when interactions are a series of discrete, stateless HTTP requests. This model fits a mobile app that requires a lot of back-and-forth messaging because each user action—fetching data, submitting updates, creating items—can be handled as its own independent request and response. The server doesn’t have to maintain session state between calls, which simplifies scaling and makes caching GET responses effective, helping keep the app responsive across variable networks. In contrast, real-time streaming relies on persistent, bidirectional connections, which REST doesn’t natively provide and would be less efficient for continuous, low-latency messaging. Static homepage loading involves minimal back-and-forth, and an overnight batch transfer is a scheduled, non-interactive process, so they don’t illustrate the interactive, request-driven pattern REST excels at.

REST works best when interactions are a series of discrete, stateless HTTP requests. This model fits a mobile app that requires a lot of back-and-forth messaging because each user action—fetching data, submitting updates, creating items—can be handled as its own independent request and response. The server doesn’t have to maintain session state between calls, which simplifies scaling and makes caching GET responses effective, helping keep the app responsive across variable networks. In contrast, real-time streaming relies on persistent, bidirectional connections, which REST doesn’t natively provide and would be less efficient for continuous, low-latency messaging. Static homepage loading involves minimal back-and-forth, and an overnight batch transfer is a scheduled, non-interactive process, so they don’t illustrate the interactive, request-driven pattern REST excels at.