CleanSlate Announces Strategic Partnership with Docker

CleanSlate Announces Strategic Partnership with Docker

At CleanSlate, we pride ourselves in being a leader in digital transformation. We work with cloud platforms such as AWS to modernize our customers’ applications and deliver ROI.

Docker is the market leading containerization platform that allows you to securely build and run your applications in any environment with speed. Docker has three components: software, objects and registries. The platform places software in isolated containers, which allows a company to manage and secure their legacy applications, as well as modernize their existing applications. The lightweight containers run simultaneously through on-premise, public cloud or private cloud at lightning speed.

We are excited to have a CleanSlate as a Docker partner. Their deep knowledge and skills in the areas of digital transformation, cloud and application migration make them a strong partner. 

Casey Watson

Vice President of Sales, Docker Central Region

CleanSlate helps our Clients modernize their applications, and accelerate their migration to the Cloud. We found Docker to be a critical component for our Clients who need a ubiquitous Container solution that plugs into modern DevOps CI/CD automations. We are proud to be a Docker Partner with our Clients.

David Reed

Senior Director of Business Development, CleanSlate

As a leader in the digital transformation space, we are always looking for the best tools and solutions to drive success for our clients. Docker is one of the leading solutions in this area, and we are proud to be a Docker partner. By being a partner, we are able to leverage their technology staff and their professional service team to help our clients get their applications deployed quicker, with higher reliability and maintainability. We have a team of certified Docker solution consultants at CleanSlate, and are able to utilize our partnership with the Docker team to provide the best solutions for our clients.

Comparing Swarm vs Kubernetes Terminology

Comparing Swarm vs Kubernetes Terminology

One of the things that my team and I are sticklers about is using the proper terminology for the proper technology. It’s just not the debate of “Principle” vs “Principal”, it’s the inferred technology that is applied by the terms you use. For instance, if a client told me they had a Docker Cluster, I might infer they are using Kubernetes, as that is correct terminology. When, in fact, they may be using Docker EE and should have used the term Docker Swarm.

Recently, when I was learning more about Docker EE Swarm at DockerCon ‘19, I started to realize the concepts are similar in Kubernetes, but the terminology was subtly different. I started to put together my own cheat sheet of similar components, so that I could keep things straight between the different sessions I attended. Now, I can speak both Swarm and Kubernetes without mingling terms, something my team will certainly appreciate!

Swarm Term Kubenetes Term Loose Definition
Swarm Cluster A group of machines that are running that provide high availability of containers.
Node Cluster Member Either a physical or virtual host that is participating within the Swarm/Cluster.
Manager Master Manages the strategy of how work is distributed within the Swarm/Cluster.
Worker (Worker) Node A participating member of the Swarm/Cluster that is providing compute capacity.
Container Container A standard unit of software that packages up code and all its dependencies, so the application runs quickly and reliably from one computing environment to another.
Task Pod A group of containers that are deployed together on the same host.
Service ReplicaSet Starts and manages the tasks/pods, ensuring the desired state.
Service Deployment Provides declarative updates to ensure the desired state is maintained.
Stack Stack A collection of services to run an application.
VIP ClusterIP Service The IP address representing the service definition.

Please contact us for your Docker needs.