Search Results for "middleware"

The flexible HTTP client library for Elixir, with support for middleware and multiple adapters. Tesla is an HTTP client loosely based on Faraday. It embraces the concept of middleware when processing the request/response cycle. Define module with use Tesla and choose from a variety of middleware. Tesla is built around the concept of composable middlewares. This is very similar to how Plug Router works.

Commanded is an Elixir framework for implementing CQRS (Command Query Responsibility Segregation) and Event Sourcing patterns. It provides domain-driven design tools—aggregates, commands, events, and projections—backed by an event store (e.g. PostgreSQL).

Plug is a specification and set of utilities for building composable modules in Elixir web applications. It defines a standard connection interface, allowing developers to create “plugs” that act as middleware for handling requests and responses. Examples include parsing parameters, managing sessions, logging, or authentication, all of which can be plugged into a pipeline. Plug serves as the foundation for the Phoenix framework, which builds on it to deliver a full-featured web stack. The library supports both synchronous and streaming responses, making it adaptable to various web scenarios. ...

Exq is a job processing library compatible with Resque / Sidekiq for the Elixir language. Exq uses Redis as a store for background processing jobs. Exq handles concurrency, job persistence, job retries, reliable queueing and tracking so you don't have to. Jobs are persistent so they would survive across node restarts. You can use multiple Erlang nodes to process from the same pool of jobs. Exq uses a format that is Resque/Sidekiq compatible. This means you can use it to integrate with...

Maru is a DSL for building HTTP/REST APIs in Elixir that emphasizes concise routing, parameter validation, and versioning. Inspired by Ruby’s Grape, it lets you describe endpoints declaratively—paths, verbs, and nested scopes—while composing reusable middleware via Plug. Strong parameter parsing and validators help keep controllers clean by moving input checking and coercion into the route layer. Built-in support for namespacing and API versioning simplifies rolling changes or maintaining multiple client generations side by side. Error handling, helpers, and content negotiation are wired into the DSL, so common cross-cutting concerns are consistent across endpoints. ...