3 ms·
It can be tough to put these into production with autoscaling on the cloud. So if you need an application level load balancer with an ecs container with fargate
by shams93 8y ago
It can be tough to put these into production with autoscaling on the cloud. So if you need an application level load balancer with an ecs container with fargate on aws you're going to be limited to load balancing https requests there's no support for websockets on application load balancers. Part of this is that the cloud is not great at providing tools to deploy these applications. There are tools like firebase which just give you a realtime api to work with but rolling your own is tough when the tools on aws and azure are so biased towards old fashioned rest api deployment.
- happylamp 8y agoThats a really good point! It is interesting that support for websockets on a large scale is still quite limited when it comes to AWS/Azure/Google. Probably explains why SSE is more and more a viable alternative even though it has more overhead than websockets
- discreteproj 8y agoThat makes a lot of sense. I guess I would have expected cloud providers to push the industry into newer (but stable) technologies. As web dev continues to mature and becomes increasingly interested in fast, real-time, application development, I have to think that user demand will eventually force cloud providers' hands. That said, there are clearly other considerations at hand. I definitely think there's a market to provide services that support these protocols, of which Firebase is evidence. The only problem is Firebase, while great for smaller, quick projects, has some major issues at scale.