Read the new white paper on major incident management. Businesses need to be prepared for minor and major incidents to happen to their technologies, be it an integration disconnecting or an entire system being taken offline. Preparation ensure that not only can losses be minimized, but they can protect themselves and potentially their clients from risky impacts.
In this article, you will learn about some of the tools to test microservices running in a Kubernetes cluster. In particular, we will compare the Speedscale CLI tool with other tools and the main benefits of using Speedscale CLI. In the last few years, software companies have been shifting from building monolith applications to utilizing smaller microservices. In a microservices architecture, you operate with decentralized applications. This means that there's a separation in which each service is responsible for a specific component of your application.
In order to answer this question, it is best to first explain what is IBM MQ and the benefits that it can bring to a business. IBM MQ (Messaging and Queuing) is a messaging system that enables applications running on different computers to communicate quickly with each other in real-time. This is achieved by exchanging messages using queues, and processed as and when computing resources and internet bandwidth allow. IBM MQ has been designed to provide high availability and reliability and can be used in a variety of different environments, including cloud computing.
This is Part 2 of a two-part series on Blameless Postmortems. The previous article went into why blameless postmortems are so effective; this second part goes into detail on how to build your own postmortem process and kick it into overdrive. Read Part 1 here. So you've read our first installment and recognized the value of the blameless postmortem for efficiency, culture, and output. Now you're ready to get off the blame train and kickstart a blameless postmortem process of your own. Where to begin?