Search Results for "development server stacks"

Scala combines object-oriented and functional programming in one concise, high-level language. Scala's static types help avoid bugs in complex applications, and its JVM and JavaScript runtimes let you build high-performance systems with easy access to huge ecosystems of libraries. Scastie is Scala + sbt in your browser! You can use any version of Scala, or even alternate backends such as Dotty, Scala.js, Scala Native, and Typelevel Scala. You can use any published library. You can save and...

Sangria is a Scala GraphQL implementation. It is an example of GraphQL server written with Play framework and Sangria. It also serves as a playground, where you can interactively execute GraphQL queries and play with some examples. If you want to use sangria with a react-relay framework, then you also may be interested in sangria-relay. Sangria is a spec-compliant GraphQL implementation, so it works out of the box with Apollo, Relay, GraphiQL and other GraphQL tools and libraries. Since...

Declarative, type-safe web endpoints library. With tapir, you can describe HTTP API endpoints as immutable Scala values. Each endpoint can contain a number of input and output parameters. Compile-time guarantees, develop-time completions, read-time information. Separate the shape of the endpoint (the "what"), from the server logic (the "how"). Generate documentation from endpoint descriptions. Leverage the metadata to report rich metrics and tracing information. Re-use common endpoint...

Caliban is a purely functional library for building GraphQL servers and clients in Scala. The design principles behind the library are the following. Minimal amount of boilerplate: no need to manually define a schema for every type in your API. Pure interface: errors and effects are returned explicitly (no exceptions thrown), all returned types are referentially transparent (no Future). Clean separation between schema definition and implementation: schema is defined and validated at compile...

Kamon Telemetry is a set of libraries for instrumenting applications running on the JVM. With Kamon Telemetry you can collect metrics, propagate context across threads and services, and get distributed traces automatically. The best way to get started is by following our installation guides and taking it from there. Have fun with Kamon. Monitor your backend applications, fix performance issues, and get alerted when problems happen. All without being a monitoring expert. Everybody starts...

ScalikeJDBC is a tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use and very flexible APIs. What’s more, QueryDSL makes your code type-safe and reusable. ScalikeJDBC is a practical and production-ready one. Use this library for your real projects. Whether you like it or not, JDBC is a stable standard interface. Since most of RDBMS supports JDBC interface, we can access RDBMS in the same way. We believe that ScalikeJDBC...

C1000K-Servers is a benchmark and prototype collection for high-performance WebSocket servers. It compares implementations built with frameworks and runtimes such as Spray, Netty, Undertow, Jetty, Vert.x, Grizzly, Node.js, Go, and Go-fasthttp. The project focuses on large-scale long-lived WebSocket connections and documents tests reaching more than one million active connections. It includes simple server prototypes that can act as scaffolds for chat, message pushing, notification, or...

...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.