Mattermost v6.7 is now available
Mattermost v6.7 is generally available today and includes the following new features (see changelog for more details).
Mattermost v6.7 is generally available today and includes the following new features (see changelog for more details).
Ask any engineer what they’d like to eliminate from their daily to-do list, and the answer will almost certainly be some version of reducing toil. Engineering organizations can burn hours and hours of work time on repetitive, manual tasks that reduce bandwidth for high-impact projects. That being the case, it’s no surprise that reducing toil helps your team work more productively and experience better job satisfaction in the long run.
For teams who deploy software to users around the world, every second counts when responding to outages and other incidents. It’s important that you have tools in your arsenal that are up to the challenge. Service monitoring, alerting, collaboration, and visibility are all essential components of a well-implemented incident response plan.
Time and resource consumption have become the driving forces of developing modern applications. While building cloud-native applications, it’s important to ensure that you have the most optimized code in place, and oftentimes that means leveraging concurrency. While writing concurrent code may sound overwhelming at first, Golang makes it extremely easy to get a handle on.
Bringing the best software solutions to market as quickly as possible requires using automation to facilitate repetitive tasks (e.g., testing) so you can spend more time writing high-quality code. This is one of the main reasons why today’s top-performing dev teams build continuous integration (CI) and continuous delivery or continuous deployment (CD) pipelines, which enable them to ship new releases faster.
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.