Welcome to the 8th edition of Open Source Matters: our regular publication about the latest happenings in open source! Let’s dive into the news.

Most products that run as Software-as-a-Service (SaaS) are built to be multi-tenant, meaning that a single instance or deployment is meant to be used by multiple organizations. There’s a good reason for this: it’s generally easier to scale and operate multi-tenant applications. But in this new age of containers, orchestration, infrastructure-as-code, and Kubernetes, where it’s cheaper, faster, and simpler to deploy a new instance of an application, that may no longer be the case.

puppetlabs-pe_status_check is a new supported module for Puppet Enterprise. It provides a series of indicators of system status that the Puppet Support team has determined to avoid support incidents or outages. Utilizing this module and the accompanying documentation will allow the user to craft preventative maintence workflows and, should it still be required, increase the quality of information in any support ticket, to help decrease the time to resolution for any incident.

The path to success in software development can be long and challenging. It requires a lot of skills and dedication as it’s not just about building applications, it’s so much more. It is also about being tailored for any situation, requiring us to be quick to adapt to change and to the unexpected.

In the Kubernetes (K8s) community, there is a huge misconception about CPU allocation and utilization. Even highly experienced SREs find themselves struggling with the way Kubernetes allocates CPU resources, leading to misconfigured CPU allocations and extremely negative outcomes. For starters, this results in significant quality degradation on important service components, introduced by behind-the-scenes CPU limiting (or throttling).

In this tutorial, you will learn how to work with the gRPC Golang library for microservice communication by creating a simple note-taking application. APIs and service-to-service communication are what make modern microservice architecture possible. REST is generally the preferred implementation pattern, but if you only use REST, you could miss out on the significant performance gains that gRPC can offer. gRPC can provide better speed and efficiency than REST APIs.