4 ms·
Isn't this just "3.4.7 Remote Data Access (RDA)"[1] from Fielding's REST thesis[2] (where client means javascript+browser and server reads some-kind-of-wrapper-
by e12e 13y ago
Isn't this just "3.4.7 Remote Data Access (RDA)"[1] from Fielding's REST thesis[2] (where client means javascript+browser and server reads some-kind-of-wrapper-over-sql-or-nosql-so-that-quering-is-quite-simple?). I sometimes wonder if people haven't read that despite it being quite accessible, a fantastic introduction to architectural analysis and the hype of the Representional State Transfer acronym.
For those that have somehow missed it (is it really obscure?) -- the introduction alone is well worth the read, even if you don't care about the argument that leads up to REST being a good idea for an architecture for a hypertext application/system.
[1] https://www.ics.uci.edu/~fielding/pubs/dissertation/net_arch_styles.htm#sec_3_4_7 https://www.ics.uci.edu/~fielding/pubs/dissertation/net_arch...
[2] https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm
- auvrw 13y agothanks for the links. i hadn't read the paper. it seems like the design patterns book in that it's a good reference to, um, refer back to when looking at the latest "new" thing. going back to the parent comment, > I would love to learn more and avoid mistakes made during it's infancy. you'll probably want to look at zookeeper (or some system built on top of zookeeper like storm) if you expect the thing to grow into a large project with lots of services. and to the article, > Should all your applications use the same language? there are definitely reasons (library availability, runtime capabilities, the simple fact that you don't have to, and so on) not to use the same language, but i've found being able to refactor between applications very helpful.