The latest News and Information on DevOps, CI/CD, Automation and related technologies.
We started building Mattermost because there was no collaboration solution on the market that fulfilled our engineering teams’ needs as game developers. These days, we’re a software development startup with many of the same needs, processes, and frustrations as our customers. Mattermost has been 100% remote from the beginning, with employees all over the world.
Thanks to a lot of hard work and excellent feedback from the open source community, Mattermost v6.0 is now generally available! This is a major platform upgrade with new capabilities and wider use case coverage, which many server administrators will be eager to take advantage of. Due to the scope of the changes introduced in v6.0, admins will want to plan ahead for a bit of downtime, especially for larger database migrations. Here’s a rundown of what’s new and what to expect.
This is the fourth (and second-last) part of our FinOps series - Optimize. Here is a list of posts in the series: Note: I am ex-AWS, so you will notice a lot more focus on AWS tools and services as examples here, however all cloud providers have similar services and tools.
In a previous post, we talked about the increasing adoption of Platform Engineering teams. The post covered topics such as defining Platform Engineering and the roles and responsibilities of the team. When building an internal platform, a clear goal that many teams want to achieve is: Even though this is key to a successful platform team, this responsibility increases complexity, costs, support time, and more. Not to mention that this can be a long, very long journey.