# I like Ember a lot, But I'm Worried **URL:** \ **Category:** Uncategorized\ **Created:** [July 5, 2018, 10:04pm UTC](https://discuss.emberjs.com/t/i-like-ember-a-lot-but-im-worried/15081 "2018-07-05T22:04:03Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![jelhan](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/jelhan/32/16917_2.png) [@jelhan](https://discuss.emberjs.com/u/jelhan)\ **Post date:** [July 6, 2018, 12:31pm UTC](https://discuss.emberjs.com/t/i-like-ember-a-lot-but-im-worried/15081/6 "2018-07-06T12:31:16Z")
> [@Mofungo](#): > > Great to know that I can just wait till the API mess is under control to start using it. You could also start using it right now. For endpoints which are already implementing JSON:API go with the defaults. If the endpoint is already RESTful customize Adapter and Serializer to match the current implementation. If it’s not yet RESTful, you may be still able to customize the Adapter and Serializer to match it. There is not restriction preventing you, to implement a Adapter which is using `POST` to fetch records. If this doesn’t work out for some endpoints, you could use `fetch` and push the record to store manually - or if you don’t need them in store (e.g. they don’t have a relationship to any other object in store), just go with it. This would allow you a smooth transition. Also have in mind that endpoints which do not represent entities but actions for example, `fetch` is mostly a better solution than fighting ember-data. Also have a look at [this discussion](https://discuss.emberjs.com/t/when-to-add-ember-data/15050/9). --- _[View the full topic](https://discuss.emberjs.com/t/i-like-ember-a-lot-but-im-worried/15081)._