home.social

#apacheapisix — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #apacheapisix, aggregated by home.social.

fetched live
  1. #DRY is an important principle in software development. This post will show you how to apply it to #ApacheAPISIX configuration.

    blog.frankel.ch/dry-apisix-con

  2. #DRY is an important principle in software development. This post will show you how to apply it to #ApacheAPISIX configuration.

    blog.frankel.ch/dry-apisix-con

  3. #DRY is an important principle in software development. This post will show you how to apply it to #ApacheAPISIX configuration.

    blog.frankel.ch/dry-apisix-con

  4. #DRY is an important principle in software development. This post will show you how to apply it to #ApacheAPISIX configuration.

    blog.frankel.ch/dry-apisix-con

  5. #DRY is an important principle in software development. This post will show you how to apply it to #ApacheAPISIX configuration.

    blog.frankel.ch/dry-apisix-con

  6. When I introduce #ApacheAPISIX in my talks, I mention the massive number of existing plugins, and that each of them implements a specific feature. One of the key features of Apache APISIX is its flexibility. If a feature is missing, you can create your own #plugin, showcasing the platform’s adaptability to your specific needs. In this post, I aim to provide practical alternatives to writing a custom plugin, offering solutions you can quickly implement in your projects.

    blog.frankel.ch/when-write-api

  7. When I introduce #ApacheAPISIX in my talks, I mention the massive number of existing plugins, and that each of them implements a specific feature. One of the key features of Apache APISIX is its flexibility. If a feature is missing, you can create your own #plugin, showcasing the platform’s adaptability to your specific needs. In this post, I aim to provide practical alternatives to writing a custom plugin, offering solutions you can quickly implement in your projects.

    blog.frankel.ch/when-write-api

  8. When I introduce #ApacheAPISIX in my talks, I mention the massive number of existing plugins, and that each of them implements a specific feature. One of the key features of Apache APISIX is its flexibility. If a feature is missing, you can create your own #plugin, showcasing the platform’s adaptability to your specific needs. In this post, I aim to provide practical alternatives to writing a custom plugin, offering solutions you can quickly implement in your projects.

    blog.frankel.ch/when-write-api

  9. When I introduce #ApacheAPISIX in my talks, I mention the massive number of existing plugins, and that each of them implements a specific feature. One of the key features of Apache APISIX is its flexibility. If a feature is missing, you can create your own #plugin, showcasing the platform’s adaptability to your specific needs. In this post, I aim to provide practical alternatives to writing a custom plugin, offering solutions you can quickly implement in your projects.

    blog.frankel.ch/when-write-api

  10. When I introduce #ApacheAPISIX in my talks, I mention the massive number of existing plugins, and that each of them implements a specific feature. One of the key features of Apache APISIX is its flexibility. If a feature is missing, you can create your own #plugin, showcasing the platform’s adaptability to your specific needs. In this post, I aim to provide practical alternatives to writing a custom plugin, offering solutions you can quickly implement in your projects.

    blog.frankel.ch/when-write-api

  11. Lots of service providers offer a #freetier of their service. The idea is to let you kick their service’s tires freely. If you need to go above the free tier at any point, you’ll likely stay on the service and pay. In this day and age, most services are online and accessible via an #API. Today, we will implement a free tier with #ApacheAPISIX.

    blog.frankel.ch/free-tier-api-

  12. Lots of service providers offer a #freetier of their service. The idea is to let you kick their service’s tires freely. If you need to go above the free tier at any point, you’ll likely stay on the service and pay. In this day and age, most services are online and accessible via an #API. Today, we will implement a free tier with #ApacheAPISIX.

    blog.frankel.ch/free-tier-api-

  13. Lots of service providers offer a #freetier of their service. The idea is to let you kick their service’s tires freely. If you need to go above the free tier at any point, you’ll likely stay on the service and pay. In this day and age, most services are online and accessible via an #API. Today, we will implement a free tier with #ApacheAPISIX.

    blog.frankel.ch/free-tier-api-

  14. Lots of service providers offer a #freetier of their service. The idea is to let you kick their service’s tires freely. If you need to go above the free tier at any point, you’ll likely stay on the service and pay. In this day and age, most services are online and accessible via an #API. Today, we will implement a free tier with #ApacheAPISIX.

    blog.frankel.ch/free-tier-api-

  15. Lots of service providers offer a #freetier of their service. The idea is to let you kick their service’s tires freely. If you need to go above the free tier at any point, you’ll likely stay on the service and pay. In this day and age, most services are online and accessible via an #API. Today, we will implement a free tier with #ApacheAPISIX.

    blog.frankel.ch/free-tier-api-

  16. #RateLimiting is an age-old #ReverseProxy feature focused on protecting against DDoS attacks. It treats all clients the same and is purely technical. In this day and age, most #API providers offer different subscription tiers; the higher the tier, the higher the rate limit, and the more you pay incidentally. It’s not technical anymore and requires to differentiate between clients.

    In this post, I want to detail how to do it with #ApacheAPISIX.

    blog.frankel.ch/different-rate

  17. #RateLimiting is an age-old #ReverseProxy feature focused on protecting against DDoS attacks. It treats all clients the same and is purely technical. In this day and age, most #API providers offer different subscription tiers; the higher the tier, the higher the rate limit, and the more you pay incidentally. It’s not technical anymore and requires to differentiate between clients.

    In this post, I want to detail how to do it with #ApacheAPISIX.

    blog.frankel.ch/different-rate

  18. #RateLimiting is an age-old #ReverseProxy feature focused on protecting against DDoS attacks. It treats all clients the same and is purely technical. In this day and age, most #API providers offer different subscription tiers; the higher the tier, the higher the rate limit, and the more you pay incidentally. It’s not technical anymore and requires to differentiate between clients.

    In this post, I want to detail how to do it with #ApacheAPISIX.

    blog.frankel.ch/different-rate

  19. #RateLimiting is an age-old #ReverseProxy feature focused on protecting against DDoS attacks. It treats all clients the same and is purely technical. In this day and age, most #API providers offer different subscription tiers; the higher the tier, the higher the rate limit, and the more you pay incidentally. It’s not technical anymore and requires to differentiate between clients.

    In this post, I want to detail how to do it with #ApacheAPISIX.

    blog.frankel.ch/different-rate

  20. #RateLimiting is an age-old #ReverseProxy feature focused on protecting against DDoS attacks. It treats all clients the same and is purely technical. In this day and age, most #API providers offer different subscription tiers; the higher the tier, the higher the rate limit, and the more you pay incidentally. It’s not technical anymore and requires to differentiate between clients.

    In this post, I want to detail how to do it with #ApacheAPISIX.

    blog.frankel.ch/different-rate

  21. Last week, I described how to add a dynamic #watermark to your images on the JVM. Another alternative is to use ready-made components, namely #imgproxy and #ApacheAPISIX I already combined them to resize images on-the-fly.

    Here's how to achieve it:

    blog.frankel.ch/dynamic-waterm

  22. Last week, I described how to add a dynamic #watermark to your images on the JVM. Another alternative is to use ready-made components, namely #imgproxy and #ApacheAPISIX I already combined them to resize images on-the-fly.

    Here's how to achieve it:

    blog.frankel.ch/dynamic-waterm

  23. Last week, I described how to add a dynamic #watermark to your images on the JVM. Another alternative is to use ready-made components, namely #imgproxy and #ApacheAPISIX I already combined them to resize images on-the-fly.

    Here's how to achieve it:

    blog.frankel.ch/dynamic-waterm

  24. Last week, I described how to add a dynamic #watermark to your images on the JVM. Another alternative is to use ready-made components, namely #imgproxy and #ApacheAPISIX I already combined them to resize images on-the-fly.

    Here's how to achieve it:

    blog.frankel.ch/dynamic-waterm

  25. Last week, I described how to add a dynamic #watermark to your images on the JVM. Another alternative is to use ready-made components, namely #imgproxy and #ApacheAPISIX I already combined them to resize images on-the-fly.

    Here's how to achieve it:

    blog.frankel.ch/dynamic-waterm

  26. Nearly at the end of my two weeks marathon across Europe. This week was @berlinbuzzwords, DevConf CZ, and JavaDay Lviv 🇺🇦

    I came late at night and today, I’ll go to Lyon for Tech and Wine and conduct an #ApacheAPISIX workshop 🔨

  27. Nearly at the end of my two weeks marathon across Europe. This week was @berlinbuzzwords, DevConf CZ, and JavaDay Lviv 🇺🇦

    I came late at night and today, I’ll go to Lyon for Tech and Wine and conduct an #ApacheAPISIX workshop 🔨

  28. Nearly at the end of my two weeks marathon across Europe. This week was @berlinbuzzwords, DevConf CZ, and JavaDay Lviv 🇺🇦

    I came late at night and today, I’ll go to Lyon for Tech and Wine and conduct an #ApacheAPISIX workshop 🔨

  29. Nearly at the end of my two weeks marathon across Europe. This week was @berlinbuzzwords, DevConf CZ, and JavaDay Lviv 🇺🇦

    I came late at night and today, I’ll go to Lyon for Tech and Wine and conduct an #ApacheAPISIX workshop 🔨

  30. Nearly at the end of my two weeks marathon across Europe. This week was @berlinbuzzwords, DevConf CZ, and JavaDay Lviv 🇺🇦

    I came late at night and today, I’ll go to Lyon for Tech and Wine and conduct an #ApacheAPISIX workshop 🔨

  31. Recently, I had to use #GitHubPages to publish my #ApacheAPISIX workshop. Travis is no longer free. #GitHubActions are a thing. I used the now nominal path and faced a few hurdles; here are my findings.

    blog.frankel.ch/refresher-gith

  32. Recently, I had to use #GitHubPages to publish my #ApacheAPISIX workshop. Travis is no longer free. #GitHubActions are a thing. I used the now nominal path and faced a few hurdles; here are my findings.

    blog.frankel.ch/refresher-gith

  33. Recently, I had to use #GitHubPages to publish my #ApacheAPISIX workshop. Travis is no longer free. #GitHubActions are a thing. I used the now nominal path and faced a few hurdles; here are my findings.

    blog.frankel.ch/refresher-gith

  34. Recently, I had to use #GitHubPages to publish my #ApacheAPISIX workshop. Travis is no longer free. #GitHubActions are a thing. I used the now nominal path and faced a few hurdles; here are my findings.

    blog.frankel.ch/refresher-gith

  35. Recently, I had to use #GitHubPages to publish my #ApacheAPISIX workshop. Travis is no longer free. #GitHubActions are a thing. I used the now nominal path and faced a few hurdles; here are my findings.

    blog.frankel.ch/refresher-gith

  36. I continue to work on my #OpenTelemetry demo. Its main idea is to showcase traces across various technology stacks, including #asynchronous communication via an #MQTT queue. This week, I added a couple of components and changed the #architecture. Here are some noteworthy learnings; note that some of them might not be entirely connected to @opentelemetry

    blog.frankel.ch/even-more-open

    #Observability #DistributedTracing #ApacheAPISIX @graalvm #Golang #Ruby

  37. I continue to work on my #OpenTelemetry demo. Its main idea is to showcase traces across various technology stacks, including #asynchronous communication via an #MQTT queue. This week, I added a couple of components and changed the #architecture. Here are some noteworthy learnings; note that some of them might not be entirely connected to @opentelemetry

    blog.frankel.ch/even-more-open

    #Observability #DistributedTracing #ApacheAPISIX @graalvm #Golang #Ruby

  38. I continue to work on my #OpenTelemetry demo. Its main idea is to showcase traces across various technology stacks, including #asynchronous communication via an #MQTT queue. This week, I added a couple of components and changed the #architecture. Here are some noteworthy learnings; note that some of them might not be entirely connected to @opentelemetry

    blog.frankel.ch/even-more-open

    #Observability #DistributedTracing #ApacheAPISIX @graalvm #Golang #Ruby

  39. I continue to work on my #OpenTelemetry demo. Its main idea is to showcase traces across various technology stacks, including #asynchronous communication via an #MQTT queue. This week, I added a couple of components and changed the #architecture. Here are some noteworthy learnings; note that some of them might not be entirely connected to @opentelemetry

    blog.frankel.ch/even-more-open

    #Observability #DistributedTracing #ApacheAPISIX @graalvm #Golang #Ruby

  40. I continue to work on my #OpenTelemetry demo. Its main idea is to showcase traces across various technology stacks, including #asynchronous communication via an #MQTT queue. This week, I added a couple of components and changed the #architecture. Here are some noteworthy learnings; note that some of them might not be entirely connected to @opentelemetry

    blog.frankel.ch/even-more-open

    #Observability #DistributedTracing #ApacheAPISIX @graalvm #Golang #Ruby

  41. 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.

    blog.frankel.ch/pass-parameter

  42. 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.

    blog.frankel.ch/pass-parameter

  43. 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.

    blog.frankel.ch/pass-parameter

  44. 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.

    blog.frankel.ch/pass-parameter

  45. 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.

    blog.frankel.ch/pass-parameter

  46. 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.

    blog.frankel.ch/implement-idem

  47. 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.

    blog.frankel.ch/implement-idem

  48. 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.

    blog.frankel.ch/implement-idem

  49. 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.

    blog.frankel.ch/implement-idem

  50. 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.

    blog.frankel.ch/implement-idem