Spot.io VS Replay.io

+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 / 15 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

Not at this time. I'm pretty full up at this point with day job ( https://replay.io ), conferences, and personal life stuff. My current ongoing Redux maintenance task is trying to revamp our "Redux Essentials" tutorial to be TS-first. Making slower progress on that than I'd wanted, but hopefully can get that wrapped up in the not _too_ distant future. Beyond that, we've got a ton of open RTK Query feature requests... - Source: Hacker News / 5 days ago

Exactly - that's what we've already built for web development at https://replay.io :) I did a "Learn with Jason" show discussion that covered the concepts of Replay, how to use it, and how it works: - https://www.learnwithjason.dev/travel-through-time-to-debug-javascript Not only is the debugger itself time-traveling, but those time-travel capabilities are exposed by our backend API: -... - Source: Hacker News / 3 months ago

I made a Replay recording of the sandbox:. Source: 11 months ago

Hiya folks! In addition to all my free time spent working on Redux, answering questions, and modding this sub, my day job is working on Replay.io. Today we're thrilled to announce our new Replay for Test Suites feature, which lets you record and time-travel debug Cypress (and Playwright) E2E tests as they ran in CI! Source: 11 months ago

FWIW, the Firefox devs who were doing the WebReplay time travel debugging POC weren't, as far as I know, fired. Instead, they left and started Replay ( https://replay.io ), a true time-traveling debugger for JavaScript. I joined Replay as a senior front-end dev a year ago. It's real, it works, we're building it, and it's genuinely life-changing as a developer :) Not sure how well this would have fit into Firefox... - Source: Hacker News / 12 months ago