📗
Janus Manual
  • Introduction
  • Installation
    • Docker
  • Quick Start
    • Authenticating
    • Add an endpoint
    • Modify (Update/Delete) an endpoint
    • Add Plugins
    • Authentication
    • Adding your API - File System
  • Clustering/HA
  • Proxy Reference
    • Terminology
    • Overview
    • Routing capabilities
    • Load Balacing
    • Request Host header
      • Using wildcard hostnames
      • The preserve_host property
    • Request URI
      • The strip_path property
      • The append_path property
    • Request HTTP method
    • Routing priorities
    • Conclusion
  • Plugins
    • Basic
    • Organization
    • Body Limit
    • Circuit Breaker
    • Compression
    • CORS
    • OAuth
    • Rate Limit
    • Request Transformer
    • Response Transformer
    • Retry
  • Auth
    • OAuth 2.0
  • Misc
    • Health Checks
    • Monitoring
    • Tracing
  • Known Issues
    • Stale HTTP Keep-Alive
  • Upgrade Notes
    • 2.x to 3.x
    • 3.6.x to 3.7.x
Powered by GitBook
On this page

Was this helpful?

Clustering/HA

Multiple Janus nodes pointing to the same datastore must belong to the same "Janus Cluster".

A Janus cluster allows you to scale the system horizontally by adding more machines to handle a bigger load of incoming requests, and they all share the same data since they point to the same datastore.

A Janus cluster can be created in one datacenter, or in multiple datacenters, in both cloud or on-premise environments. Janus will take care of joining and leaving a node automatically in a cluster, as long as the node is configured properly.

Configuration update

Some backends requires that you define an update interval, which is used to check for changes on that storage. You can do that by setting the cluster configuration like this:

[cluster]
  UpdateFrequency = "5s"
PreviousAdding your API - File SystemNextProxy Reference

Last updated 4 years ago

Was this helpful?