gRPC
prometheus
Our great sponsors
gRPC | prometheus | |
---|---|---|
200 | 374 | |
40,488 | 52,380 | |
1.2% | 1.5% | |
9.9 | 9.9 | |
7 days ago | about 6 hours ago | |
C++ | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gRPC
-
Reverse Engineering Protobuf Definitions from Compiled Binaries
Yes, grpc_cli tool uses essentially the same mechanism except implemented as a grpc service rather than as a stubby service. The basic principle of both is implementing the C++ proto library's DescriptorDatabase interface with cached recursive queries of (usually) the server's compiled in FileDescriptorProtos.
See also https://github.com/grpc/grpc/blob/master/doc/server-reflecti...
The primary difference between what grpc does and what stubby does is that grpc uses a stream to ensure that the reflection requests all go to the same server to avoid incompatible version skew and duplicate proto transmissions. With that said, in practice version skew is rarely a problem for grpc_cli style "issue a single RPC" usecases: even if requests do go to two or more different versions of a binary that might have incompatible proto graphs, it is very common for the request and response and RPC to all be in the same proto file so you only need to make one RPC in the first place unless you're using an extension mechanism like proto2 extensions or google.protobuf.Any.
-
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.
-
gRPC Name Resolution & Load Balancing on Kubernetes: Everything you need to know (and probably a bit more)
The loadBalancingConfig is what we use in order to decide which policy to go for (round_robin in this case). This JSON representation is based on a protobuf message, then why does the name resolver returns it in the JSON format? The main reason is that loadBalancingConfig is a oneof field inside the proto message and so it can not contain values unknown to the gRPC if used in the proto format. The JSON representation does not have this requirement so we can use a custom loadBalancingConfig .
-
Dart on the Server: Exploring Server-Side Dart Technologies in 2024
The Dart implementation of gRPC which puts mobile and HTTP/2 first. It's built and maintained by the Dart team. gRPC is a high-performance RPC (remote procedure call) framework that is optimized for efficient data transfer.
- Usando Spring Boot RestClient
-
How to Build & Deploy Scalable Microservices with NodeJS, TypeScript and Docker || A Comprehesive Guide
gRPC is a high-performance, open-source RPC (Remote Procedure Call) framework initially developed by Google. It uses Protocol Buffers for serialization and supports bidirectional streaming.
-
Actual SSH over HTTPS
In general, tunneling through HTTP2 turns out to be a great choice. There is a RPC protocol built on top of HTTP2: gRPC[1].
This is because HTTP2 is great at exploiting a TCP connection to transmit and receive multiple data structures concurrently - multiplexing.
There may not be a reason to use HTTP3 however, as QUIC already provides multiplexing.
I expect that in the future most communications will be over encrypted HTTP2 and QUIC simply because middleware creators can not resist to discriminate.
[1] <https://grpc.io>
-
SGSG (Svelte + Go + SQLite + gRPC) - open source application
gRPC
-
Level UP your RDBMS Productivity in GO
I have decided to use gRPC because it's a very simple protocol and it's very easy to use.
-
Create Production-Ready SDKs with Goa
Goa generates gRPC code for you. gRPC is an efficient alternative to plain HTTP, over which you can provide your API. It requires the use of protocol buffers, made by Google. Our repository already provides the protoc app for you, in completed_app/lib.
prometheus
-
Observability at KubeCon + CloudNativeCon Europe 2024 in Paris
Prometheus
-
4 facets of API monitoring you should implement
Prometheus: Open-source monitoring system. Often used together with Grafana.
-
Building an Observability Stack with Docker
After that, you will set up a metrics server container. It will use Prometheus.io, an open-source monitoring and alerting toolkit designed to collect, store, and query time series data, making it a tool for monitoring your systems' performance and health through metrics.
-
Root Cause Chronicles: Quivering Queue
Thankfully KEDA operator was already part of the cluster, and all Robin had to do was create a ScaledObject manifest targeting the Dispatch ScaleUp event, based on the rabbitmq_global_messages_received_total metric from Prometheus.
- Diagnósticos usando dotnet-monitor + prometheus + grafana
-
Prometheus Fundamentals (Lesson-01)
$ wget https://github.com/prometheus/prometheus/releases/download/v2.48.1/prometheus-2.48.1.linux-amd64.tar.gz
-
Start your server remotely
I build the Tasmota firmware for the S31's nightly, and expose the Prometheus endpoint so I can also monitor the current used by these devices in real time with the data pushed to Grafana. I have ~30 of them in my home/homelab, and servers, appliances, sump pump, fans, etc. are all monitored by my S31 fleet.
-
List of your reverse proxied services
Prometheus
-
PM2 module to monitoring node.js application with export to Prometheus and Grafana
In most cases, applications use the combination of Prometheus + Grafana, which allows collect data and display it in the form of graphs and also to set up alerts for changes in any metrics.
-
Exploring the OpenTelemetry Collector
Prometheus is one of the primary monitoring solutions. It works on a pull-based model: Prometheus scrapes compatible endpoints of your application(s) and stores them internally.
What are some alternatives?
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
metrics-server - Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.
Apache Thrift - Apache Thrift
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
skywalking - APM, Application Performance Monitoring System
Jolokia - JMX on Capsaicin
Telegraf - The plugin-driven server agent for collecting & reporting metrics.
JavaMelody - JavaMelody : monitoring of JavaEE applications
zeroRPC - zerorpc for python
Glowroot - Easy to use, very low overhead, Java APM
rpclib - rpclib is a modern C++ msgpack-RPC server and client library
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database