StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Languages
  4. Query Languages
  5. GraphQL Ruby vs Prisma

GraphQL Ruby vs Prisma

OverviewDecisionsComparisonAlternatives

Overview

Prisma
Prisma
Stacks1.3K
Followers974
Votes55
GitHub Stars44.2K
Forks1.9K
GraphQL Ruby
GraphQL Ruby
Stacks68
Followers76
Votes0
GitHub Stars5.4K
Forks1.4K

GraphQL Ruby vs Prisma: What are the differences?

### Introduction
In this Markdown, we will focus on highlighting the key differences between GraphQL Ruby and Prisma.

1. **Language Support**: GraphQL Ruby primarily supports the Ruby programming language, allowing developers to write GraphQL schemas in Ruby syntax. On the other hand, Prisma supports multiple languages including TypeScript, JavaScript, Go, and others, providing flexibility to developers in choosing the language they are most comfortable with.
2. **Deployment Options**: GraphQL Ruby requires setting up and maintaining servers to host the GraphQL API, which can be a more involved process. In contrast, Prisma simplifies deployment by offering a cloud-based hosting solution, reducing the operational overhead for developers.
3. **Schema Management**: GraphQL Ruby relies on manual schema definitions within the Ruby codebase, which can lead to potential inconsistencies and errors. Prisma, on the other hand, uses a declarative data model that automatically generates a GraphQL schema based on the defined data model, ensuring consistency and reducing the likelihood of schema-related issues.
4. **Integration with Databases**: GraphQL Ruby provides support for integrating with various databases but requires additional setup and configuration to establish database connections. Prisma, by design, seamlessly connects to databases such as MySQL, PostgreSQL, and SQLite, simplifying the database integration process for developers.
5. **Real-time capabilities**: GraphQL Ruby lacks built-in real-time capabilities, requiring additional libraries or frameworks to implement real-time functionality. Prisma, with its subscriptions feature, offers real-time capabilities out of the box, enabling developers to easily implement real-time updates in their applications.
6. **Community and Ecosystem**: GraphQL Ruby has a smaller community and ecosystem compared to Prisma, which has gained traction and support from a larger developer community. This broader ecosystem often translates to more resources, tools, and community support available for developers using Prisma.

### Summary
In summary, GraphQL Ruby and Prisma differ in language support, deployment options, schema management, integration with databases, real-time capabilities, and community/ecosystem size.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Prisma, GraphQL Ruby

Raj
Raj

CTO & Founder at Novvum

Oct 5, 2020

Review

Hey Brian, it's hard to pick a best tool for any situation, however, there are tools that offer advantages dependent on use case.

Server Side

If you're looking to quickly generate a GraphQL API, you can use a Graphql As A Service like FaunaDB, Slash Graphql, or 8base.

If you want something more advanced on the server side: Prisma with Postgres, Nexus, & Apollo Server (js) is a great stack to try out. Examples here

Check out TypeORM and TypeGraphQL too

If you're have some existing data on Postgres, PostGraphile or Hasura are your best bet!

If you are using a lot of AWS services, check out Amplify and AppSync. Tutorial here

On the client side:

Check out Gatsby! Graphql is already configured and used to query static or remote information at build time. It's a great way to get your feet wet!

Apollo Client is often the choice for more advanced use cases. But URLQL and gqless are some pretty good alternatives too!

Hope this helps! 👍

294 views294
Comments

Detailed Comparison

Prisma
Prisma
GraphQL Ruby
GraphQL Ruby

Prisma is an open-source database toolkit. It replaces traditional ORMs and makes database access easy with an auto-generated query builder for TypeScript & Node.js.

Get going fast with the graphql gem, battle-tested and trusted by GitHub and Shopify.

Auto-generated and type-safe query builder for Node.js & TypeScript; Declarative data modeling & migration system; GUI to view and edit data in your database; Single source of truth for database and application models; Auto-completion in code editors instead of needing to look up documentation; Less boilerplate so developers can focus on the important parts of their app; Queries not classes to avoid complex model objects;
Define Your Schema - Describe your application with the GraphQL type system to create a self-documenting, strongly-typed API.; Run Queries - Serve queries to build a great UI or webservice.
Statistics
GitHub Stars
44.2K
GitHub Stars
5.4K
GitHub Forks
1.9K
GitHub Forks
1.4K
Stacks
1.3K
Stacks
68
Followers
974
Followers
76
Votes
55
Votes
0
Pros & Cons
Pros
  • 12
    Type-safe database access
  • 10
    Open Source
  • 8
    Auto-generated query builder
  • 6
    Supports multible database systems
  • 6
    Increases confidence during development
Cons
  • 2
    Doesn't support downward/back migrations
  • 1
    Mutation of JSON is really confusing
  • 1
    Do not support JSONB
  • 1
    Doesn't support JSONB
  • 1
    Do not support JSONB
No community feedback yet
Integrations
TypeScript
TypeScript
Node.js
Node.js
Microsoft SQL Server
Microsoft SQL Server
PostgreSQL
PostgreSQL
Serverless
Serverless
Apollo
Apollo
SQLite
SQLite
MongoDB
MongoDB
GraphQL
GraphQL
MariaDB
MariaDB
Ruby
Ruby
GraphQL
GraphQL

What are some alternatives to Prisma, GraphQL Ruby?

GraphQL

GraphQL

GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012.

Sequelize

Sequelize

Sequelize is a promise-based ORM for Node.js and io.js. It supports the dialects PostgreSQL, MySQL, MariaDB, SQLite and MSSQL and features solid transaction support, relations, read replication and more.

PostGraphile

PostGraphile

Execute one command (or mount one Node.js middleware) and get an instant high-performance GraphQL API for your PostgreSQL database

OData

OData

It is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. It helps you focus on your business logic while building RESTful APIs without having to worry about the various approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, etc.

Hibernate

Hibernate

Hibernate is a suite of open source projects around domain models. The flagship project is Hibernate ORM, the Object Relational Mapper.

Doctrine 2

Doctrine 2

Doctrine 2 sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernates HQL.

MikroORM

MikroORM

TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, MariaDB, PostgreSQL and SQLite databases.

Entity Framework

Entity Framework

It is an object-relational mapper that enables .NET developers to work with relational data using domain-specific objects. It eliminates the need for most of the data-access code that developers usually need to write.

peewee

peewee

A small, expressive orm, written in python (2.6+, 3.2+), with built-in support for sqlite, mysql and postgresql and special extensions like hstore.

MyBatis

MyBatis

It is a first class persistence framework with support for custom SQL, stored procedures and advanced mappings. It eliminates almost all of the JDBC code and manual setting of parameters and retrieval of results. It can use simple XML or Annotations for configuration and map primitives, Map interfaces and Java POJOs (Plain Old Java Objects) to database records.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase