3 ms·
REST is working with documents only, there is just no way to DO something (more than C/R/U/D), you need to map actions to some C/R/U/D and so on. That's a serio
by sigsergv 11y ago
REST is working with documents only, there is just no way to DO something (more than C/R/U/D), you need to map actions to some C/R/U/D and so on. That's a serious practical limitation.
- andrewstuart2 11y agoMore accurately, REST involves only transferring state. The tricky (but worthwhile IMO) part is modeling what you want to happen as the state transition or set of state transitions that it is.
- sigsergv 11y agoYes, and also REST does not eliminate real business concepts so you need constantly “convert” business/domain operations to REST CRUD, and this process takes too much resources. You can change business/domain of course, but I'm not sure it's suitable for everyone (API is just one of components among others). REST is conceptually really hard and requires almost military discipline.
- oldmanjay 11y agoI'm amazed that you feel this way, because my experience is completely the opposite. Banging out the REST API portion of things is usually a mechanical wrapper around some business process in the systems I have been creating. CRUD comes into play with entity manipulation, of course, but that's only one facet and in my current case, not even the dominant one. In fact, I don't even know why you'd think you have to map business processes to CRUD at all. It almost seems like you have some religous belief about what REST actually is, much like how the article talks about "de facto" standards that are nothing of the sort. I suppose you have strange requirements or design impositions that make your life difficult, but I caution you against believing that your use case is universal because in my very real experience, none of your opinions are supportable.