Facade server for different service from different endpoints.
Only have to define mutators, querys, types in the schema.graphqls file and then implement the Resolvers:
GraphQLMutationResolver, GraphQLQueryResolver interfaces.
And if you want services wraps that invoke external services from other domain.
Inspired by micro services architecture
My purpose is to eliminate the service layers and only implement mutator and query resolvers.
This was based on repo code.
Graphql Java example for beginners The purpose is to eliminate the service layers and only implement mutator and query resolvers. Without spring-controllers that expose services only types and mutators.
IDEAS:
- Customize the server console
- Edit the graphql schemas.
- Recompile the graphql schemas.
- Upload new graphql schemes.
- Upload new mutators resolver from jar.
=======
Facade server for different service from different endpoints.
Only have to define mutators, querys, types in the schema.graphqls file and then implement the Resolvers:
GraphQLMutationResolver, GraphQLQueryResolver interfaces.
And if you want services wraps that invoke external services from other domain.
Inspired by micro services architecture
My purpose is to eliminate the service layers and only implement mutator and query resolvers.
This was based on repo code.
Graphql Java example for beginners The purpose is to eliminate the service layers and only implement mutator and query resolvers. Without spring-controllers that expose services only types and mutators.
IDEAS:
- Customize the server console
- Edit the graphql schemas.
- Recompile the graphql schemas.
- Upload new graphql schemes.
- Upload new mutators resolver from jar.
443c392d1fd8eef66eae26448fc8048a5105ecdc