GraphQL Playground Reviews

gRPC Reviews

GraphQL Playground mentions (11)

• Exploring GraphiQL 2 Updates and New Features

  GraphiQL is a tool that was created to help developers explore GraphQL APIs, maintained by the GraphQL Foundation. But when GraphiQL became more and more popular, developers started to create additional GraphQL IDEs. A good example of this was GraphQL Playground, which quickly became the most popular GraphQL IDE. It was loosely based on GraphiQL, but had more features and a better UI. - Source: dev.to / over 1 year ago

• Why Is It So Important To Go To Meetups

  I went to a GraphQL meetup and they used the gql playground and a similar schema generator to what I was using, and it made me feel relevant. - Source: dev.to / about 2 years ago

• GraphQL subscriptions at scale with NATS

  Here, we'll create a simple GraphQL server and subscribe to a subject from our resolver. We'll use GraphQL playground to mock client side behavior. Once we're connected we'll use NATS CLI to send a payload to our subject and see the changes on the client. - Source: dev.to / over 2 years ago

• GraphQL vs REST in .NET Core

  Now we can consume created GraphQL API. In the GitHub Repo same functionality has been added with REST approach and GraphQL endpoint. Also widely used Swagger configured for Web API Endpoints as well as AltairUI added for GraphQL endpoint testing. Naturally, AltairUI it not a must for GraphQL, you can also use Swagger, GraphiQL, or GraphQL Playground. - Source: dev.to / over 2 years ago

• Creating GraphQL Api Using NestJS For Multiple Databases

  Navigate to http://localhost:3000/graphql. NestJS uses graphql playground by default. It's a lovely GraphQL IDE. We can check our schema here. - Source: dev.to / over 2 years ago

gRPC mentions (91)

• Text-based language processing enhanced with AI/ML

  Aside from the obvious differences in client library nomenclature and use of different credentials, API usage is fairly similar. Not visually obvious is that the older platform client library calls the REST versions of the GCP APIs whereas the newer product client libraries call the gRPC versions which generally perform better... Yet another reason why the product client libraries are always recommended. - Source: dev.to / 5 days ago

• Fastly and the Linux kernel

  The open source projects Fastly uses and the foundations we partner with are vital to Fastly’s mission and success. Here's an unscientific list of projects and organizations supported by the Linux Foundation that we use and love include: The Linux Kernel, Kubernetes, containerd, eBPF, Falco, OpenAPI Initiative, ESLint, Express, Fastify, Lodash, Mocha, Node.js, Prometheus, Jenkins, OpenTelemetry, Envoy, etcd, Helm,... - Source: dev.to / 11 days ago

• Best Practices for Building Microservices with NestJS

  Choose a consistent communication protocol for inter-service communication. Common protocols include HTTP, gRPC, and message brokers like RabbitMQ or Kafka. NestJS supports various communication strategies, allowing you to choose the one that best fits your needs. - Source: dev.to / 24 days ago

• Why Did Google Choose To Implement gRPC Using HTTP/2?

  gRPC is an open-source high-performance RPC framework developed by Google. The design goal of gRPC is to run in any environment, supporting pluggable load balancing, tracing, health checking, and authentication. It not only supports service calls within and across data centers but is also suitable for the last mile of distributed computing, connecting devices, mobile applications, and browsers to backend services.... - Source: dev.to / about 1 month ago

• Difference between GraphQL, REST, and gRPC

  And, gRPC is a high-performance, open-source protocol used for creating APIs. It uses Google's Protocol Buffers as a data format and provides support for streaming and bi-directional communication. - Source: dev.to / about 1 month ago