Question 1

How do I set up GraphQL subscriptions with Lacinia?

Accepted Answer

Define subscription fields in your EDN or SDL schema and write resolvers that return async streams; use lacinia-pedestal for WebSocket support to handle real-time connections efficiently.

Question 2

Lacinia vs graphql-java for Clojure: which should I choose?

Accepted Answer

Lacinia is designed for Clojure with idiomatic APIs and EDN schemas, offering better integration, while graphql-java is a Java library that works from Clojure but may feel less native. Pick Lacinia for a pure Clojure experience or if you value its data-centric approach.

Question 3

How to handle authentication in a Lacinia API?

Accepted Answer

Authentication is typically done at the HTTP layer (e.g., using Ring middleware) before queries reach Lacinia; inject user context into the execution context for resolvers to access authorization data.

Question 4

Can Lacinia work with databases like Datomic or JDBC sources?

Accepted Answer

Yes, Lacinia is backend-agnostic; write resolvers that query any data source, such as using Clojure libraries for Datomic or SQL databases, and return Clojure maps or records.

Question 5

What are Lacinia's performance benchmarks compared to Node.js GraphQL servers?

Accepted Answer

Lacinia runs on the JVM with Antlr4 parsing, offering good performance for heavy loads, but it may have higher memory overhead than Node.js alternatives; specific benchmarks vary by use case and schema complexity.

Question 6

How to migrate a REST API to GraphQL using Lacinia?

Accepted Answer

Start by defining a GraphQL schema in EDN or SDL that mirrors your REST endpoints, then implement resolvers that call existing business logic or APIs, gradually expanding the schema as you refactor.

Lacinia

What is Lacinia?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions