Let's Learn GraphQL

by arunoda • 11 years ago

166 34 11 years ago

clessg2• 11 years ago

Looks great, thanks for this! Back when I worked with Meteor, Arunoda's work was exceptionally helpful.

The homepage seems to be a bit confusing, I think. You don't have to sign up to read some of the content. There is a small link below the large button: https://learngraphql.com/basics/introduction.

Correction: As sync pointed out, you still need to sign up to access the full content.

sync• 11 years ago

You still have to sign up for the 'Start Lesson' button at the bottom of every page.

clessg2• 11 years ago

Ah, that's a bit of a shame.

samstave• 11 years ago

I signed up on mobile (iOS) and it went into a loop

sgdesign• 11 years ago

Awesome to see the Kadira team branching out beyond Meteor-only content, can't wait to check this out!

davidwparker• 11 years ago

Looks interesting. Question: why do I need to sign in with my Github account?

arunoda6• 11 years ago

It's an online course, you need to do some tasks in each lesson. And you get points.

That's why you need to login with GitHub. See more on this: https://news.ycombinator.com/item?id=10384683

octref2• 11 years ago

Don't know why people would downvote this. The permission this site is asking is only email address associated with Github. As someone who is always logged in with Github, this saves me from creating another account associated with my email address.

qnaal• 11 years ago

that people would defend having to log into a social media account to read a tutorial on a database language made me physically ill

I had to swallow it (just bile)

brentvatne• 11 years ago

Looks fantastic, thanks! FYI I shared this in Slack and the preview showed up like as "Learn How to Build Fast and Efficient Meteor Apps" - screenshot: http://url.brentvatne.ca/VYvi.png

arunoda6• 11 years ago

Good call. Working on it :)

dsyko• 11 years ago

The team at Kadira is great at diving into technical subjects and making fun and easy to follow learning materials. I loved Bullet Proof Meteor, I'm looking forward to learning GrapgQL through this new course.

curiousjorge• 11 years ago

what use case is there for graphql? and what does meteor have to do with it?

arunoda6• 11 years ago

GraphQL basically allows to build your backend as a well defined API. Then, you can query it from anywhere. It has a good query language and some nice tools like GraphiQL - https://github.com/graphql/graphiql

Meteor is a full stack. It has no direct relationship(or cannot compare with) GraphQL. Meteor also a realtime framework, but GraphQL does not address realtime aspects (yet).

lobo_tuerto• 11 years ago

How does this compare to Falcor? Can they be used together or ar they competing technologies?

arunoda6• 11 years ago

Falcor is based on top of REST. It's core is on top of the client side.

GraphQL is different and trying focus on the API end. (You can think it's trying to replace REST). GraphQL's client side part it Relay for now. It's somewhat complex compared with Falcor. But, I believe we can have a easy to use React independent client for GraphQL.

tuyguntn• 11 years ago

Sorry for my ignorance about the project, GraphQL looks awesome in terms of flexibility while developing and saving network traffic, but I have a question related to how API backend will work with GraphQL.

If storage was some kind of NoSQL and stores everything as one huge JSON, then we can filter out data while retrieving, but what would happen if data storage is RDBMS? Are we going to do multiple joins to retrieve data?

seems GraphQL work really well with graph databases, but if you have 2-3nesting in GraphQL query, then you need to do multiple big joins on the server side

tbrock• 11 years ago

Facebook made it, so even though they are using an RDBMS they aren't doing any joins. They use MySQL just as you would a nosql datastore in that to "join" data they are doing multiple queries and stitching the results together manually.

lojack• 11 years ago

Yes, you could end up with multiple big joins. The advantage is that you're at least only doing a single query for those joins. What would be worse is performing joins on the client and doing three separate queries to get the data you need.

Also, keep in mind that this is a query language and not an API spec. If you want to allow clients to perform massive joins then GraphQL will facilitate that, but that's your decision to make. Ultimately you still need to decide what clients can and can not query.

tarex• 11 years ago

many many thanks , its really awesome .

Let's Learn GraphQL

Related Stories