IBM Cloud Private vs. Linux Containers LXD

IBM Cloud Private is well suited for SaaS models.

Incentivized

Scenarios where you need an authentication server, a GIT repository the system works very well 'cause you don't need any scalability and the ease to configure and share the same Linux system image across the containers and the rollback process is quick. I didn't put any critical applications there not because of the limitations but due to a company policy.

Incentivized

• There is a large variety of services available on IBM Cloud.
• This is my first experience with a PaaS and I haven’t had any major problems navigating around it.
• It is easy to deploy applications and services on IBM Cloud.

Incentivized

• GIT repositories.
• Authentication servers.
• Application instances.

Incentivized

• More hands on training outside of virtual classes would be helpful.

Incentivized

• Ease of use.
• Copying containers from one machine to another.
• Creation of containers with config files similar to Docker.

Incentivized

With VMware cloud, each VMware Cloud customer must have an SDDC account(VMC) as well as a general AWS account. The two accounts must be linked for the service to work which is a tiresome thing to do for some clients but with IBM Cloud Private all these issues are solved.

Incentivized

Linux Containers LXD feels like a more primitive version of docker, docker-compose and similar projects from the docker ecosystem. The Dockerfile and docker-compose.yml methods of specifying a container setup, as well as the network and file configurations afforded by Docker make working with containers much easier and more reproducible than with Linux Containers LXD.

Incentivized

• N/A
• N/A
• N/A

Incentivized

• Quicker development cycles.
• Reduced need for different physical machines or servers.
• Standardized development environment.

Incentivized