Episode goal: zoom out. Connect the runtime model and the repository map to the story, and leave the viewer with a crisp mental model and a next step.
Cold open
On camera: “We started with a question — what are microservices for — and ended with a way to govern them. Let’s assemble the whole picture.”
The runtime
On screen: the recurring diagram, now complete — request →
ChenileExchange → interception pipeline (your policies) → pure implementation → back out. Voiceover: “The same exchange-and-pipeline model runs in the gateway and in each service. That single fact is what let one policy abstraction serve both the edge and the last mile.”The layers
Walk the layers:
chenile-parent (versions) → chenile-core (runtime) → blueprints (query-workflow, process-management) → integration (service-registry, proxies, security, messaging) → testing/aux (bdd, others) → cconfig.The 11 repos
Quick montage of the repository cards; pause on the four that carry the policy story:
chenile-core (the pipeline), chenile-security (the gateway), chenile-service-registry (placement), chenile-proxies/chenile-messaging (reach beyond HTTP). “Eleven repos, one release train, currently v2.1.29.”The five moves
Voiceover, brisk: “One: adopt services for deployability and ownership. Two: split definition from implementation. Three: turn horizontal concerns into policies. Four: place policies at the gateway and the last mile. Five: use one abstraction for both, with the registry choosing placement.”
And testing
Voiceover: “The same discipline covers testing. One Gherkin spec runs as a MockMvc unit test and a REST Assured integration test — behaviour written once, placement chosen by configuration.”
And messaging
Voiceover: “And events. Services depend on the
chenile-pub-sub interface; MQTT, Kafka, Azure and in-JVM are swappable behind it — and every message runs the same pipeline, so the same policies apply.”Config & the client side
Voiceover: “Even configuration follows the pattern —
cconfig gives modular, per-tenant, runtime overrides behind one client. And the interception idea reaches the client side: the proxy framework and service registry let you call any service through its interface, local or remote, with a client-side interceptor chain on the way out.”The thesis
Lower third: “Business logic stays pure. Governance stays consistent. Placement is configuration — not a rewrite.”
Call to action
“Generate your first service — episode four shows every command — read the five-part story on the site, and star the repos. Links below.”
Recap card
“Chenile: separate what a service does from how it’s governed — everywhere it runs.”
Companion reading: Architecture · The 11 repositories · The five-part story