Imagine you are sending a message to your friend, but you want to ensure that no one else can understand it. So lets say you are encoding your message using a special language that only you and your friend knows. This way, even if someone intercepts the message, they won't be able to understand its true meaning. The encoded message itself is what we call the "payload." In the world of APIs (Application Programming Interfaces), the concept of a payload is quite similar.

Step right up, ladies and gentlemen, and witness the grand spectacle of the digital age! In a world where data is king, where information reigns supreme, and cloud data warehouses are multiplying like rabbits, there's a technology initiative like no other— data warehouse modernization! This article is the second in the series "Seven Data Integration and Quality Scenarios for Qlik and Talend," and answers everything you wanted to know about data warehouse modernization but were afraid to ask.

In the past decade, chat apps have gone from being a disruptive new technology to something we use every day. Today, WhatsApp boasts over 2 billion daily active users, by far the market leader, followed by WeChat with 1.3 billion and Facebook Messenger at just under 1 billion. Chat apps, put simply, are going nowhere. In that time, customers have come to expect a consistent experience across their chat apps – and a core set of functionality has evolved across all major providers.

Picture this: during a bustling holiday season, a global e-commerce giant faces a sudden influx of online orders from customers worldwide. As the company's data pipelines navigate a labyrinth of interconnected systems, ensuring the seamless flow of information for timely product deliveries becomes paramount. However, a critical error lurking within their data pipeline goes undetected, causing delays, dissatisfied customers, and significant financial losses.

You’ve probably heard of the “shift-left” mantra as it echoes throughout the tech industry. And if you haven’t, let me be the first to update you that you’ve been living under a rock. Like a real rock, not even a figurative one. In all seriousness, ‘shift-left’ has shaken things up quite a bit in the tech industry, bringing with it a paradigm shift in how we approach software development.

We’re excited to announce that Kong is now working with Cloudsmith to host our community edition and enterprise edition gateway packages. With new hosting comes a couple of changes to how you, our loyal customers, will be receiving our software.

Is your organization currently relying on an ELK cluster for log analytics in the cloud? While the ELK stack delivers on its major promises, it isn’t the only search and analytics engine — and may not even be your best option for log management. As cloud data volumes grow, ELK monitoring can become too costly and complex to manage.

One of the hardest debates is deciding between a code-first API approach or design-first. In an ideal world, we would deliver our APIs at maximum velocity, with minimum maintenance. To maintain the appropriate API consumption, the world has looked at Amazon’s API Gateway as the orchestration of resources to create, deploy, and manage APIs at scale. One of the biggest challenges users face when using any API Gateway is the lack of consistency and standardization throughout the API experience.

Software testing and quality engineering (QE) are critical aspects of successful digital delivery in today’s fast-paced digital landscape. Many digital enterprises face challenges in achieving frictionless experiences, efficiency, and effectiveness in their QE journey.

Kong will crash on the ARM64 platform (the machine with Mac M1/M2 chips or any ARM64 platform). The error message shows the crash is triggered by the SIGILL signal, which means there is an illegal instruction in the Kong binary code. And it turns out to be caused by an error in the LuaJIT ARM64 JIT compiler. This post records how the error is found and fixed.