5 ms·

Graphql won the race for me. Grpc is no longer relevant. Too many hurdles, no proper to and from Web support. You have to use some 3rd party non free service.

• deleted 2y ago
  [deleted]
• nicce 2y ago
  Aren’t their usecases completely different?
  • pensatoio 2y ago
    Yes. The use cases are very different, as far as these things go. To say otherwise is borderline misinformation. You can build services internally with gRPC and serve a public graphQL API that aggregates them.
    • lakomen 2y ago
      That's just a distributed monolith and you shouldn't do that.
      • pensatoio 2y ago
        Haha. No...it's just a _distributed system_. One with firm, precisely-defined boundaries around each horizontally scaled sub-system.
  • lakomen 2y ago
    Not at all.
  • _cenw 2y ago
    Intersects quite heavily if you're defining a schema for your API
  • lmm 2y ago
    No, they're both possible choices for your basic client-server communication layer that you build everything else on. (I mean, technically gRPC rather than protobuf, but protobuf is the biggest part of gRPC).
  • revskill 2y ago
    What are differences ?