Blazer VS GraphQL

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 / 2 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: 10 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 / almost 2 years ago

GraphQL is a query language and runtime for APIs. It provides a flexible and efficient way for clients to request and retrieve specific data from a server using a single API endpoint. - Source: dev.to / 17 days ago

When you use technologies like GraphQL, it is trivial to derive TypeScript types. A GraphQL API is created by implementing a schema. Generating the TypeScript type definitions from this schema is simple, and you do not have to do any more work than just making the GraphQL API. This is one reason why I like GraphQL so much. - Source: dev.to / 25 days ago

REST and GraphQL have advantages, drawbacks, and use cases for different environments. REST is for simple logic and a more structured architecture, while GraphQL is for a more tailored response and flexible request. - Source: dev.to / about 1 month ago

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications. - Source: dev.to / about 1 month ago

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:. - Source: dev.to / 7 months ago