Decide Runtime Targets about router HOT 5 CLOSED

The very general desire is that we be able to run on Kubernetes and AWS-Lambda-like environments, but that's of course caught up in the implementation details of the Docker images that are running within it and the binary that we're trying to run on it!

Kubernetes seems pretty well understood, but we should try to identify the technical requirements of running on AWS Lambda!

from router.

strawdog: let's not bother trying to support 32-bit.

other strawdogs?

from router.

Kubernetes seems pretty well understood, but we should try to identify the technical requirements of running on AWS Lambda!

I think supporting the "cheaper" lambda architecture for ARM is preferred as the router will spend most of it's time waiting for other services to respond rather than doing anything computational heavy.

from router.

Any idea what the roadmap looks like for this? It's a huge blocker for us and I'm sure a lot of others for running the router locally (natively) on M1 Mac.

from router.

I'm going to close this issue, which was originally meant to track which architectures we wanted to support. If you're looking to track the ARM support stuff, then I'd recommend following #1192.

from router.