<p>We are developing a middleware SDK, both in C++ and Java to be used as a library/DLL by, for example, game developers, animation software developers, Avatar developers to enhance their products.</p>

<p>Having created a typical API using specific calls for specific functions I am considering simplifying the API by using a REST type API (GET, PUT, POST, DELETE) or CRUD type (CREATE, READ, UPDATE, DELETE) interface.</p>

<p>This would work in a similar way to a client-server type REST API where there are only 4 possible API calls but these can take flexible parameters.</p>

<p>This seems to have the benefit of making the API stable in that new calls are not being added and old calls are not being removed. So a consumer of this API need not worry about having to recompile and change their code to suit any updates to our middleware.</p>

<p>The overhead is that there is an extra layer of redirection in the middleware controller to route API calls and the developer needs to know what parameters are available for each REST call (supplied of course).</p>

<p>I have not so far seen this system used outside of web type client server applications so my question is this: Is this a feasible idea?</p>

<p>I am thinking in terms of its efficiency as well as if for example a game developer would find it easy to use.</p>

[{'answer_id': 62683, 'author': 'Avi Flax', 'author_id': 7012, 'author_profile': 'https://Stackoverflow.com/users/7012', 'pm_score': 2, 'selected': False, 'text': "<p>Yes, this is a feasible idea. But I'm not sure the benefits would justify the costs. REST is best applied to a networked application scenario, oriented around requests and responses. While there are definite learning curve advantages to a uniform interface, those advantages can be present in almost any well-designed API which provides reasonably abstract procedures.</p>\n\n<p>You also expressed concern for whether a game developer would find a RESTful API easy to use. I'd be dubious. I've implemented many RESTful web services, and helped many developers get up to speed both building them and using them, and the conceptual leap required to grasp REST can be substantial for someone who has been steeped in procedural APIs for years. I'd think that game developers in particular would be very strongly connected to procedural APIs, to the point that attempting to adopt a different paradigm, whatever its benefits, might prove extremely difficult.</p>\n"}, {'answer_id': 1172147, 'author': 'aehlke', 'author_id': 89373, 'author_profile': 'https://Stackoverflow.com/users/89373', 'pm_score': 1, 'selected': False, 'text': "<p>Remember that REST is not specific to HTTP, and does not rely on just the 4 HTTP verbs. The verbs you have and can use depend on what protocol you're using.</p>\n"}]
['https://Stackoverflow.com/questions/62513', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/6775/']