In the age of cloud native modernization many have focused on methods for driving better feature velocity, but without additional consideration for resiliency and runtime behavior, many such projects are struggling. Often, we hear of CIOs and CTOs being hired to drive better feature velocity to only later discover they were fired due to some resiliency issue. So how can you achieve better feature velocity without compromising resiliency? In this talk we venture into the role of modern distributed runtimes that can deliver a declarative approach to the resiliency problem. As an application owner, you should be able to trace the overall performance of user transactions in specific geographic locations, from the time a user clicks on an application to the time the transaction is completed, regardless of the number of distributed cloud services that transaction uses. More importantly, instead of contending with multiple “tuning knobs” to achieve such quality of service, the cloud runtime gives you the ability at deployment time to state the service level objectives (SLOs) and service level indicators (SLIs) you expect from the system.