Skip to end of metadata
Go to start of metadata

Stabilize your services with the Repose API Filter

What Is Repose?

Repose is an open-source RESTful HTTP proxy service. It provides the solution to common API processing tasks such as rate limitingclient authenticationversioninglogging, and much moreRepose allows services to use Enterprise Integration Patterns.

How Does Repose Work?

Repose allows downstream services to trust incoming requests as authorized, and well formed.
Repose takes incoming requests and adjusts them to be ready for consumption by passing requests through a series of filters. These filters provide functionality such as Authentication, Authorization, Rate Limiting and Request Modification. 

You download and install Repose on your server, configure your downstream service endpoint in the system-model and you are set to configure filters and services that work for you. We have many sample configs you can use to get started. Or, since Repose is open source, you can build your own stacks of reusable software components. 

Repose runs as a standalone proxy server which sits between the client and the downstream service.  We call this deployment method Valve. Repose can also run within a servlet container such as Glassfish or Tomcat in the Root.war deployment.  You decide which one works best for you.

You can tweak many of your configurations without having to restart Repose – it will pick up config changes on the fly, making it easy to configure and test.

Repose can be configured to use a distributed data store service where cached information is exchanged across multiple nodes. This makes Repose fault tolerate with proven performance.

What Features Does Repose Offer?

The most popular Repose features are:

  • Client Authentication
  • Client Authorization
  • Rate Limiting
  • Versioning
  • HTTP Logging
  • Content Normalization
  • Translation

See the complete list of Repose Filters.

Get started with Repose

  1. Install
  2. Configure
  3. Test
  4.  Analyze

 

Icon

If you wonder what we've been working on lately, visit Recent Changes.

 

 

  • No labels