AWS Lambda VS Spot.io

Amazon Web Services (AWS) Lambda is a serverless function-as-a-service (FaaS) platform that lets you deploy, run, and scale code in the cloud as self-contained functions without having to manually configure any infrastructure. Lambda runs your functions on demand in response to specific events, such as an HTTP request from the internet or activity in another AWS service. - Source: dev.to / 3 days ago

FaaS is specifically focused on building and running applications as a set of independent functions or microservices. Major cloud providers like AWS (Lambda), Microsoft Azure (Functions), and Google Cloud (Cloud Functions) offer FaaS platforms that allow developers to write and deploy individual functions without managing the underlying infrastructure. - Source: dev.to / 15 days ago

So AWS Lambda is basically a serverless computing service that is offered by AWS. It enables developers to run the code in response to various events. It protects the developers from the pain of managing the servers. Using a serverless execution model helps the developers to handle provision, manage and scale the servers automatically. Through this approach the developers can fully focus on writing the code... - Source: dev.to / 28 days ago

The first product that popularized the term “serverless” was AWS Lambda, which is both the prototypical and archetypical function as a service provider. It also has a great name, which pings back to its envisioned place in the cloud of the future. In computer programming, a lambda, often referred to as a lambda function or lambda expression, is a concise way to represent an anonymous function, which is a function... - Source: dev.to / 3 months ago

You can build a custom config rules in 2 ways, using AWS Lambda and CloudFormation Guard. Lambda gives you a lot of flexibility, but it also brings complexity of maintaining. CloudFormation Guard is a bit more lightweight in that regard. Yes, you still need to maintain the logic to determine when your resource is compliant or not. But you need to do this in both cases, thus my go to preference is CloudFormation... - Source: dev.to / 3 months ago

+1 In my previous stint, I had worked with Spot (https://spot.io/) as one of our vendors. Absolutely great product, amazing customer support and ability to take feature requests, or otherwise address our pain points quickly and effectively. - Source: Hacker News / 12 days ago

FWIW, I am also a big spot.io fan for our workload. During the holidays I run 30-50% spot instances and run 100% spot most of the year. Source: over 1 year ago

Also, you definitely should look into Reservations, and (sale pitch coming) Spot can help you manage those. Source: over 1 year ago

All of this is on spot-instances. We used spot.io (I believe the product is called "Ocean") and they basically took care of all the backend logic to make spot-instances available for the ECS cluster. Source: about 2 years ago

Does cloud provider matter? I would say/think so. Not just cloud provider, but further more, how you set it up, which begets cloud provider. Are you setting it up with only the aws cli? Or did you terraform it? Maybe you chose a particular terraform module or maybe you used eksctl. Maybe you used kops or kubeadm. All these things matter when you get to cluster autoscaling, tainting particular node types to... Source: almost 3 years ago