Search Results for "client server"

...Since GraphQL has a type system, the server defines a schema that the client can query using the introspection API. This provides the client with a set of possibilities. After the client got this information and decided which parts of the data it needs, it is able to describe its data requirements in form of a GraphQL query. An important aspect of GraphQL is that it’s completely backend agnostic.

...The core philosophy behind Spray is that it should act as a “library” for integration and HTTP layers, not as a full application framework—it gives you the building blocks to handle HTTP and REST but doesn’t impose heavy structure. It includes modules for low-level HTTP I/O, routing, client and server APIs, HTTP model (requests/responses), (un)marshalling, servlet adapters, and testing utilities. Its routing DSL offers expressive combinators for defining HTTP endpoints, and its testkit allows route logic to be tested in isolation (even without spinning up actors). It was popular in earlier Scala/Akka stacks but has since been superseded by Akka HTTP as the maintained successor.