ServerlessConf NY this past October was an important milestone for those of us tracking how software is built on cloud services. . We’ve seen the serverless talks evolve from “what is serverless” to “I built a weird thing” to “We built a new business” to “We refactored a legacy app and kickstarted our feature velocity.” We’ll come back to those last two soon, , but I want to highlight some points from one in particular by Tim Wagner.

IDC predicts a ten-fold increase in data by 2025, which should surprise just about no one. We are all producing more and more data every day—more data than ever before, with no slowdown in sight. Recently we joined forces with our friends over at CHAOSSEARCH to deliver a webinar on the topic of Big Data Done Right—How to Spend Less While You Store & Analyze More. In this webcast, we discussed some best practices around big data storage, transfer, and access.

Since Kubernetes was open sourced by Google in 2014, it has steadily grown in popularity to become nearly synonymous with Docker orchestration. Kubernetes is being widely adopted by forward-thinking organizations such as Box and GitHub for a number of reasons: its active community, rapid development, and of course its ability to schedule, automate, and manage distributed applications on dynamic container infrastructure.

Digitalization is sweeping across many industries, creating a huge need for innovation. This innovation forces companies to be more agile and deliver faster. However, increasing the speed of your development team doesn’t happen by magic. It’s a metric that isn’t easy to change. How can you adjust to this fast-paced digitalization? I want to introduce you to DevOps.

Have you ever been in charge of your company’s observability stack? Does the pain of implementing, configuring, scaling, and maintaining (oh, and correlating the data between) various monitoring, troubleshooting, and security tools resonate with you? If so, you might be our next tech evangelist – our next DevOps Evangelist!

AIOps is a new solution to an age-old problem: How do I stop my team from going insane managing 15 million different tool consoles? The tool bloat problem is not new for anyone who has been in this business for more than a minute. In the old days, when IT teams were comprised of specialists in servers, storage, networking, databases and so forth, each group of specialists had a favored tool set that showed them how their little patch of the world was functioning.

The k3s project was started by Darren Shepherd, Chief Architect at Rancher 7 months ago and has already become one of the most popular Kubernetes options on the CNCF Landscape by number of GitHub stars. To put this into context, k3s is more popular than OpenShift by IBM/Red Hat and only Rancher Kubernetes itself is more popular than k3s. Now stars are indicative of interest and popularity only and that should be noted.