Deploy ADS
Access Decision Service (ADS) is a Java application that you can deploy in several ways depending on your infrastructure and operational requirements.
Deployment options
| Option | When to use |
|---|---|
| JAR file | You want a straightforward, command-line deployment on a single host without container orchestration. |
| Kubernetes | You need container orchestration, scalability, or are running ADS alongside other services in a K8s cluster. |
With either deployment option, you can choose which engine mode ADS runs in. See Engine modes for details.
Choose JAR vs Kubernetes
Use the JAR deployment when:
- You are evaluating ADS or running a proof of concept
- You have a simple, single-host deployment
- You do not need container orchestration
Use the Kubernetes deployment when:
- You need horizontal scaling across multiple pods
- You are running ADS as part of a containerized microservices architecture
- You require rolling updates, health-based restarts, and declarative configuration
note
For TLS configuration specific to Kubernetes deployments, see TLS configuration for Kubernetes.
Before you deploy
If this is your first time setting up ADS, start with the Get started section. It covers prerequisites, licensing, and the basic configuration you need before deploying.