Software Alternatives & Reviews

ProxySQL VS GraphQL

Compare ProxySQL VS GraphQL and see what are their differences

ProxySQL logo ProxySQL

ProxySQL: high-performance, GPL licensed MySQL proxy. It supports hundreds of thousands of concurrent connections and can be multiplexed to hundreds of servers.

GraphQL logo GraphQL

GraphQL is a data query language and runtime to request and deliver data to mobile and web apps.
  • ProxySQL Landing page
    Landing page //
    2023-05-23
  • GraphQL Landing page
    Landing page //
    2023-08-01

ProxySQL videos

#ProxySQL Use Case Scenarios - #ProxySQL #Database Tutorial - René Cannaò - #Percona Live 2017

More videos:

  • Review - ProxySQL Use Case Scenarios / Alkin Tezuysal (Percona)
  • Review - Inexpensive Datamasking for MySQL with ProxySQL - data anonymization for developers

GraphQL videos

REST vs. GraphQL: Critical Look

More videos:

  • Review - REST vs GraphQL - What's the best kind of API?
  • Review - What Is GraphQL?

Category Popularity

0-100% (relative to ProxySQL and GraphQL)
MySQL Tools
100 100%
0% 0
Developer Tools
0 0%
100% 100
Databases
100 100%
0% 0
Javascript UI Libraries
0 0%
100% 100

User comments

Share your experience with using ProxySQL and GraphQL. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, GraphQL seems to be a lot more popular than ProxySQL. While we know about 223 links to GraphQL, we've tracked only 10 mentions of ProxySQL. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

ProxySQL mentions (10)

  • Save Cost on RDS Data Transfer - Internet - Out
    Another option could be ProxySQL, where you can cache queries on the ProxySQL server. Source: about 1 year ago
  • Is replication between v5.1 and v8 possible?
    Also, if you're not using it yet, I can recommend looking at ProxySQL to do your read-write/read-only failover controls. Source: over 1 year ago
  • SSL Termination for SQL
    What are the recommendations here? I took a look into ProxySQL and it looks like since v2, it can do frontend and backend SSL connections. I have it locally working on a docker setup. Source: over 1 year ago
  • Business complexity with performance
    DB: Split you write-read operations. You may scale read as needed. Write operations can be slow if you have too many indices, so make sure to use only the ones you really need. Your DBMS may have some configuration to optimise, for example in MySQL if you do NOT need ACID compliance you can set innodb_flush_log_at_trx_commit = 2 to achieve better write speed. For MySQL you should also look into https://proxysql.com/. Source: over 1 year ago
  • Advanced caching mechanisms using distributed locks and async pub/sub systems.
    A Layer-7 Database Load Balancer is optional here. An L7-DBLB can be used for various use cases (eg: ProxySQL). One or more database instances handle queries from the web server. A Client-side DB query/connection load balancing can also be used instead of an L7-DBLB according to the use case of the application. - Source: dev.to / over 1 year ago
View more

GraphQL mentions (223)

  • Building Scalable GraphQL Microservices With Node.js and Docker: A Comprehensive Guide
    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 / 19 days ago
  • Type-Safe Fetch with Next.js, Strapi, and OpenAPI
    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 / 27 days ago
  • REST vs. GraphQL: A Detailed Comparison of API Architectures for Developers
    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
  • Gatsby tutorial: Build a static site with a headless CMS
    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
  • Rust GraphQL APIs for NodeJS Developers: Introduction
    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
View more

What are some alternatives?

When comparing ProxySQL and GraphQL, you can also consider the following products

Gonarch Tech - MySQL High Availability as a service

gRPC - Application and Data, Languages & Frameworks, Remote Procedure Call (RPC), and Service Discovery

PostgREST - Automatic REST API for Any Postgres Database

Next.js - A small framework for server-rendered universal JavaScript apps

MariaDB MaxScale - We are the company behind #MariaDB, the fastest growing #opensource #database. Download MariaDB at https://t.co/DtYwuH0FOl.

React - A JavaScript library for building user interfaces