When to use REST?

O WHEN TO USE REST ? When designing web services , one of the most contentious issues is whether REST or SOAP should be used . In the following situations , REST services should be used : • Limited resources and bandwidth Because SOAP messages are heavier in content and consume far more bandwidth , REST should be used when network bandwidth is limited . • Statelessness If there is no need to keep information in a consistent state from one request to the next , REST should be used . If you need a proper information flow , where some information from one request needs to flow into another , SOAP is a better choice . We can use any online shopping site as an example . Typically , these sites require the user to first add items that must be purchased to a cart . To complete the purchase , all of the cart items are transferred to the payment page . This is an example of an application that would benefit from the state feature . The cart items ' state must be transferred to the payment page for further processing . Caching If a large number of requests must be cached , REST is the ideal solution . Clients may request the same resource multiple times at times . This may result in an increase in the number of requests sent to the server . The most frequently used query results can be saved in an intermediate location by implementing a cache . As a result , whenever a client requests a resource , it will first check the cache . If the resources are available , the process will not proceed to the server . As a result , caching can aid in reducing the number of trips to the web server . ● • Ease of ng - Coding REST Services and then implementing them is far easier than SOAP . So , if you need a quick win solution for web services , REST is the way to go . in www.newsdata.io