Docker-Rocket Conflict is a Good Sign

Immediately, a discussion of uncertainty and doubt, and the familiar fear of thorn apprehension. Will this be the end of Doktor and a new beginning for container technology? Was this evidence that Doktor and other containers are still subjects of the open-source community, which is still not ready for enterprise?

Was it some time ago when some developers or organizations parted ways with their container technology from the Doktor community?

Some of these questions and claims are valid and poignant, while others indicate a lack of understanding of the history of open source software.

As I have previously written, the negative connotations of a fork, or confrontation in open source communities tend to be widely discussed and highlighted, but the fact of the matter is that these discussions and controversies are usually a definite of something else. The signs are: vitality.

Rocket launched

Rocket is another open source container technology, launched in late 2014, led by CoreOS, a provider of a lightweight Linux distro for running clusters and containers.

While CoreOS has claimed that it always has been, and continues to be a contributor and partner in the Docker community, it also claims that with its work and announcements in DockerCon Europe last year, Docker as a container company Is making a move towards technology. A platform rather than another component within today’s modern infrastructure and application software stack.

In my opinion Rocket marks the continuation of another imminent trend that continues to influence and disrupt enterprise IT: polyglot programming.

With different requirements between large enterprise and SP users and the different benefits of different components, today’s enterprise also requires many different moving parts – from application development and deployment: language and framework, databases, app servers, web servers – For infrastructure: including bare metal, traditional datacenters, virtual environments, and clouds … We now see the same for containers and container structures.

It is also worth noting that customers prefer when there is no open source option that is reliable, but there are many options. Examples include XN and KVM, Chef and Puppet, CloudStack and OpenStack and now perhaps Docker and Rocket.

Don’t mind

After talking to both Docker and Rocket’s backers and community members, it also seems clear that there is less bad blood than many think or illustrate.

The story of Docker and Rocket also bears some interesting meaning in terms of open source software and communities. The situation became slightly personal and political, but it is a healthy side effect of openness to air complaints, differences and possible reforms.

While many struggle to see these issues quickly and negatively or as a sign of trouble, it is also a sign of an important, working project and community.

The rocket will serve as a discipline on the docker to keep it more open and will probably also help with using drive features and functionality and other components (such as Systemed) and vice versa, as we have seen in different Linux distributions, Seen with hypervisors. And other techniques.

Leave a Reply

Your email address will not be published. Required fields are marked *