Talk of what to do with legacy systems often causes angst among leaders. Retiring the system means lost functionality that might be too difficult to replace. Keeping it means more time spent on maintenance rather than value-added tasks. Replacing it can be a financial and logistical nightmare. The result of these talks is often to simply keep it and make do as best as possible.

Application programming interfaces (APIs) are fast becoming the global standard for automated data exchange between and within companies. When a company first launches APIs, an adjacent step is to set up an effective system for automating API planning and implementation. But beyond that, as companies grow and expand their API use, the central challenge becomes figuring out how to best position APIs for scale as multiple, distributed teams build APIs across business units, often around the world.

Standardized a decade ago through RFC 6455, WebSocket has since matured into one of the main technologies powering the modern web. Designed to be event-driven and full-duplex, and optimized for minimum overhead and low latency, WebSockets have become a preferred choice for many organizations and developers seeking to build interactive, realtime digital experiences that provide delightful user experiences.

Boomi, previously known as Dell Boomi, is a well-known software provider for enterprise integration. It manages all the information and data that needs to flow between different companies, systems, and applications. Boomi products are designed to offer the best possible performance with the lowest possible latency. However, not everyone can afford or has room in their budget for this particular product.

In this episode of Kongcast, I spoke with Grant McKeen and Jonathan White from IntegrationWorks about how open banking and BIAN (Banking Industry Architecture Network) work with Kong Gateway to create simplicity from complexity in the banking and financial services industry. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.

gRPC is a remote procedure call framework that has been widely adopted among cloud native applications. It is an attractive choice for engineers needing more capabilities than what REST APIs provide. However, observability and testing tools for gRPC are few and far between. Because of this, triaging or understanding application behavior is potentially time-consuming and overly burdensome.

Many organizations that already rely on Integration Platform as a Service (iPaaS) to integrate applications question the necessity of an API management system. The question of which to use over often confuses. So which one is the best choice? The answer is both. Here we’ll discuss why an Integration Platform as a Service alone isn’t enough. Companies will need to embrace both iPaaS and API management to achieve the true agility and innovation they need to remain competitive.

Microservices have an entirely new set of problems due to their distributed service-oriented architecture. As a result, microservice design patterns have surfaced. This post will consider the specific design patterns that can help us build reliable, secure and traceable microservices.

Modern-day applications aim to cover a wide range of users’ needs in a flexible and scalable manner. The software development landscape is moving at a fast pace, and the competition is so fierce that a business simply can’t afford to offer a low-quality product. Thorough testing of both functional and non-functional aspects of a software application has become an essential step in the software development process. It ensures that users get the best version of your product.