OpenNext VS Spot.io

However, CT3A initialized the tRPC client to use new HTTP streaming features, which are still unstable. Moreover, streaming is still considered experimental with both OpenNEXT adapter (internal part of nextjs-web resource) and AWS Lambda (on which the Next.js app will run). - Source: dev.to / 21 days ago

No they don't, hence projects like https://open-next.js.org/ and the multitude of stories of 3rd party serverless offerings being half-broken. They also keep breaking at time goes on since they're playing catch up on the build output: https://www.reddit.com/r/nextjs/comments/1685dyr/avoid_aws_amplify_at_all_cost_its_fraud/ https://www.reddit.com/r/nextjs/comments/160ui01/is_aws_amplify_good_for_hosting_nextjs/... - Source: Hacker News / 6 months ago

The default refrain rears its head again. Next.js and Vercel heavily push serverless deployment: 13 reworked the built-in API support to leverage Web Standards, which discarded interop with the a much larger server ecosystem in order to enable better edge support. Serverless deploys require providers to support the Next.js Build API:... - Source: Hacker News / 7 months ago

I'm currently waiting SST v2 to be released where they will use https://open-next.js.org instead of https://github.com/serverless-nextjs/serverless-next.js. Source: over 1 year ago

However you might like to look at https://open-next.js.org or https://sst.dev. Source: over 1 year 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