For realtime, I used Pushpin with Server Sent Events. (It supports WebSocket as well). - Source: dev.to / 11 months ago

Instead of letting clients directly interface with your services over websockets, consider using Pushpin [1], which allows you to completely isolate realtime communication from your services. As a bonus, it also provides you the ability to cycle (redeploy/restart) your services without your clients having to reconnect (that's where the name comes from). And as you can imagine - because communication with your... - Source: Hacker News / about 1 year ago

Vapor[0] based on Swift. Advantage of this is that you don't have to evaluate multiple frameworks for Swift and suffer paralysis by analysis. All the Swift community is behind one framework. The next is Actix[1] based on Rust. There are many frameworks in Rust and most of them have not reached 1.0 And which framework will survive becomes a question. Other not so well-known is Wt[2] based on C++. This actually is... - Source: Hacker News / over 1 year ago

If you are developing the backend then Pushpin[0] is the easiest to integrate with. [0] https://pushpin.org. - Source: Hacker News / over 1 year ago

There is also the option of running a proxy which handles the stateful nature of websockets (i.e. https://pushpin.org/), and then handle the rest in a stateless way with lambdas or similar. 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 / about 2 months 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