Drawing a parallel to the React revolution in frontend development, this article explores how shifting from Separation by Technology to Separation by Concerns can solve the modern infrastructure bottleneck. Learn how BigConfig uses a component-based approach to unify Kubernetes, Terraform, and Ansible, enabling modularity, interchangeability, and a “clean interface” for your entire stack.
Terraform and Ansible often struggle with true cross-provider portability. BigConfig Package bridges this gap, allowing developers to deploy both stateful and stateless applications seamlessly across any hyperscaler, from Oracle Cloud to Hetzner.
Greenspun’s Tenth Rule warns that every complex system eventually reinvents a buggy version of Lisp. From YAML-hell in CI/CD to the “accidental” programming languages of Helm, Terraform and Ansible, the DevOps world is living this prophecy. Discover how shifting from rigid configuration to the power of Clojure and BigConfig can help you escape the trap of ad-hoc infrastructure logic.
BigConfig Package moves beyond the “Kubernetes-only” mindset of Helm by treating infrastructure and software as a single unit. By replacing specialized CLIs with Babashka (Clojure), it eliminates the friction between shell scripts and compiled binaries. This approach allows developers to move seamlessly between a CLI, a REPL for debugging, and a library for deep automation.
