Kitchens¶
In DataKitchen's DataOps Automation, users perform all work within virtual workspaces called Kitchens.
Kitchens are where teams can build, manage, and run pipelines that provision infrastructure and do data work. Think of kitchens as factories that contain assembly lines called recipes.
Every customer has a single master kitchen from which all static and sandbox working kitchens are branched. Kitchens are hierarchical in nature and their underlying version control branches hold hierarchical relationships. This means that users can create child kitchens, generating exact copies of the parent kitchen's recipes.
Tip
Kitchen types: Design your kitchens to be static or used as a sandbox. Static kitchens are permanent workspaces, while sandbox kitchens are temporary or ephemeral. For more information, see Set Kitchen Type.
Centralized connections¶
DataKitchen data pipelines, called recipes, often connect to many infrastructure or toolchain instances as data is extracted, loaded, and transformed. The system supports a shared definition of these infrastructure connections, facilitating rapid recipe development and iteration.
Isolated infrastructure¶
Each kitchen can be configured so its recipes run on, and connect with, infrastructure associated with specific environments. This is done by defining infrastructure connections as part of the kitchen workspace definition.
In this way, customers can have Production, Hot Fix, User Acceptance Testing, Proof-of-Concept, Development, and Feature Sprint environments that are isolated from one another.
Rapid creation and teardown¶
Users can create and tear down child kitchens quickly and easily to experiment with ideas, separate software/data environments, isolate feature branches, and clean up disposable work.
For example, kitchens associated with release environments and user-specific kitchens can exist indefinitely. Kitchens associated with hotfixes, feature development, or experimentation can be ephemeral.