Question 1

How to add a database to sangria akka-http example?

Accepted Answer

The example uses mock data; to add a database, you need to modify the sangria resolvers to fetch from sources like PostgreSQL with Slick or MongoDB, and update the schema to include mutations and proper data models.

Question 2

Sangria or GraphQL Java for Scala projects?

Accepted Answer

Sangria is native to Scala with better integration for Scala features like case classes and Futures, while GraphQL Java is Java-based and may require more boilerplate. Sangria is often preferred for Scala-centric teams.

Question 3

How to deploy this GraphQL server to Heroku?

Accepted Answer

Use the Heroku deploy button in the README or set up an sbt build with a Procfile; ensure environment variables for port configuration, as akka-http defaults to 8080 but Heroku requires dynamic port binding.

Question 4

Does this example support GraphQL subscriptions?

Accepted Answer

No, it only demonstrates basic queries and variables. Sangria supports subscriptions, but you'd need to implement them separately, likely with akka-streams or WebSockets for real-time data.

Question 5

How to customize the GraphQL playground in sangria?

Accepted Answer

The playground is served via akka-http; to customize, modify the server code to pass configuration options like theme or settings through the playground endpoint or consider embedding a different GraphQL IDE.

Question 6

Can I use this with Play Framework instead of akka-http?

Accepted Answer

Not directly; this example is tied to akka-http. To use sangria with Play, adapt the HTTP routing and request handling, as Play has different abstractions for web servers and may require additional dependencies.

sangria-akka-http-example

What is sangria-akka-http-example?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions