apisix-ingress-controller
Spring Boot
apisix-ingress-controller | Spring Boot | |
---|---|---|
33 | 167 | |
944 | 72,870 | |
0.7% | 0.7% | |
8.7 | 10.0 | |
10 days ago | 6 days ago | |
Go | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
apisix-ingress-controller
- Apache APISIX: A dynamic, real-time, high-performance API gateway
-
Implementing the Idempotency-Key specification on Apache APISIX
This post shows how to implement it with Apache APISIX.
-
3 Tips for Deploying APISIX in Kubernetes (Part 1)
APISIX Ingress Controller is a tool focused on API management, offering high performance and flexible configuration options. If you require more complex routing rules, rate limiting, circuit breaking, and other advanced features, APISIX Ingress Controller may be a better choice. It provides a rich plugin system, allowing integration of plugins through APISIX Ingress CRD using declarative configuration to handle authentication, authorization, monitoring, logging, and other functionalities. This enriches the capabilities of APISIX Ingress Controller and simplifies configuration.
-
Hardening Apache APISIX with the OWASP's Coraza and Core Ruleset
In this post, I'd like to describe how to fix some of them via the Apache APISIX API Gateway.
-
Mastering APISIX Health Checks: Active and Passive Monitoring Strategies
In the era of digitization, the availability and stability of services are crucial for the success of enterprises. As a key component of microservices architecture, the API gateway plays a significant role. APISIX, an open-source API gateway platform, ensures the continuity and stability of services through its health check mechanism.
-
2023 in retrospective
Next February will mark the two-year milestone that I'm working for: API7.ai on Apache APISIX. I'm still very pleased about both. It allows me to do things I like a lot, such as writing posts and giving talks.
-
Five Apache projects you probably didn't know about
In early 2021, I started to work on the Apache APISIX project. I have to admit that I had never heard about it before. In this post, I'd like to introduce some Apache projects that are less well-known than HTTPD or Kafka.
-
Apache APISIX plugin priority, a leaky abstraction?
Apache APISIX is an API Gateway, which builds upon the OpenResty reverse-proxy to offer a plugin-based architecture. The main benefit of such an architecture is that it brings structure to the configuration of routes. It's a help at scale, when managing hundreds or thousands of routes.
- Building a starter pack for an API-as-a-Service
-
10 Common API Resilience Design Patterns with API Gateway
API resilience is about building robust APIs that can withstand a variety of challenges, ensuring that they continue to function effectively. API Gateways play a key role in this, acting as the entry point for external requests and managing the communication between different services by taking into account common API resilience patterns. One of the popular open-source API Gateways, Apache APISIX, provides a variety of features to enhance the resilience and robustness of APIs. In this article, we will explore 10 common API resilience design patterns and how they can be implemented using APISIX.
Spring Boot
- JHipster 8 - Analisando o código da nossa primeira aplicação monolítica - Parte 2/3
-
Walmart is migrating the remaining F# code into Java
- Usually manually wired and configured vs the spring boot "starter" pattern of having libraries that automatically do some of the manual setup work for you: https://github.com/spring-projects/spring-boot/blob/main/spr...
I wish more client library sets had the feature-matrix that the pulsar one does, because in practice most end up being the same: Java supports everything because it's either built in the same codebase or is the most used client and gets the most support, while the dotnet client codebase has many feature-requests or performance improvement issues, often leading to a "third-party client" being created.
- AI PR adds auto generated comments to whole Spring Boot Project
-
AI commented the entire Spring Boot codebase
https://github.com/spring-projects/spring-boot/pull/39754/co...
-
Spring Boot 3 And Java 17 Migration Guide
If you’re currently running with an earlier version of Spring Boot, I recommend that you upgrade to Spring Boot 2.7 before migrating to Spring Boot 3.0. It minimizes compatibility issues as much as possible.
- Spring Boot 3.2.0 Release Notes
-
The Game of Life, the Universe, and Everything: Java Virtual Threads in Action
Okay, we need to build the game? No problem, we will use Spring Boot and Swing!
-
Netflix Uses Java
It's weird that some people including you directly attack my competence. As a power user you should have plenty of experience getting something to work that is not properly document, does not work how the documentation promised it to, or has weird problems on top of it. Look at idiotic things like this:
https://github.com/spring-projects/spring-boot/issues/33044
Take any similar issue and you'll see a bunch of people who try to find a solution for them because they just aren't repeatable at all. The underlying issue is the auto configuration doing things you can't follow quite properly. It's like it wasn't mean to be understood. Issues like the one I linked above also show me that the spring dev crowd also doesn't understand the ecosystem anymore. The problem is complexity and automagic.
-
What's New in Spring Framework 6.1
An interested reader can decide for themselves:
https://github.com/spring-projects/spring-boot/tree/main/spr...
-
Secure Java URL encoding and decoding
Explicitly decoding URL query parameters occurs less often because many frameworks, including Spring Boot, handle decoding automatically.
What are some alternatives?
ingress-nginx - Ingress-NGINX Controller for Kubernetes
helidon - Java libraries for writing microservices
envoy - Cloud-native high-performance edge/middle/service proxy
Play - The Community Maintained High Velocity Web Framework For Java and Scala.
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
javalin - A simple and modern Java and Kotlin web framework [Moved to: https://github.com/javalin/javalin]
IngressMonitorController - A Kubernetes controller to watch ingresses and create liveness alerts for your apps/microservices in UptimeRobot, StatusCake, Pingdom, etc. – [✩Star] if you're using it!
Quarkus - Quarkus: Supersonic Subatomic Java.
apisix - The Cloud-Native API Gateway
Jooby - The modular web framework for Java and Kotlin
ingress-merge - Merge Ingress Controller for Kubernetes
ZK - ZK is a highly productive Java framework for building amazing enterprise web and mobile applications