Tutum vs kaniko: What are the differences?

# Introduction
Tutum and Kaniko are two popular tools in the world of containerization and container management. While both serve similar purposes, there are key differences that set them apart in terms of functionality and usage.

1. **Build Context**: Tutum utilizes a Dockerfile with the entire context, including source code, dependencies, and configuration files, to build an image. On the other hand, Kaniko enables users to build container images from a Dockerfile without needing a Docker daemon or root access, making it suitable for secure and efficient image building in environments where Docker is restricted.

2. **Image Layering**: Tutum uses Docker's layering feature to create container images, which can result in larger image sizes due to multiple intermediate layers. In contrast, Kaniko employs a single-stage build process, eliminating unnecessary intermediate layers and producing smaller, more streamlined container images.

3. **Parallelism**: Kaniko supports parallel building by default, allowing for faster image builds by utilizing multiple CPU cores efficiently. In contrast, Tutum does not have built-in support for parallel building, which may lead to longer build times for large and complex projects.

4. **Caching Mechanism**: Tutum relies heavily on Docker's caching mechanism to speed up subsequent builds by reusing previously built layers. Kaniko, on the other hand, offers a more customizable caching mechanism that allows users to control caching at different stages of the build process, enhancing build performance and flexibility.

5. **Build Environment**: Tutum requires a running Docker Daemon on the host system to build container images, which may pose security risks and resource constraints in certain environments. Kaniko, being a tool that operates inside an unprivileged container, eliminates the need for a Docker Daemon and provides a more secure and isolated build environment.

6. **Compatibility**: Tutum is tightly integrated with Docker and relies on Docker's APIs and features for building and managing container images. In contrast, Kaniko is a standalone tool that does not depend on Docker or Docker registries, making it compatible with various container orchestration platforms and workflows beyond the Docker ecosystem.

In Summary, Tutum and Kaniko differ in their build context, image layering, parallelism, caching mechanism, build environment, and compatibility, offering users unique features and advantages in container image management and deployment.