Timeline for Is it a bad choice to consume the REST API from the back-end too?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 16:19 | history | edited | Jonathan Eunice | CC BY-SA 3.0 |
correct typo
|
| Apr 12, 2017 at 0:36 | comment | added | RubberDuck | This is s great answer. If you keep your REST controllers thin and only responsible for "parse request, call business model class lib, return result", then it's perfectly reasonable to call that library directly. Just beware non-http related logic in your controllers. | |
| Nov 9, 2014 at 8:51 | vote | accept | seldon | ||
| Nov 8, 2014 at 20:44 | comment | added | seldon | Thank you for the answer! And yes, one of the main concerns is inefficiency and I am thinking about a way to abstract the access layer from the API implementation, so I can access it in a REST-fashion but directly from the code, thus eliminating all the overhead due to HTTP | |
| Nov 8, 2014 at 19:30 | history | answered | Jonathan Eunice | CC BY-SA 3.0 |