ArchiTECHt Daily: Is the container war even winnable?

Some folks call the fight for users among the various container technologies "the container wars," bu
ARCHITECHT
ArchiTECHt Daily: Is the container war even winnable?
By ARCHITECHT • Issue #38
Some folks call the fight for users among the various container technologies “the container wars,” but with each passing month the fight looks more one-sided. And the Cloud Native Computing Foundation is coming out on top, evidenced by yesterday’s news of Docker contributing the containerd project, and CoreOS contributing its rkt technology, to the foundation.
By “Cloud Native Computing Foundation,” of course, I mean Kubernetes. At least for the time being. The CNCF was created originally as a neutral home for Kubernetes, and now plays host to a bunch of complementary technologies, as well. Its original membership of a handful of container-focused companies has expanded to dozens of vendors and even some big end-users.
There’s almost too much history to unpack here, but the very short version is that as Docker the company grew, it started building more stuff into Docker the open source project, a move that rubbed many users and ecosystem players the wrong way. This led to competing technologies (including rkt) and, ultimately, the Open Container Initiative, which helped spur a stripped-down, industry-standard container format and runtime (runC). containerd, a stripped-down, modular version of the original Docker daemon, manages runC.
Here is some background reading (and I mean a tiny sampling from a huge body of work) on some of the technologies and business factors at play:
The CNCF came about separately (although both are Linux Foundation projects), but really is fruit of the same tree as far as Docker is concerned. Whether it was Google’s original intention or not, Kubernetes helped further the notion that containers themselves should be dumb, modular commodities. Let the orchestration platform do all the work; no need for any company’s bloat or other funkiness in the containers themselves. 
To Docker’s credit, it has been instrumental in helping launch the OCI and—clearly, with the submission of containerd—to helping advance the CNCF causes. But I would argue this hasn’t always been by choice. Docker—borne and bred of open source—has to listen to its community or risk taking an incredible amount of flak. Or, worse yet, risk losing users and coming down on the wrong side of history.
In fact, Docker’s completely understandable (and, arguably, necessary) decision to compete against Kubernetes with Swarm, and integrate that into the core Docker components, only exacerbated calls for an alternative.
When I say that CNCF is winning the container wars, I’m not suggesting it’s doing so by playing unfairly or even, really, by fighting. It’s able to determine the pieces of the cloud-native stack because it has a large community, good technologies and is just so damn open. Even Kubernetes, the CNCF’s linchpin project, is no longer just a Google joint; one of its creators is managing container services at Microsoft, and the other two started a Kubernetes company called Heptio. 
When you say “Kubernetes” you are not, in fact, implying any specific vendor. You could be talking about the open source project, or any of the various distributions and services built upon it. Being bigger than any one vendor is critical to any open source project that’s aiming for revolutionary impact.
Companies that develop what the container community calls “boring infrastructure” aren’t forced to join the CNCF or donate their technologies to it, but it sometimes might feel like they don’t have a choice. You can either try to become an anointed component of the new application stack and hope it results in paying customers, or you can go it alone against one of the world’s most-popular open source projects and the technologies pulled in by its gravitational field. If you don’t contribute that that core functionality, someone else probably will.
I guess what I’m trying to say is that open source coopetition and modularity are great for users, but not always great for the companies involved. There is huge opportunity in front of every company in the container space right now, but with the CNCF seemingly calling the rules of the game, everyone else needs to play their cards very carefully and (at the risk of mixing metaphors) always look a few moves out to see where they’ll be competing, differentiating or assimilating down the road.

Sponsor: Datos IO
Around the web: Artificial intelligence
I remain cautiously pessimistic about Salesforce’s AI ambitions. But if there’s one thing Marc Benioff knows how to do, it’s sell a vision.
Computation can get expensive, just like reading a Harper’s article can suck up an entire Sunday. Sometimes you need to know when to skim. (Oh, yeah, and a reminder that Salesforce does have some smart AI folks.)
metamind.io  •  Share
You see, now, why Intel is dropping major cash on getting into this space. Also, the world could use some smarter dishwashers, Bosch.
Speak of the devil. Here’s a deeper look into how Mobileye’s technology works.
A note to other large companies trying to establish a reputation as an AI leader: Do this kind of stuff all the time.
These are fine for techies, but we really need a way to visualize this stuff for the rest of the world. I’ve kind of given up on data literacy becoming a thing.
This man is doing the lord’s work and someone should build a Chrome plugin like this. He wouldn’t have to if legitimate news sites would stop writing bad headlines.
You don’t hear too much about question-answering systems anymore, like the original Watson one. Just sayin’.
arxiv.org  •  Share
Optimizing deep learning models is still a lot of work, so why not create a system that do it by itself?
arxiv.org  •  Share
Around the web: Cloud and infrastructure
Smart, smart, smart way to leverage both of its industry-leading platforms and have them feed off each other. Hopefully it results in some must-have skills beyond timers and controlling lights.
GitLab wants to own code management by taking on GitHub, Jenkins and more. Gitter, the chat startup it acquired, offers some interesting possibilities around collaboration and building communities.
If you’re serious about defense, then you should be serious about science and the Department of Energy. 
And it’s not because of altruism. Microsoft sees that if it wants to reap the benefits of the OCP community, it has to play along. Azure will be better as a result.
Sponsor: Marshal.io
Around the web: All things data
I left that headline in its original form because it’s damn compelling. These “experts” largely have vested interests in Hadoop not being the answer, but they also have some good points.
Come for the well-designed user experience, stay for the “‘misuse’ [that] is a primary driver of Splunk’s continued adoption.” Hey, if it technically works …
This is a fun map—if you’re really into distributed data stores.
I don’t actually know a lot about BlueData, but it seems like I should …
Did you enjoy this issue?
ARCHITECHT
The most interesting news, analysis, blog posts and research in cloud computing, artificial intelligence and software engineering. Delivered daily to your inbox. Curated by Derrick Harris. Check out the Architecht site at https://architecht.io
Carefully curated by ARCHITECHT with Revue. If you were forwarded this newsletter and you like it, you can subscribe here. If you don't want these updates anymore, please unsubscribe here.