Enterprise Integration Patterns Aren't Dead; They're Running on Kubernetes and Orchestrating AI

Enterprise Integration Patterns Aren't Dead; They're Running on Kubernetes and Orchestrating AI Keip is a Kubernetes operator for Enterprise Integration Patterns. Gregor Hohpe and Bobby Woolf documented these patterns in 2003: content-based routers, message transformers, splitters, aggregators, dead letter channels. Spring Integration has implemented them for years, but deploying Spring Integration on Kubernetes has always been harder than it should be. Keip fixes that. It turns integration routes into native Kubernetes resources, and I use it to run an LLM-powered media analysis pipeline on my home cluster. Why I Built It The problem is deploying Spring Integration in Kubernetes. The traditional workflow is: write Java, compile, build a container image, push to a registry, deploy. For every route change, the whole cycle repeats. Adding a filter step, restructuring routing logic, or wiring in a new output channel was indistinguishable from a logic change: same build cycle, same contain