In 2020, JFrog’s experts published a treasure trove of content — blogs, articles, infographics, and more — to share insights and advice with our customers and the DevOps community at large. In case you missed them — or want to re-read them — here’s a list of the most popular ones. They range from a primer on container registries to an explainer on achieving high-availability for your Maven repository.

How many major versions of a given Go module are there? That simple question doesn’t always have an easy-to-discover answer. Golang’s unique system of semantic import versioning solves some key problems of ensuring Go module compatibility across dependencies. But it also makes it a bit harder to learn what major versions of a Go module are available. The go client doesn’t provide a way to find out, nor will it inform you when a newer major version of a dependency exists.

The SolarWinds hack, which has affected high-profile Fortune 500 companies and large U.S. federal government agencies, has put the spotlight on software development security — a critical issue for the DevOps community and for JFrog. At a fundamental level, if the code released via CI/CD pipelines is unsafe, all other DevOps benefits are for naught.

We get it, installing Artifactory and the JFrog DevOps Platform on Kubernetes can be daunting. As easy as we’ve sought to make it with our official JFrog installation Helm charts, there are a lot of decisions to be made. That’s meant to give you the widest possible choice for how to best fit your JFrog installation to your infrastructure. But choice can be overwhelming, too.

Continuous Deployment (CD) requires setting up your infrastructure and automation to update your solution with the latest code change from the main branch. That’s what we call “Liquid Software”. Full automation makes your deployment seamless, less error prone, faster and it makes the feedback loop shorter because you can now deploy after each change. Achieving continuous deployment requires the following elements.

Ownership isn’t for everyone — building and maintaining an abode is a lot of trouble when all you need is a place to hang your hat. That can also be true when you’re a creator of Helm charts. You’ll certainly want the benefits of a Helm chart repository to store, version, and share your charts for deploying applications to Kubernetes.

Research firm IDC has recently published an infographic (check it out below!) outlining the new requirements for modern software distribution and key guidance for organizations to meet future needs and overcome the bottlenecks in the next era of large-scale application delivery. With the advent of DevOps and modern delivery practices, organizations are becoming better at rapidly developing and deploying new applications to better serve their customers and stay competitive in today’s digital age.

If you’re using the JFrog DevOps Platform to manage your software artifacts, then there’s a good chance that one of the clients you’re already using is JFrog CLI. JFrog CLI is a robust tool, which enhances and extends the capabilities of the JFrog Platform, by connecting it to your build and automation agents.

Earlier this year, we launched ChartCenter, our newest community platform to help Kubernetes developers find Helm charts. This new free Helm central repository was built with chart immutability  in mind— meaning every version of a Helm chart and every version in ChartCenter will always be available even if the original source goes down.

We’re delighted to announce that, after a rigorous evaluation by the AWS Service Ready Program, JFrog Artifactory and Xray have been validated as following best practices for AWS Outposts. What additional engineering did we do to get our core DevOps solutions to perform on AWS Outposts? None at all. We’re proud of meeting AWS’s strict standards, but it was no surprise.