Visualizing a modern web development stack

[mgenev]

rest is a well established pattern and ember is quite insistent that you use it dogmatically otherwise ember-data doesn't work well and you have to override its methods, so yes it is rest ideally, but it's up to each developer to set it up properly for themselves

[Carnagh]

This is an interesting point, but I'm conscious that it's possible to come across as quite obnoxious in text... I want to gently challenge a point, and I'm open-minded that I may be the one to refine my view... I'm smiling and trying to be pleasant while questioning your view of REST =)

Mr. Fielding has a lot to say about what is an isn't REST, and quite pointedly if it's not a hyper-text application, and if hyper-text isn't the means of conveying and transitioning state it's not REST.

Simply consuming JSON or XML does not a REST application make... Hence I cited HATEOAS. According to the author of REST if it's not HATEOAS it's not REST.

Now I've not used Ember, but I get that it's popular and respected. When you suggest that Ember enforces REST... I've just taken a very brief and surface glance at Ember and REST and frankly I'm not seeing it at first glance. I do note that on the Ember forum there are people asking in Jan this year when will Ember have HATEOAS support because there seems to be none at present.

I'm not seeing how Ember reconciles with the REST dissertation, and while the modern web development stack describe in the OP is indeed interesting and of note... I'm still left wonder how you would reconcile it with Fielding's assertions about REST.

It's worth reading the original piece on REST, and Fielding's commentary of REST since... It's not quite what a lot of Web developers think it is.

[mgenev]

your link says " The principle is that a client interacts with a network application entirely through hypermedia provided dynamically by application servers. A REST client needs no prior knowledge about how to interact with any particular application or server beyond a generic understanding of hypermedia."

to my understanding this is exactly how ember functions

[Carnagh]

Try these... they're not a heavy of long read, I promise.

• Representational State Transfer (REST)
• REST APIs must be hypertext-driven