Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Orchestrator #23

Closed
tomcrane opened this issue Oct 25, 2020 · 2 comments
Closed

New Orchestrator #23

tomcrane opened this issue Oct 25, 2020 · 2 comments

Comments

@tomcrane
Copy link
Contributor

Orchestrator is now itself the load balancer and reverse proxy, rather than using NGINX in front of .NET.

  • includes Redis to track asset state and location
  • enforces access control on assets
  • Optionally uses disk-based web cache (but see this) or Cloudfront
@tomcrane
Copy link
Contributor Author

tomcrane commented Nov 9, 2020

Possibly #12

This needs revisiting

@donaldgray
Copy link
Member

Closing this as we have the basics for a YARP-based Orchestrator implementation. Tickets can be tracked on Orchestrator board or orchestrator .

Regarding the 3 points raised in the initial comment:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants