Operations | Monitoring | ITSM | DevOps | Cloud

The best way to stay out of danger is to keep far away from where danger lurks. But in the internet age, the global network means risk to your systems is from everywhere, at all times. With estimates that worldwide damage from cybercrime will exceed 6 trillion dollars by 2021, many companies choose, or are required by regulations to isolate their most sensitive systems to avoid any type of security breach.

With any huge task, more helpers make it go faster. That’s the solution large organizations increasingly seek for deploying large applications to hundreds of nodes. When others pitch in, many hands make light work. JFrog is pleased to introduce Peer-to-Peer (P2P) Distribution to help deliver content to huge K8s cluster runtime environments efficiently and at scale.

All developers have seen them, even in well-structured Golang programs: comments suggesting you keep away from lines of code since they seem to be working in a magic way. These warnings make us timid, fearing we might break something. But applications need to change, to improve and innovate. That’s why unit tests are a vital part of software development. They help developers know whether the small parts of their software perform their intended function correctly.

Robert Greiseimer has called Go the language of cloud computing and while it’s no secret that Go has strong features that support the needs of microservice architecture, distributed systems, and large-scale enterprise applications, what is less talked about is that Go was also built with web development in mind from the start. In fact, many developers in the community are using Go for full-stack development and championing new modules and frameworks that make Go a strong language for the web.

Today is a momentous day for JFrog, as we’re excited and proud to join the Nasdaq family of listings. While COVID-19 challenges every company and prevents us from being together in many ways, we’re humbled that Times Square was turned green today! This is obviously an important milestone, and it couldn’t have happened without over a decade of hard work and millions of hours that have gone into this amazing company.

ChartCenter is a free Helm chart central repository that was built to help the Helm community find immutable, secure, and reliable charts for publicly available Kubernetes apps. With ChartCenter, you have a single source of truth to proxy all public charts from one, always available location. Without ChartCenter, you need to add each Helm chart’s repository to the Helm client for every Kubernetes app you want to install and update.

For the last four years, anyone wanting to deploy the Ingress NGINX Controller for Kubernetes would find its official Helm chart nginx-ingress in the stable repository maintained by the Helm project. Those days are over. And not just for NGINX, the most popular Ingress Controller used as a reverse proxy and load balancer, but for all open-source K8s apps. With the advent of Helm 3, the Helm project is deprecating the stable repositories.

The growth of Kubernetes has been stellar and K8s applications have grown in importance and complexity. Today, even configuring a single application can require creating many interdependent K8s sources that each depend on writing a detailed YAML manifest file. With this in mind, Helm as a package manager for Kubernetes is a major way users can make their K8s configurations reusable.

Using an open-source Go module from the community of other developers can be like going on a blind date. That “getting to know you” phase that can be awkward and risky. The more you know in advance, the better off you’ll be, right? When using software, having accurate and precise documentation is one of the most important aspects. Good software documentation tells the story of what a particular piece of code does and how to use it.

Introducing, adding, or replacing a new SCA (Software Composition Analysis) tool such as JFrog Xray into your SDLC, if not handled correctly, can be very disruptive to the SDLC and organization. This blog post provides recommended best practices for onboarding JFrog Xray; in order to reduce disruption, improve adoption, and shift left to create a DevSecOps behaviour.