feathers / graphql using REST / Sockets about socketio HOT 8 CLOSED

This does not address your question but its related items you might want to be aware of.

(1) We have a Feathers GraphQL adapter ready. The docs have to be written before its released. With it you can define resolvers on the server and pass queries from the client, the basic stuff. Its focus is on Query requests.

The adapter however can also use the schema to generate code for your resolvers. The generated code works with either SQL and non-SQL databases. It uses dataloaders for non-SQL databases for high performance; join-monster for SQL databases.

(2) We are just about to release a new populating hook fastJoin which is heavily inspired by GraphQL. Its very fast. The docs are in progress. https://feathers-plus.github.io/v1/feathers-hooks-common/guide.html

from socketio.

Interesting to learn from this, but I have no clue where that adapter is ?
Maybe needed to wait a bit ?
Websockets too ?

This is a lot of questions but this looks like exciting :)

from socketio.

from socketio.

I'm still open to explanations / suggestions about implementing websocket subscriptions.

from socketio.

Any word on the release? I'm happy to dig through the code to figure it out without docs if the adapter is ready.

from socketio.

I'm working on reducing what people would need to learn to implement GraphQL. Basically, automating the schemas and resolvers somewhat. The previous docs are complete but a bit daunting.

Will you actually use it? I'm asking because more people have agreed to use it than have actually done so. And each one costs me $7, LOL.

I'm presenly focused on Query. How important is Mutation and Subscriptions to you? (As an aside, I think I would prefer using Feathers for mutations and real-time.)

from socketio.

It's hard to tell ahead of time without seeing the implementation. I'm happy to pay the $7 to take a look at it though. Where's that cost coming from?

I'm starting a new project and would like to use GraphQL but using Feathers as a base gives me the ability to include things like authentication without much overhead.

Feathers also opens up both REST and Socket.io which give us a fallback for existing application integrations.

This part of the project is only the server side for me. I'm using Apollo on the client side with this boilerplate: https://github.com/react-boilerplate/react-boilerplate

Is this a new GraphQL implementation or an Apollo GraphQL connector for Feathers?

from socketio.

I don't think it uses any Apollo utils and certainly not Apollo itself.

I sent you a link. There are 3 examples: non-SQL, SQL, both.

I'm adding a graphql option to the generator. That'll make it easier to use GraphQL with existing Feathers service. I can send you a link to that in about a week.

from socketio.