# The Discourse API in GraphQL

**URL:** <https://meta.discourse.org/t/the-discourse-api-in-graphql/41183>\
**Category:** Development\
**Created:** [17 Marzo 2016, 9:24am UTC](https://meta.discourse.org/t/the-discourse-api-in-graphql/41183 "2016-03-17T09:24:22Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![sashko](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sashko/32/52315_2.png) [@sashko](https://meta.discourse.org/u/sashko)\
**Post date:** [17 Marzo 2016, 8:07pm UTC](https://meta.discourse.org/t/the-discourse-api-in-graphql/41183/13 "2016-03-17T20:07:35Z")

</div>

> [@Cortrah](#):
>
> I think that the biggest problems graphql will face are similar, crafting the schemas in particular, then authentication and authorization and finally the simple but necessary mapping of the different server side language conventions to javascript. If I’m right the graphql structure makes it so that cycles are not a problem, is that right?

Yep, I think this is spot on. But it’s important to separate GraphQL from JavaScript - there happen to be a lot of libraries that combine the two, but GraphQL by itself is independent of any specific implementation or transport, which is very important for people who aren’t interested in writing JavaScript at all (for example, native mobile app developers with a Rails backend).

> [@Cortrah](#):
>
> I’ll be following what you do here for sure.

I’m excited to learn more and I’ll share it as I do!

---

_[View the full topic](https://meta.discourse.org/t/the-discourse-api-in-graphql/41183)._