Systems | Development | Analytics | API | Testing

APIs have revolutionized every industry. They fuel digital transformation and power the web, making up more than 83% of global internet traffic. And API adoption will only grow, with AI, Web3, and decentralization only further driving API usage and integration. But these sometimes-overlooked enablers of connectivity and communication present a serious security challenge: APIs are increasingly in the crosshairs of cyber-attackers.

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.

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.

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.

Take your API development skills to the next level with Go, Gin, JWT, and Gorm. Follow this detailed step-by-step guide to create robust, secure, and production-ready APIs that harness the power of authentication, authorization, and database integration.

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.