Strange Loop Conference | "Avoiding the Pitfalls of Autoscaling with Constant Work" by David Grizzanti (Strange Loop 2022) @StrangeLoopConf | Uploaded 1 year ago | Updated 3 hours ago
The idea of auto-scaling, geo-redundancy, and high-availability for internet applications has been around for a number of years, however, many of the traditional scaling and failover patterns overlook regional outages and cascading failures. The most common practices have applications scale as demand increase or in the case of regional outages.
If you've ever wondered if there is an alternative way to manage these risks, this talk is for you!
We'll look at the concept of constant work as an alternative to scaling on-demand and avoiding cascading failures when systems fail. Particularly, we'll dig into systems that implement this idea of constant work, how to deal with the trade offs of scale and cost, and where may be good areas for you to invest in this idea.
Lastly, we'll dig into a concrete example by showing off a system with both methods implemented to test our theory in practice!
David Grizzanti
The New York Times, Principal Engineer
@dgrizzanti
David Grizzanti is a Principal Engineer at The New York Times focused on improving developer productivity by enabling engineering teams to more effectively and efficiently build, test, integrate and deploy software. Previously he was a Distinguished Engineer at Comcast, where he oversaw the development of multi-tenant software platforms that support tens of millions of customers across North America. His areas of interests include improving infrastructure automation, open source communities, and engineering leadership.
-------- Sponsored by: --------
Stream is the # 1 Chat API for custom messaging apps. Activate your free 30-day trial to explore Stream Chat. https://gstrm.io/tsl
The idea of auto-scaling, geo-redundancy, and high-availability for internet applications has been around for a number of years, however, many of the traditional scaling and failover patterns overlook regional outages and cascading failures. The most common practices have applications scale as demand increase or in the case of regional outages.
If you've ever wondered if there is an alternative way to manage these risks, this talk is for you!
We'll look at the concept of constant work as an alternative to scaling on-demand and avoiding cascading failures when systems fail. Particularly, we'll dig into systems that implement this idea of constant work, how to deal with the trade offs of scale and cost, and where may be good areas for you to invest in this idea.
Lastly, we'll dig into a concrete example by showing off a system with both methods implemented to test our theory in practice!
David Grizzanti
The New York Times, Principal Engineer
@dgrizzanti
David Grizzanti is a Principal Engineer at The New York Times focused on improving developer productivity by enabling engineering teams to more effectively and efficiently build, test, integrate and deploy software. Previously he was a Distinguished Engineer at Comcast, where he oversaw the development of multi-tenant software platforms that support tens of millions of customers across North America. His areas of interests include improving infrastructure automation, open source communities, and engineering leadership.
-------- Sponsored by: --------
Stream is the # 1 Chat API for custom messaging apps. Activate your free 30-day trial to explore Stream Chat. https://gstrm.io/tsl
