In a new research paper, Mary Johnston Turner, IDC research vice president for cloud management, explains why cloud-native applications and infrastructure require modern observability. IDC's research shows that 97 percent of global enterprises use connected cloud strategies that depend on a diverse mix of on-premises, off-premises, hosted, edge, and public cloud infrastructure.

This month, I made the decision to join CloudZero as their new chief revenue officer — a choice I’m incredibly excited about. In the past week, a number of colleagues have asked me to share why I joined the company. After answering the question a few times, I decided to take a minute to collect my thoughts and explain why this incredible company is the next step in my career.

We’re excited to announce a suite of new capabilities designed to help IT teams build cloud-native applications with confidence.

In the first part of this article, we mention that at the moment, you have three options for you to start developing your Logic Apps: And we already analyze the advantages, disadvantages, and how to start developing Logic Apps by using the Azure Portal and Visual Studio. Today we are going to do the same but this time using Visual Studio Code.

With cloud computing growing at a phenomenal rate across the world, shifts in consumer behavior towards digital services are resulting in evolutionary changes for the banking, financial services and insurance industry. Cloud-based banking, for example, is regarded as a catalyst for business transformation and a turning point in financial services. Cyber safety, however, has become a key concern holding back cloud adoption in many organizations.

It’s safe to say that cost per tenant (also known as cost per customer) on AWS has been a challenging metric to obtain. Until now, your best bet has usually been to either make a best guess or build some sort of homegrown system. As of November 4, 2020, when you google “cost per tenant,” you get a few things at the top of the page. The first is a couple of blogs by AWS, where they describe an extraordinarily complex system, which you can build yourself.

For many years after the inception of Compute Engine on June 28, 2012 (GA December 2, 2013), N1 was the only Google Cloud machine type family offered.

Last month, inspired by JamstackConf I built Jamstackery.website. This mini-site runs on AWS, and is managed by our platform. Our hope is that this mini-site demonstrates the promise of an architecture that blends containers with functions, and all the supporting certificates, permissions, and resources necessary to provide a world-class infrastructure.

The cloud is here—and so are its acronyms. Since software as a service (SaaS) hit the world in 2001, the ‘as a service’ model has been extended to just about everything you can think of. Along the way, the definition has become a little muddied. It used to be that -aaS meant something delivered on a subscription basis via the cloud, without a physical component.

Do you know how much it costs to operate your software per customer, at each pricing tier? The past six months have been highly unusual to say the least. For some companies, the disruption and shift to work from home meant 100x in usage almost overnight; for others usage completely collapsed in the same time period. These sharp swings in utilization have been disruptive to cloud unit economics. Both scenarios are risky and require extreme elasticity from the technical infrastructure.