Two useful analogies for the V'bilt architecture:
- Per its namesake, V'bilt is a railway, or maybe the locomotive. It proceeds along its route, collecting train cars. What these cars actually do is opaque to the locomotive. The locomotive is only concerned with collecting the specified cars on its route. The whole train, ultimately, delivers a functioning Chord online storefront to the Internet.
As much as possible, then, V'bilt attempts to treat the store components themselves as entirely encapsulated. They indicate what inputs they need (resources, credentials, etc.), and V'bilt provides them.
V'bilt, then, manages the following responsibilities:
- orchestration
- config/secret management
- CI/CD
- build management tooling
- upgrade management
This maps pretty cleanly to K8s.