Search Results for "requests"

Scala Steward is an automated tool that helps to keep Scala libraries and plugins up to date by checking for dependency updates and sending pull requests.

A Git platform powered by Scala with easy installation, high extensibility & GitHub API compatibility. GitBucket is a Git web platform powered by Scala offering, easy installation, intuitive UI, high extensibility by plugins, API compatibility with GitHub. You can also deploy gitbucket.war to a servlet container which supports Servlet 3.0 (like Jetty, Tomcat, JBoss, etc). To upgrade GitBucket, replace gitbucket.war with the new version, after stopping GitBucket. All GitBucket data is stored...

SpinalHDL is a hardware description (HDL) framework embedded in Scala, enabling hardware designers to build digital circuits with modern programming abstractions. Instead of writing in Verilog or VHDL directly, users describe hardware components and their interconnects using Scala code and Spinal’s domain-specific library, which then emits synthesizable hardware (e.g. as Verilog). Because SpinalHDL is embedded in Scala, it allows reuse of functional abstractions, parameterization, modular...

...The OpenWhisk platform supports a programming model in which developers write functional logic (called Actions), in any supported programming language, that can be dynamically scheduled and run in response to associated events (via Triggers) from external sources (Feeds) or from HTTP requests. The project includes a REST API-based Command Line Interface (CLI) along with other tooling to support packaging, catalog services and many popular container deployment options. Since Apache OpenWhisk builds its components using containers it easily supports many deployment options both locally and within Cloud infrastructures.

Graphcool was an open-source framework for developing and deploying GraphQL-based backends. It acts as a “backend-as-a-service / framework” that lets you define your data model via GraphQL SDL (Schema Definition Language), and in turn generates a GraphQL CRUD API, supports nested mutations, filtering, pagination, and real-time subscriptions. Graphcool separates the business logic from stateful storage components, allowing the stateful parts (database, subscription engine) to scale...

Diffy is a traffic-shadowing and response-diffing tool that helps you validate a new version of a service against a trusted baseline before a full cutover. It acts as a proxy that fans out real production requests to three backends: the current “primary,” a “candidate” (new build), and a “shadow” baseline, then compares responses to detect behavioral differences. By using live traffic rather than synthetic tests, Diffy surfaces edge cases and data-dependent discrepancies that unit tests often miss. It provides mechanisms to normalize noise (timestamps, IDs, ordering) so diffs reflect meaningful regressions rather than incidental variance. ...

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

Gizzard is a Scala framework originally developed by Twitter for building scalable, fault-tolerant, distributed key-value stores that can be sharded and replicated. It provides infrastructure for routing requests through shard trees, splitting or rebalancing shards dynamically, failover, and migrations. In Gizzard, data is stored in underlying storage shards (which could be databases or other stores) and Gizzard handles the process of routing requests correctly as the cluster topology changes. Gizzard's architecture is designed for operational flexibility: you can change the shard layout over time, reassign replicas, migrate data between nodes, and have requests redirected during transitions. ...