3 ms·
Related question: Does a REST API make sense for an internal interface? Or is the overhead prohibitive compared to a more specialized interface? (By internal i
by wozer 10y ago
Related question: Does a REST API make sense for an internal interface? Or is the overhead prohibitive compared to a more specialized interface?
(By internal interface I mean: an interface that is used only by the team that created it)
- blowski 10y agoMaybe. It adds a whole layer of complexity, but it might be worth it. Depends on your team's structure and relevant experience, and on the details of the project.
- rimantas 10y agoI'd argue that it removes complexity, not adds it.
- eecks 10y agoI think it's more maintainable and easier to test
- PeterisP 10y agoIt depends on the problem - if the particular interface is semantically suitable for REST, then there won't be any overhead and REST will just be a useful convention on how exactly you should represent it; and on the other hand if that particular interface needs are not suitable for REST then you probably should implement it with RPC, message queues or whatever other option better suits the problem instead of trying to mangle it into REST paradigm.