The database/sql package in the Go standard library maintains a pool of connections so that all queries going through a single *sql.DB instance will reuse the same pool. This is great because you get a connection pool out of the box. But what if you need to share the same connection pool across processes? How do you use the same API in different processes but still reuse the same pool?

Ask any software engineer about the best way to do something and they’ll likely tell you “it depends.” Every project and team works differently and has specific concerns, requirements, and opinions, adding complexity on top of the technical and operational complexity of software development. The challenge lies in managing the work and emergent complexity while staying abreast of industry best practices in a way that fits our teams’ particular processes and environments.

In case you missed it, insurtech — technology developed to improve and transform the insurance industry — is having a bit of a moment. Forrester recently reported record-breaking funding for insurtechs, closing Q3 at $15 billion – more funding than in 2019 and 2020 combined – with more deals anticipated by the end-of-year.

In the first part of this series, we explored the fastest way to get started with Mattermost Apps. In the second installment, we looked under the hood of a Mattermost App and examined how it works and how its components interact with each other. In this piece, we’ll outline the various authentication methods available using the Mattermost Apps framework.

Recent news about Log4j has enterprises and vendors scrambling for information and answers, including customers of messaging middleware and Integration Infrastructure Management (i2M) products. Nastel Technologies customers will not be exposed to any risks from this vulnerability, but enterprises are encouraged to check with their Cloud and other solution vendors to protect themselves and their data.

Mattermost v6.2 is generally available today and includes the following new features (see changelog for more details).

The Internet of Things (IoT) is a term that describes the increasingly sophisticated ecosystems of online, connected devices we share our world with. The slightly odd name refers to the fact that the first iteration of the internet was simply a network of connected computers. As the internet grew, phones, office equipment like printers and scanners, and industrial machinery were added to the internet.

In a recent blog post, I introduced the tech stack our Mattermost Technical Writing team uses every day to build, contribute to, improve, and maintain the Mattermost product documentation at docs.mattermost.com. Building on this knowledge, I’d like to share more about how we work as a writing team, the branching strategies we’ve learned to adopt, and the review workflows every documentation contribution goes through before being merged into the codebase.

There’s little doubt that cloud computing is now the absolutely dominant force across enterprise computing. Most companies have switched from buying their own hardware and software to renting both from vendors who host their services in vast anonymous data centers around the globe.