I try to avoid these tools wherever possible, given the choice I'd always go for tools like Blazer. https://github.com/ankane/blazer No such luck in my current role, Looker and PowerBI are both in use by different bits of the org and nobody has the ability to delve into the underlying figures. - Source: Hacker News / 3 months ago

As u/jaxn said you could use Blazer for this kind of thing. I would also look into materialized views or custom tables and a scheduled job that calculates the metrics they care about. That will take you a long way. Eventually you can use something like Metabase but I would put that off for as long as possible as it's really expensive and pretty involved. Source: 11 months ago

And it's Open Source: https://github.com/evidence-dev/evidence if you are into the Ruby on Rails world. It's super solid, and it's been an indispensable tool integrated to all my projects. - Source: Hacker News / about 1 year ago

I use Ahoy too, but I don't have very good visibility into the data. I should spend more time building queries and creating charts. I should probably set up blazer as well: https://github.com/ankane/blazer. - Source: Hacker News / almost 2 years ago

The Blazer gem provides a nice way to analyze the results easily. It is simple to install and allows SQL queries to run against tables. The query here shows that the candidate implementation is significantly faster than the original. - Source: dev.to / about 2 years ago

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 / 3 months ago

Services in general communicate via Thrift (and in some cases HTTP). Source: about 1 year ago

Protocol Buffers is the most popular one, but there are many others such as Apache Thrift and my own Typical. Source: over 1 year ago

RPC is not strictly OO, but you can think of RPC calls like method calls. In general it will reflect your interface design and doesn't have to be top-down, although a good project usually will look that way. A good contrast to REST where you use POST/PUT/GET/DELETE pattern on resources where as a procedure call could be a lot more flexible and potentially lighter weight. Think of it like defining methods in code... Source: over 1 year ago

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto. - Source: dev.to / over 1 year ago