metaflow VS botocore

I would recommend the following: - https://www.mage.ai/ - https://dagster.io/ - https://www.prefect.io/ - https://metaflow.org/ - https://zenml.io/home

1) I've been looking into [Metaflow](https://metaflow.org/), which connects nicely to AWS, does a lot of heavy lifting for you, including scheduling.

even for people who don't have an ML background there's now a lot of very fully-featured model deployment environments that allow self-hosting (kubeflow has a good self-hosting option, as do mlflow and metaflow), handle most of the complicated stuff involved in just deploying an individual model, and work pretty well off the shelf.

They had to figure out video compression that worked at the volume that they wanted to deliver. They had to build and maintain their own CDN to be able to have a always available and consistent viewing experience. Don’t even get me started on the resiliency tools like hystrix that they were kind enough to open source. I mean, they have their own fucking data science framework and they’re looking into using neural networks to downscale video.. Sound familiar? That’s cause that’s practically the same thing as Nvidia’s DLSS (which upscales instead of downscales).

Check out Metaflow by Netflix

Github Actions, Metaflow and AWS SageMaker are awesome technologies by themselves however they are seldom used together in the same sentence, even less so in the same Machine Learning project.

It's undeniable that leadership is instrumental in any company and project success, however I was intrigued with one of their ML tool choices that helped them reach their goal. I was so curious about this choice that I just had to learn more about it, so in this article will be talking about a sound strategy of effectively scaling your AI/ML undertaking and a tool that makes this possible - Metaflow.

With some searching, you can sometimes get an idea of what’s to come in the future. AWS’s SDKs are intended to be used with all AWS partitions, supporting all the partitions and regions. By examining the Python SDK (boto) code , we can infer that two more partitions may be in progress.

More correctly would likely be https://github.com/boto/botocore/issues/1543

Pretty much all of the SDKs refer to a standard set of JSON files that define the APIs, in a much older internal format ("C2J") than anything like Smithy or OpenAPI. You can find these in most SDK repos today, e.g. boto3: https://github.com/boto/botocore/blob/develop/botocore/data/kms/2014-11-01/service-2.json