AIOps stands for artificial intelligence for IT Operations. AIOps, is a set of tools and algorithms that gather data from the entire IT environment, including different monitoring systems, log files and other IT data sources. It then analyzes and applies machine learning algorithms to determine the root cause of an incident. This means that instead of having to go through a long troubleshooting process by analyzing log files and manually looking for root causes, AIOps does it for you in minutes.

As defined by Amazon Web Services, DevOps is the integration of cultural concepts, practices, methods, and tools which allow an organization to provide services and applications at high speed: advancing and improving their products at a much faster rate than those using traditional software process for infrastructure management and development. This allows organizations to serve clients more effectively and compete in the market.

Developing a strategy for integrating data across your organization helps ensure that everyone has access to the most up-to-date data in a secure way. This article provides an example of a strategy you can use to develop your own. Despite the global digital acceleration of data use cases, many companies still struggle to be data-driven.

Apache Kafka is the de facto standard for event streaming use cases across industries. Many use cases can be applied to the aviation industry, too. Concepts like payment, customer experience, and manufacturing differ in detail. But in the end, it is about integrating systems and processing data in real-time at scale. For instance, omnichannel retail with Apache Kafka applies to airline, airports, global distribution systems (GDS), and other aviation industry sectors.

The Go standard library has fantastic support for making HTTP requests. However, sometimes, a request needs to be modified or an action needs to be taken upon response (eg. logging a response). In many cases, adding these logs to the every request would involve a lot of duplicate code. In other cases accessing the client might not be possible because of restricted access in a different package or third party library. Thus, I introduce RoundTrippers.

Spending two decades in the middleware field has given me deep insight into the evolution of this technology domain. I began my career as a software engineer in a platform group, building reusable components using technologies like object linking and embedding (OLE), the distributed component object model (DCOM) and common object request broker architecture (CORBA).

Maximizing the value of streaming data requires carefully navigating operational tradeoffs when developing and managing cloud native applications. Organizations that are rapidly producing and processing high volumes of data — like Netflix, Salesforce, Shopify and even the United States Postal Service (USPS), are constantly applying and testing new methods to manage the complexity of data streaming in the cloud.

Banking is about financial transactions. These are executed by sending payments and instructions over middleware. If you control the middleware, then you control the business. If the middleware fails, then the company fails. If you can see and analyze the transactions going through the middleware, you can see the business itself. And if you have real-time analytics of that data and it’s automatically actioned, then you can innovate and accelerate the company’s development.

Today’s enterprises can relate to this logic, especially concerning digital transformation projects. They have broken systems that need fixing, but they also spend a lot of effort fixing systems that don’t necessarily need those levels of intervention. Specifically, companies often face a dilemma: digital modernisation requires apps and systems to be upgraded and operate in the new technology norms. Yet those same systems often exist for good reasons.