I recently read a post on "6 Ways To Pass Parameters to #Spring#REST API". Though the title is a bit misleading, as it’s unrelated to REST, it does an excellent job listing all ways to send parameters to a Spring application. I want to do the same for #ApacheAPISIX; it’s beneficial when you write a custom plugin.
Last week, I wrote an analysis of the #ITEF#Idempotency-Key specification. The specification aims to avoid duplicated requests. In short, the idea is for the client to send a unique key along with the request:
If the server doesn’t know the key, it proceeds as usual and then stores the respons
If the server knows the key, it short-circuits any further processing and immediately returns the stored response
This post shows how to implement it with #ApacheAPISIX.
I lastly stumbled upon a list of 16 practices to secure your #APIs. In this two-post series, I’d like to describe how we can implement each item with #ApacheAPISIX (or not).
On Foojay :foojay: Today, @frankel of #ApacheAPISIX describes the options for #versioning HTTP APIs: path-based, query-based, and header-based. Check them out and be consistent across your organization:
Another alternative to chop the monolith, by @frankel#apacheapisix "Instead of forking the call on the client side, we fork the call on the Gateway side." Source code included on Foojay :foojay: Today.
"A long time ago, #observability as we know it didn't exist; what we had instead was monitoring." Check out @frankel 's of #ApacheAPISIX latest post, this time on the #OpenTelemetry Collector, which sits at the center of the OpenTelemetry architecture.
In a few words, the idea of #canaryreleases is to deliver a new software version to only a fraction of the users, analyze the results, and decide whether to proceed further or not.
In this post, I’d like to detail this introduction briefly, explain different ways to define the fraction, and show how to execute it with #ApacheAPISIX.