ZeroMQ Reviews

gRPC Reviews

ZeroMQ mentions (35)

• Omegle is Gone, What Will Fill It's Gap?

  In this post from 2011, the creator of Omegle, Leif Brooks, explains what technology is used, including Python and a library called gevent for the backend. On top of that, Adobe Cirrus is used for streaming video. Though this post was 12 years ago, it is valuable to know what a web application like Omegle requires. A modern library that may provide some functionality for a text chat at a minimum may be... Source: 7 months ago

• Video Streaming at Scale with Kubernetes and RabbitMQ

  They might be thinking of something like ZeroMQ, which is pretty well liked: https://zeromq.org/ That said, I wouldn't call RabbitMQ that heavyweight myself, at least when compared to something like Apache Kafka. - Source: Hacker News / 8 months ago

• learn by doing vs learn by course?

  If you want to learn message passing in an environment you're familiar with, you should check out ZeroMQ. It's a C++ lib for socket abstraction, it's immensely useful in distributed systems, it can also do in-process message passing, and it's got bindings/ports for C and Rust. Source: about 1 year ago

• Shipping large ML models with electron

  Inspired by the IDE language server protocol, I created an API interface between the electron and the Python ML interface. ZeroMQ turned out be an invaluable resource as a fast and lightweight messaging queue between the two. - Source: dev.to / about 1 year ago

• how to display constantly changing data from a database in real time

  If you really need it live, like for a chat or auctions you can use https://zeromq.org/ over websockets. Source: over 1 year ago

gRPC mentions (89)

• 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 / 10 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 / 23 days 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

• Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard

  gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle. - Source: dev.to / 2 months ago

• Delving Deeper: Enriching Microservices with Golang with CloudWeGo

  While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / 4 months ago