DEV Community

Mursal Furqan Kumbhar for AWS Community Builders

Posted on • Edited on

1

When NOT to use Amazon Sagemaker

Hey Friends ✋
So I hope you liked my previous article on why we can move towards Amazon Sagemaker, but as they say, you can use sugar everywhere.
Similarly, in this article we are going to discuss some scenarios, where we can NOT use Amazon Sagemaker. Or I should rephrase it as where Amazon Sagemaker won't be a viable option.

The problems we discussed in the past article though represent a vast majority of ML projects, there are certainly few scenarios where this might not be a valid option.

Scenarios

  1. Sagemaker, expects you to code your data engineering and analysis needs(in your choice of language).
  2. The entire orchestration of infrastructure and transition from one phase to another though happens with few lines code; definitely needs a small amount of code.
  3. For professionals, who prefer a drag and drop (absolutely no code) solutions for the data engineering and modeling phase, Azure ML studio would be a more ideal choice.
  4. Both Azure ML Studio and AWS Sagemaker are great platforms for developing ML solutions but are targetted for a completely different set of users.

Conclusions

AWS Sagemaker has been a great deal for most data scientists who would want to accomplish a truly end-to-end ML solution. It takes care of abstracting a ton of software development skills necessary to accomplish the task while still being highly effective and flexible and cost-effective. Most importantly, it helps you focus on the core ML experiments and supplements the remainder necessary skills with easy abstracted tools similar to our existing workflow.

Image of Timescale

🚀 pgai Vectorizer: SQLAlchemy and LiteLLM Make Vector Search Simple

We built pgai Vectorizer to simplify embedding management for AI applications—without needing a separate database or complex infrastructure. Since launch, developers have created over 3,000 vectorizers on Timescale Cloud, with many more self-hosted.

Read more

Top comments (0)

Best Practices for Running  Container WordPress on AWS (ECS, EFS, RDS, ELB) using CDK cover image

Best Practices for Running Container WordPress on AWS (ECS, EFS, RDS, ELB) using CDK

This post discusses the process of migrating a growing WordPress eShop business to AWS using AWS CDK for an easily scalable, high availability architecture. The detailed structure encompasses several pillars: Compute, Storage, Database, Cache, CDN, DNS, Security, and Backup.

Read full post

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay