How to set up Reitit with Ring for a REST API?

Use the `reitit-ring` module to define routes as data, integrate coercion middleware like `rrc/coerce-request-middleware`, and add modules for validation—see the Ring example in the README for a step-by-step guide.

Reitit vs Compojure: which is better for a new Clojure web app?

Reitit offers better performance, modularity, and bi-directional routing, but Compojure is simpler and more opinionated; choose Reitit for complex, data-driven apps, and Compojure for quick prototypes.

Can Reitit handle client-side routing in ClojureScript?

Yes, the `reitit-frontend` module provides tools for frontend routing with data-driven syntax and bi-directional capabilities, similar to server-side usage, as shown in the examples.

How to generate OpenAPI docs with Reitit?

Use the `reitit-openapi` module to annotate routes with data, which automatically generates OpenAPI specifications that can be served with Swagger UI for interactive documentation.

What are the common pitfalls when using Reitit's coercion?

Ensure proper middleware ordering and error handling, as coercion errors can be verbose; leverage the friendly error messages to debug validation issues, as demonstrated in the invalid request example.

How to integrate Reitit with Pedestal for interceptors?

Use the `reitit-pedestal` extra module to map Reitit routes to Pedestal interceptors, allowing you to leverage Pedestal's concurrency model while benefiting from Reitit's routing features.

Is Reitit suitable for microservices with high performance needs?

Yes, its fast routing and modular design make it ideal for microservices, but consider the setup complexity and ensure compatibility with your deployment environment's JVM version.

Reitit — Fast Clojure Routing Library

What is Reitit?

Reitit is a fast, data-driven routing library for Clojure and ClojureScript that handles both server-side and client-side routing. It solves the problem of defining, matching, and generating URLs in a consistent, extensible way across different web frameworks like Ring, Pedestal, and frontend applications.

Target Audience

Clojure and ClojureScript developers building web applications, REST APIs, or single-page apps who need a robust, performant routing solution with strong validation and framework integration.

Value Proposition

Developers choose Reitit for its combination of speed, modularity, and excellent developer experience—offering bi-directional routing, pluggable coercion with popular validation libraries, and seamless integration with the Clojure ecosystem.

A fast data-driven routing library for Clojure/Script

Use Cases

Best For

Building REST APIs in Clojure with Ring or Pedestal
Developing single-page applications in ClojureScript with client-side routing
Projects requiring automatic request/response validation using Malli, Schema, or clojure.spec
Teams needing OpenAPI or Swagger documentation generation from routes
Applications where performance-critical routing is a priority
Modular web architectures where routing logic must be reused across different frameworks

Not Ideal For

Projects using minimal web frameworks where a simpler router like Compojure suffices without modular overhead
Teams heavily invested in non-Clojure web stacks, as Reitit is tightly coupled to the Clojure ecosystem
Applications requiring out-of-the-box WebSocket routing, since Reitit focuses on HTTP-based routing without native real-time support
Quick prototypes or hackathons where rapid setup with opinionated, all-in-one frameworks is prioritized

Pros & Cons

Pros

Data-Driven Flexibility

Routes are defined as plain Clojure data structures, enabling easy composition and programmatic manipulation, as shown in the quick start with vector-based definitions.

Pluggable Coercion

Integrates seamlessly with Malli, Schema, and clojure.spec for automatic request/response validation, reducing boilerplate and ensuring data integrity, demonstrated in the Ring example with coercion errors.

Framework Agnostic

Offers first-class support for Ring, HTTP interceptors, Pedestal, and frontend routing, allowing consistent routing logic across server and client applications.

Modular Architecture

Core routing is separated from optional modules like OpenAPI and Swagger, enabling lean deployments and customization, though this adds setup complexity.

Performance Optimized

Benchmarked as fast with efficient route matching and generation, crucial for high-traffic applications, as highlighted in the README's performance section.

Cons

Configuration Overhead

The modular design requires selecting and integrating multiple dependencies for features like coercion and middleware, complicating initial setup compared to all-in-one solutions.

Version Constraints

Mandates Clojure 1.11 and Java 11+, which may hinder adoption in legacy projects or environments with older JVM versions.

Steeper Learning Curve

The data-driven approach and extensive use of route data can be challenging for developers unfamiliar with Clojure's functional idioms or coming from imperative routing libraries.

Limited Built-in Features

Common functionalities like middleware and interceptors are in separate modules, adding dependency management overhead versus integrated frameworks.

Frequently Asked Questions

What is Reitit?

Target Audience

Clojure and ClojureScript developers building web applications, REST APIs, or single-page apps who need a robust, performant routing solution with strong validation and framework integration.

Value Proposition

Use Cases

Best For

Building REST APIs in Clojure with Ring or Pedestal
Developing single-page applications in ClojureScript with client-side routing
Projects requiring automatic request/response validation using Malli, Schema, or clojure.spec
Teams needing OpenAPI or Swagger documentation generation from routes
Applications where performance-critical routing is a priority
Modular web architectures where routing logic must be reused across different frameworks

Not Ideal For

Projects using minimal web frameworks where a simpler router like Compojure suffices without modular overhead
Teams heavily invested in non-Clojure web stacks, as Reitit is tightly coupled to the Clojure ecosystem
Applications requiring out-of-the-box WebSocket routing, since Reitit focuses on HTTP-based routing without native real-time support
Quick prototypes or hackathons where rapid setup with opinionated, all-in-one frameworks is prioritized

Pros & Cons

Pros

Data-Driven Flexibility

Routes are defined as plain Clojure data structures, enabling easy composition and programmatic manipulation, as shown in the quick start with vector-based definitions.

Pluggable Coercion

Framework Agnostic

Offers first-class support for Ring, HTTP interceptors, Pedestal, and frontend routing, allowing consistent routing logic across server and client applications.

Modular Architecture

Core routing is separated from optional modules like OpenAPI and Swagger, enabling lean deployments and customization, though this adds setup complexity.

Performance Optimized

Benchmarked as fast with efficient route matching and generation, crucial for high-traffic applications, as highlighted in the README's performance section.

Cons

Configuration Overhead

The modular design requires selecting and integrating multiple dependencies for features like coercion and middleware, complicating initial setup compared to all-in-one solutions.

Version Constraints

Mandates Clojure 1.11 and Java 11+, which may hinder adoption in legacy projects or environments with older JVM versions.

Steeper Learning Curve

The data-driven approach and extensive use of route data can be challenging for developers unfamiliar with Clojure's functional idioms or coming from imperative routing libraries.

Limited Built-in Features

Common functionalities like middleware and interceptors are in separate modules, adding dependency management overhead versus integrated frameworks.

Frequently Asked Questions

Reitit

What is Reitit?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

Reitit

What is Reitit?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?