Welcome To Cloud Native Now!

Today, we rebranded our Container Journal publication to Cloud Native Now. This was a move that was a long time coming. Since we launched Container Journal a few years ago, the cloud-native community has evolved and grown to become so much more than just containers–the name just no longer fit the mission. Cloud Native Now is a much better fit.

Let me give you a little history about how Container Journal started and how we ended up at Cloud Native Now. When I came back from what was possibly the second DockerCon in Seattle, I told our team at DevOps.com that Docker containers were going to change the way software was run. This was not just based on Solomon Hykes’ presentation at the time but on the enthusiasm of developers and ops folks—they were eager for this change; it was just what they had been looking for. The enthusiasm and energy of that community was palpable.

Step 1 of 7

14%

Which of the following best describes how you currently monitor and manage systems across your hybrid cloud environment?(Required)

Multiple separate tools for different environments

Multiple separate tools for different monitoring and management functions

Single consolidated dashboard

Custom built monitoring and management solution

No full monitoring and management solution

Don’t know

How valuable would it be for your monitoring and management solution to incorporate predictive analytics to help you identify and address system issues that are critical and not waste time or effort working through all the data and “noise” that is not critical?(Required)

Extremely valuable

Moderately valuable

Somewhat valuable

Slightly valuable

Not valuable

How do you most typically address potential system issues BEFORE they impact your operations?(Required)

Automated workflows and playbooks to remediate potential issues as soon as they are detected

An orchestrated response process that leverages automation, AI, and human expertise to rapidly respond to potential issues

Advanced monitoring tools such as predictive analytics and anomaly detection to proactively identify and address potential issues

Respond to issues as they arise, using manual processes and troubleshooting techniques

A combination of automated remediation, orchestrated response, and/or proactive monitoring to address potential system issues

Don’t know

Other

What methods does your organization use to control and monitor cloud/IT spending?(Required)

Centralized procurement processes

Pre-approved budget thresholds

Automated cost monitoring tools

Department-level spending controls

Regular cost audits and reviews

Cloud cost optimization platform

Approval workflows for resource provisioning

Native financial operations tools provided by the cloud provider

No formal controls in place

Don’t know

Other

Please specify:

Which methods do you rely on most to detect security vulnerabilities in your systems?(Required)

Automated scanning tools

Manual assessments

Vendor notifications

Threat modeling (for early detection)

None of these

Don’t know

Other

Please specify:

What are the TWO most common ways you prioritize vulnerabilities to address within your environment?(Required)

Based on potential impact

Based on exploitability

Regulatory compliance requirements

Based on CVSS scores

Risk-based analysis of multiple factors

First-in-first-out approach

No formal prioritization process

Don’t know

How do you typically handle system updates and security patches?(Required)

Automated updates and patches

Manually review and apply updates and patches on a regular schedule

A combination of automation and manual review

Apply updates and patches on an as-needed basis.

Outsourced update and patch management

No defined process

Don’t know

Other

Δ

We decided we should consider spinning off a separate site dedicated to the community solidifying around Docker containers. While we considered names and mapped out launch plans, I went to the next DockerCon, this one in Austin, Texas. After that event, I again gathered the team and told them this thing called Kubernetes from Google was going to be the manager for Docker containers. At that point, I was pretty sure the central piece of this whole new way of deploying and managing software was going to be around building, orchestrating and managing containers. So Container Journal was born.

Check out this conversation between Alan Shimel and chief content officer Mike Vizard discussing the history of Container Journal and the evolution to Cloud Native Now!

I was not totally wrong in my opinion, but as usual, I wasn’t totally right, either. I missed the totality of the cloud-native movement and the totally new stack of solutions it spawned. Cloud native is so much more than containers and Kubernetes today. 

We saw this even before the COVID-19 pandemic at the KubeCon + CloudNativeCon in San Diego, California in 2019. I think that was when the cloud-native movement really took off. The pandemic has not dampened this movement. Today security, data and observability are all thriving parts of the cloud-native world.

Going forward, Cloud Native Now will continue to cover the totality of the cloud-native landscape. We look forward to its maturation and growth. We think this is the most dynamic and enthusiastic community we cover here at Techstrong Group, and we hope you’ll continue to explore all the exciting developments in cloud native along with us!