You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some ideas for accomplishing this while also attaining dev/prod parity (h/t @slowr for the suggestions):
Utilize a cloud provider's blob storage functionality for storing the DistilBert model and ES index, or alternatively investigate using blob storage in PostgreSQL;
Transition to Kubernetes and package the application as a Helm package;
These are all great suggestions, thank you @slowr! Using terraform and kubernetes would be beneficial (and a technical challenge we'd like to work on!).
Would it make sense to run kubernetes (AWS EKS) on Fargate? Some thoughts on our use case:
Our pipeline needs to run every forthnight - we don't need the system to be always up.
Orion is still in its early days so it might be better to go serverless and focus more on client-facing features. Fargate would deal with some of the complexity of running kubernetes (autoscaling, IAM identity management) and maybe reduce the overall cost of the system (see here and here)
Would this be a sensible setup? Happy to learn about alternatives too!
For your use-case going server-less and using AWS EKS with Fargate (or GCP Cloud Run, etc) is the best solution price-wise and I would choose that for sure.
Fargate removes the need of specifying how many nodes you need on the control-plane when setting up the cluster which is a great resource-elasticity feature.
Be very careful on your CPU and RAM resource limits defined in your kubernetes manifests as Fargate uses them as source-of-truth to allocate the machines and do the pricing.
Some ideas for accomplishing this while also attaining dev/prod parity (h/t @slowr for the suggestions):
The text was updated successfully, but these errors were encountered: