4 ms·
I've just heard about 'API backend' and consumers (Web, Mobile, etc) and it makes a lot of sense to me on paper. The engineer in me foams at the mouth to dive i
by sergiotapia 13y ago
I've just heard about 'API backend' and consumers (Web, Mobile, etc) and it makes a lot of sense to me on paper. The engineer in me foams at the mouth to dive into this.
I just haven't had the time or right project to really use it. For example, in one of my pet projects[0] I could write an API data store and easily consume it client side or in my planned mobile applications. IT MAKES SENSE!
Does this architecture have an official name? I would love to learn more and avoid mistakes made during it's infancy.
[0] - http://www.smitecamp.com http://www.smitecamp.com
- auvrw 13y ago> Does this architecture have an official name? the article is describing a "service oriented architecture," i think.
- meowface 13y ago"Client agnostic" (I may have just made this term up, not sure) & service oriented architecture would probably be the most accurate descriptions. This really isn't anything new though. Many applications have been moving in this direction since 2008 and on. Mobile apps and heavy JS frameworks like Ember and Angular have made it even more prominent.
- e12e 13y agoIsn'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.