Skip to main content


How to Build a REST Implementation that Scales Better Than SMPP


1 comment

  • Avatar

    At a more enterprise level, consider making use of a queueing framework that will allow you to accept a large volume of requests quickly, and deal with them as fast as your application is able to.

    Typically, consumer of the API will expect some functional acknowledgment. Are you suggesting to delegate to a queue and "ack" the call back to consumer (without actually waiting for the queued task to complete execution)? This design may break functional requirement (e.g. returning an ID of a resource pushed by a POST request). How do you recommend managing this type of scenarios?


Please sign in to leave a comment.