[kemenaran]

> APIs that don't follow standard responses

Interesting. In my experience the clean separation of layers in Ember-Data (network, serialization, models) make it quite suited to non-standard APIs. I found writing a custom (de-)serializer for a non-standard API to be relatively easy.

Care to elaborate on what were your issues precisely?

[hatsix]

Not OP, but it's possible to not write any ember-data code if a server implements json-api...

Otherwise, you have to write the same code that you have to write in other places... except that w/ Ember Data there are core patterns and its easy to add tests.

Writing Ember against an API that speaks json-api is a magical experience :-D

[steveklabnik]

So happy to hear JSON API is working that well for you :)

[joshdotsmith]

Also curious about this. For reasons that our team was personally against, we had to devote some serious upfront development work to building an integration with a WordPress backend and the rest of our Ember front-end (which consumed, thankfully, a JSON-API spec backend). We wrote custom adapter and serialization layers for this, which was trivial; the only exceptions to the ease of writing such code was when the WordPress developers would return bizarre status codes or missed root objects or some other such nonsense.