Modules, not a monolith: Labs64.IO as standalone Helm charts
“Platform” is an overloaded word. For some vendors it means a monolith with feature flags: you take all of it or nothing. For others it means a pile of microservices that you wire together yourself, paying for authentication, routing and configuration again for every service. Neither is a good deal if you only need one capability today and want to add more later.
Let the gateway own your API version prefix
Most HTTP APIs carry a version in the URL: /api/v1/orders, /v2/customers. It looks harmless, but that short string ends up in many places: in every client, in the OpenAPI spec, in every controller annotation and in the routing rules in front of the service. When version 2 arrives, all of them have to move together, and anything that is missed returns a 404.
Vibe-Coding GammaLedger: My Experiment in AI-Powered App Building
The Genesis: From Spreadsheet Hell to Purposeful Architecture
Securing Microservices with Keycloak and Traefik AuthProxy
An auth proxy is a specialized service that centralizes authentication and authorization for multiple microservices. Instead of implementing security logic in every service, you can use a single proxy to handle these concerns at the edge. The Traefik Auth Proxy is a great example of this pattern, using Traefik’s forwardAuth middleware to intercept requests and enforce access policies.
Configuring Traefik Middleware for Kubernetes
Traefik is a powerful cloud-native ingress controller that uses Middleware to modify requests before they’re sent to your services. Middleware can handle crucial tasks like authentication, rate limiting, and header manipulation. By using Helm charts to manage your Traefik configuration, you gain a declarative, version-controlled, and reusable approach that’s perfect for a microservice environment.
Spring Cloud Gateway Routing for Microservices
Spring Cloud Gateway is a powerful API gateway that efficiently routes incoming traffic to the appropriate downstream microservices. At its core, this functionality relies on routes, which are the fundamental building blocks that define how requests are handled. Understanding how to configure these routes is essential for building a robust and scalable microservice architecture.