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.
Heroku is a cloud-based platform that helps companies build, deliver, monitor, and scale applications with high velocity. Heroku's popularity is due to its simplicity, usability, elegance, and focus on the developer experience. Developers find Heroku helpful as they can get their application ready and running with only minimal focus on configuring infrastructure. Heroku scores on easiness in architecting apps, deploying them to flexible cloud infrastructure, and scaling them as required.
Many organizations aspire to a world where everything is in the cloud. But, in reality most IT enterprises still rely on traditional on-prem monitoring technologies. As a market-leading monitoring tool, SCOM is ideally placed for the job; monitoring both on-prem workloads or workloads that link up to the cloud. So, as SCOM is central to most companies’ monitoring, it is essential you understand how to be successful with SCOM!
Understanding the relationship between Service Management and Project Management is a topic of interest for many people because, at first glance, both techniques appear to be competing for the same workspace in many organizations. They are critical practices for every business to develop and prosper. So, although project management and service management may sound similar, there are several key distinctions between the two concepts.
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.
