If your messaging lends itself to caching, it might very well fit with REST - which means http might be a good option. So it's not so much if you want to memor

If your messaging lends itself to caching, it might very well fit with REST - which means http might be a good option. So it's not so much if you want to memorize (cache), but if you can* (and/or should). I'm afraid I'm repeating myself - but I really whish people would read all of Fielding's thesis - it's got all kinds of reasonable architectures in it - even if it argues hypermedia/hypertext applications are well served by REST. https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm