The backend server is not just a simple CRUD, it is more like a CPU, as a processing center to coordinate various services, CRUD is just its tool.
Perhaps it is unnecessary for small applications and can be implemented using serverless, but it is essential for large applications. At least I haven’t heard of any large applications without back-end servers.
I understand what you said, this may represent a certain trend in the future. But it is still out of reach for me. It cannot replace all scenarios, especially large applications. I still need the back-end server as the processing center for coordinating various services.
I’m building a complex e-commerce application. I don’t have the infrastructure like serverless, and serverless can’t solve the problems we want to deal with either. I still need backend server. And for us, completely exposing the database and back-end logic to the insecure web or app is unacceptable.
Yeah. I am using juniper to build a graphql backend server.
But I encountered some difficulties. I don’t know how to convert graphql request from client to dgraph graphql request.
If it is neo4j, it provides a client library to deal with this problem, but dgraph does not have such a tool.
Below is an example of neo4j:
import { neo4jgraphql } from 'neo4j-graphql-js';
const resolvers = {
Query: {
Movie(object, params, ctx, resolveInfo) {
// Convert the graphql request from the client to the graphql request of neo4j.
return neo4jgraphql(object, params, ctx, resolveInfo);
}
}
};
If dgraph can also provide such a tool, then the problem becomes very simple, so that it will be easy to use dgraph’s graphql API on the graphql server.