3 ms·

Interesting, you use EdgeDB but not GraphQL instead of gRPC? I looked in to EdgeDB and GraphQL seems to be a big part of it. With gRPC and UI side of things I

Interesting, you use EdgeDB but not GraphQL instead of gRPC? I looked in to EdgeDB and GraphQL seems to be a big part of it. With gRPC and UI side of things I think there is some issues, like no standard way to handle validation errors (e.g. email field has incorrect value), so everyone reinvents the wheel. Edit: Also this EdgeQL seems like nice way to interact also from UI. gRPC is not mentioned in the EdgeDB at all.

divan 5y ago
Yes, EdgeDB has native GraphQL layer, but I'm not sure I need it. I still want to have a precise control over the the communication, memory usage and DB performance, plus as soon as you add new functionality on top of basic CRUD, it's not enough to talk directly from frontend to DB anymore. I'm not sure if those are my biases, but I still try to keep things into separated layers (i.e. DB, backend, communication and frontend), so I can change them without affecting the overall design too much.