sangria
Scala GraphQL implementation (by sangria-graphql)
Colossus
I/O and Microservice library for Scala (by tumblr)
Our great sponsors
| sangria | Colossus | |
|---|---|---|
| 5 | - | |
| 1,962 | 1,144 | |
| -0.2% | 0.0% | |
| 8.6 | 0.0 | |
| 9 days ago | over 2 years ago | |
| Scala | Scala | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sangria
Posts with mentions or reviews of sangria.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-29.
- GraphQL is quickly moving to one of my least favorite technologies
-
How is this calculating complexity?
I am taking a look at Resolver from the Sangria GraphQL library and I cannot figure out how calcComplexity works. The code in the `Success` us really confusing to me. Where is the complexity getting calculated?
-
Where is this value coming from?
I started taking a look at QueryReducer from the Sangria GraphQL library and I am having a really hard tracing the logic for rejectMaxDepth. More specifically, I don't understand why depth is a parameter to measureDepth, where it is coming from, and how the depth is being calculated in measureDepth.
-
How (Not) To Build Your Own GraphQL Server
Instead of constructing an object, it uses classes to define the types and operations for the schema that it generates. The schema generated by this implementation will have the same structure as the schema created with graphql-js. Using classes to define your schema has the advantage of being less mutable and more structured when writing code. Similar implementations can be found for TypeScript with the library TypeGraphQL or Sangria GraphQL for Scala.
-
What is the state of frameworks and libraries support to build microservices in scala?
As Api gateway we use sangria on top of Finagle (finch to be precise) and that has been a huge boon in making the connection between microservices and frontend seamless/safe.
Colossus
Posts with mentions or reviews of Colossus.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning Colossus yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
When comparing sangria and Colossus you can also consider the following projects:
Finatra - Fast, testable, Scala services built on TwitterServer and Finagle
Play - The Community Maintained High Velocity Web Framework For Java and Scala.
Scalatra - Tiny Scala high-performance, async web framework, inspired by Sinatra
Analogweb
youi - Next generation user interface and application development in Scala and Scala.js for web, mobile, and desktop.
Skinny Framework - :monorail: "Scala on Rails" - A full-stack web app framework for rapid development in Scala
Unfiltered - A toolkit for servicing HTTP requests in Scala