How much of your database workload is going to be in a public cloud?

My company closed down several of our datacenters and has a directive that all new projects are cloud based.   We keep a small 2-6 node VMware cluster in every warehouse/shipping facility for the apps they use because latency really sucks for their scanners.  We spend a staggering amount of money for it but the leadership is hoping that the cloud first strategy will drive change in the organization.  It certainly did drive a lot of turnover,  so maybe that counts? 

My company closed down several of our datacenters and has a directive that all new projects are cloud based.   We keep a small 2-6 node VMware cluster in every warehouse/shipping facility for the apps they use because latency really sucks for their scanners.  We spend a staggering amount of money for it but the leadership is hoping that the cloud first strategy will drive change in the organization.  It certainly did drive a lot of turnover,  so maybe that counts? 

Last Summer we moved to a new data center, it wasn't the boards first choice of where we needed to go. 4 years ago they asked us to price out moving to the cloud. We modeled a 100% shift, a 'only a few things' on prem, and a 50% move and 100% on prem for 2, 5 and 10 year forecasts total cost of ownership. The dev work to get 100% in the cloud took too long, so its cost was outrageous, but also impossible. Get 'lots' to the cloud was do-able to shrink our footprint in the data center, but if you need some on-premise, you can get a lot of bang for your buck by leveraging some of the same tech that AWS and Azure do. The new data center looked cheap compared to moving a significant workload. That said, we are hybrid, and compute workloads get evaluated routinely to see where they should be. Mostly its feast and famine stuff and stuff with little ties to other systems that make sense today.