Operations | Monitoring | ITSM | DevOps | Cloud

Today we’re announcing the general availability of Longhorn, an enterprise-grade, cloud-native container storage solution. Longhorn directly answers the need for an enterprise-grade, vendor-neutral persistent storage solution that supports the easy development of stateful applications within Kubernetes. We’ve been working on Longhorn for almost as long as we’ve been around as a company.

With Day 1 of the event rolled up, the platform was all set for the next day of the event. Day 2 of Integrate 2020 has been one roller-coaster experience for the attendees with some amazing sessions and certainly, loads of updates from the Microsoft Product Team and MVPs. So, for those who missed it out, make use of this blog.

This blog is an extraction of the session “Event-Driven Microservices with Azure Functions, Event Grid and Cosmos DB” presented by Martin Abbott, who is Azure MVP, Regional Director. We need to first have a deep understanding of all the services and components that are used to create the End to End application.

INTEGRATE has become part of our company culture since we started it back in 2013. We created a place for all Microsoft Integration people from across the world to get together and share experiences. This year, considering the Covid situation, we made a big decision to take INTEGRATE 2020 into a virtual conference with a new branding called “INTEGRATE 2020 REMOTE”. If you wish to get redirected to blogs based on each session on day 1 of the event, here is the quick guide to help you out.

In my Puppet travels over the last 10 or so years, one topic has continued to arise time and again, and that has been the ability to scale open source Puppet to thousands of nodes. While the best route is to use Puppet Enterprise for solid support and a team of talented engineers to help you in your configuration management journey, sometimes the right solution for your needs is open source Puppet.

In a previous article, we discussed KUDO and the benefits of it when you want to create or manage Operators. In this article we will focus on how to start to work with KUDO: Installation, using a predefined Operator and create your own one. Installing KUDO To install KUDO the first step is to install the CLI plugin in order to manage KUDO via CLI. Depending on your OS you can use a package manager like Brew or Krew, however installing the binary is a straightforward option to proceed.

With a near-endless list of Go Modules, it can be overwhelming trying to decide which is best for your Go build. For new Go developers, it can be difficult to pick a winner for your specific use case. This phenomenon is nothing new. In fact, it’s one of the reasons why open-source is so important for developers. Oftentimes, when a module is published by a developer, it was likely developed to solve a specific problem that they are facing.