Ambassador is great!
Use Cases and Deployment Scope
Currently, we use Ambassador as a secondary ingress controller. It addresses our needs by facilitating adding dynamic routes for our incredible number of endpoints. That way it makes it very easy to get multiple parallel microservices we need to be deployed to support our testing and quality assurance needs.
Pros
- Simple syntax
- Easy to understand
- Easy to install
Cons
- Documentation is not updated
- Implementing external authentication doesn't always work as described in the documentation
- The Administration console is limited
Return on Investment
- Reduced downtime by redirecting traffic between DC.
- Reduced engineering time, don't have to dedicate 1 person to manage it.
- Increased training costs in the short term.
Alternatives Considered
NGINX
Other Software Used
Amazon Simple Notification Service (SNS), Amazon Relational Database Service (RDS), Slack, Jira Software, Atlassian Confluence