Skip to content
A Clojure (JVM) library for developing GraphQL API instantly from Postgres and MySQL databases
Clojure
Branch: master
Clone or download

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src/graphqlize/lacinia
.gitignore add pom file Jan 20, 2020
LICENSE
README.md Update README.md Mar 25, 2020
deps.edn bump dependencies Feb 26, 2020
pom.xml bump version Mar 29, 2020

README.md

GraphQLize

GraphQLize, an open-source Clojure (JVM) library for developing GraphQL API instantly from your existing PostgreSQL and MySQL databases.

It aims to simplify the effort required to expose GraphQL APIs over relational databases.

Clojars Project

GraphQLize is at its early stages now. The objective of this early release is to get early feedback from the community. It is not production-ready yet!

Rationale

In the JVM ecosystem, developing GraphQL APIs to expose the data from the relational databases requires a lot of manual work. Right from defining the GraphQL schemas (either code-first or schema-first) to wiring them with resolvers and the database access logic, we spend a significant amount of our development time.

In addition to this, we also need to take care of optimizing the underlying SQL queries to avoid problems like N+1 queries. We have to account the maintenance of the resulting codebase as well!

GraphQLize will help you to overcome all these shortcomings. It provides you with an efficient GraphQL implementation in just few lines of code.

What is GraphQLize?

GraphQLize is a JVM library written in Clojure with Java interoperability. The crux of GraphQLize is generating the GraphQL schema and resolving the queries by making use of JDBC metadata provided by the JDBC drivers.

It currently supports Postgres (9.4 & above) and MySQL (8.0 & above).

Getting Started

Getting started with GraphQLize is simple and involves only a few steps.

  1. Add the GraphQLize dependency in your project.
  2. Initialize GraphQLize Resolver by providing the Java SQL data source.
  3. Add a GraphQL API endpoint and use the initialized GraphQlize Resolver in the previous step.

The actual implementation of these steps will vary based on which language (Java, Clojure) and framework (Spring Boot, Spark Java, Pedestal, etc.). Please refer the below links for more details.

Langauge Framework(s)
Java Spring Boot, Spark Java, Vanilla Java
Kotlin Spring Boot, Ktor
Clojure Pedestal, Ring, Vanilla Clojure
Scala Scalatra

Is It Production Ready?

It will be in a few months.

The objective of this alpha release is to get early feedback from the community.

There are close to forty issues that I am planning to work on in the upcoming months to make it production ready.

You can keep track of the progress by

How can I contribute?

GraphQLize is at its early stage now, and the codebase and the APIs are not stable yet.

So, at this instant, the best way to contribute is to initiate a chat in GraphQLize's Discord channel or raise a GitHub issue with all the relevant details, and we'll take it from there.

Oracle & SQL Server Support

One of the design goal of GraphQLize from day one is to support Postgres, MySQL, Oracle & MS SQL Server. To start with, I am focussing on getting it to a production ready state for Postgres & MySQL. After accomplishing this, I will be focusing on the other two.

Acknowledgements

PostgREST, PostGraphile, KeyStoneJs and Hasura are the inspiration behind GraphQLize.

GraphQLize is not possible without the following excellent Clojure libraries.

The samples in the documentation of GraphQLize uses the Sakila database from JOOQ extensively.

License

The use and distribution terms for this software are covered by the Eclipse Public License - v 2.0. By using this software in any fashion, you are agreeing to be bound by the terms of this license.

You can’t perform that action at this time.