Ember Design/Best Practices for Large Scale Projects

At least on the backend / Ember data side, The most valuable guide I’ve found is this transition page. It shows what changed in version 1.0, but there are so many examples that it got me up to speed on how to handle things.

They’re trying to make all APIs like this: http://jsonapi.org/. I’ve used several of the things on their examples page in projects and it works well. I don’t know if there’s a Java library so you might have do more yourself, but at least you know what Ember Data likes most. Specifically,

  • instead of nesting a list of child objects, just list their IDs, or call to get them separately

  • the more things you can get by ID instead of a special query, the less you’ll curse