awesome-graphql-java
sangria
awesome-graphql-java | sangria | |
---|---|---|
1 | 5 | |
585 | 1,968 | |
0.2% | 0.3% | |
3.3 | 8.4 | |
7 months ago | 12 days ago | |
Scala | ||
- | Apache License 2.0 |
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.
awesome-graphql-java
-
GraphQL is quickly moving to one of my least favorite technologies
https://github.com/Netflix/dgs-framework#readme
There's an "awesome" list in the graphql-java org, too: https://github.com/graphql-java/awesome-graphql-java#readme
sangria
- 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.
What are some alternatives?
dgs-framework - [Moved to: https://github.com/Netflix/dgs-framework]
Finatra - Fast, testable, Scala services built on TwitterServer and Finagle
graphql-java - GraphQL Java implementation
Scalatra - Tiny Scala high-performance, async web framework, inspired by Sinatra
service-engine-template - Template: REST, GraphQL & gRPC services for CRUD to Popular Databases. Supports Schema Migrations and built using service-engine Docker Image.
Colossus - I/O and Microservice library for Scala
hotchocolate - Welcome to the home of the Hot Chocolate GraphQL server for .NET, the Strawberry Shake GraphQL client for .NET and Banana Cake Pop the awesome Monaco based GraphQL IDE. [Moved to: https://github.com/ChilliCream/graphql-platform]
Play - The Community Maintained High Velocity Web Framework For Java and Scala.
Analogweb
youi - Next generation user interface and application development in Scala and Scala.js for web, mobile, and desktop.
Socko - A Scala web server powered by Netty networking and AKKA processing.
Skinny Framework - :monorail: "Scala on Rails" - A full-stack web app framework for rapid development in Scala