{"id":105,"date":"2019-06-06T18:53:28","date_gmt":"2019-06-06T22:53:28","guid":{"rendered":"http:\/\/redmonk.com\/kfitzpatrick\/?p=105"},"modified":"2019-06-06T18:55:17","modified_gmt":"2019-06-06T22:55:17","slug":"some-takeaways-from-dockercon-2019","status":"publish","type":"post","link":"https:\/\/redmonk.com\/kfitzpatrick\/2019\/06\/06\/some-takeaways-from-dockercon-2019\/","title":{"rendered":"Some Takeaways from DockerCon 2019"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-106\" src=\"http:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-Expo-Entrance-e1559854436586-1024x681.jpeg\" alt=\"Entrance to the DockerCon 2019 Ecosystem Expo Hall. The doorway is marked with a sign and flanked by Docker mascot whales hanging from the ceiling.\" width=\"1024\" height=\"681\" srcset=\"https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-Expo-Entrance-e1559854436586-1024x681.jpeg 1024w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-Expo-Entrance-e1559854436586-300x199.jpeg 300w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-Expo-Entrance-e1559854436586-768x510.jpeg 768w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-Expo-Entrance-e1559854436586-1536x1021.jpeg 1536w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-Expo-Entrance-e1559854436586-480x319.jpeg 480w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-Expo-Entrance-e1559854436586-943x627.jpeg 943w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-Expo-Entrance-e1559854436586.jpeg 2016w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">One of the best parts about being an analyst: you get to choose the experiential framework from which you analyze a given piece of tech or event. Events, especially, offer us a myriad of lenses. At a keynote you can choose to sit up front in a section reserved for press and watch the reactions on the faces of the executives nearby; you can also sit in the back with the rest of the crowd and see if the cheers\/jeers from the proverbial peanut gallery match those in the rest of the room. You have the option of staying ensconced in analyst program events, often with access to a special press room; alternatively, you can pop into a given session and experience it as would most other attendees. You can measure the temperature of an event based on who you end up chatting with at lunch, see what the vendors at the expo have to say, or get an often outside view of an event from non-conference meetings with clients who happen to be in the area.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I had all of these options available to me last month when I attended (and <\/span><a href=\"https:\/\/www.docker.com\/dockercon\/2019-videos?watch=media-and-analyst-q-a-on-emerging-trends-and-the-role-of-con\"><span style=\"font-weight: 400;\">spoke on a panel<\/span><\/a><span style=\"font-weight: 400;\"> at) DockerCon 2019 in San Francisco. The moment that stands out the most for me\u2014the one that provided the framework through which I evaluated the rest of the conference\u2014was my morning walk from my hotel to the first day\u2019s keynote on Tuesday. I fell in step with an attendee who was making the same trek. While I do not recall his name, his reason for attending the conference sticks out in my mind: although he looked forward to the keynotes and other talks, he was there primarily for the Thursday\/Friday training sessions. His organization had selected Docker as their path for modernizing their existing applications, and he had been tasked with learning how to make this happen. This chance interaction pushed me to view DockerCon beyond the crafted announcements and hype, the showmanship and cocktail receptions, to the business of what Docker\u2014as a company and a technology\u2014enables. From this perspective here are my DockerCon 2019 takeaways.<\/span><\/p>\n<h1><span style=\"font-weight: 400;\">Modernization is still big business<\/span><\/h1>\n<p><span style=\"font-weight: 400;\">As my walking comrade indicated, many organizations arrive at Docker as a solution for legacy app modernization and\/or lift-and-shift. In a continuation of a theme <\/span><a href=\"https:\/\/redmonk.com\/jgovernor\/2018\/07\/16\/some-thoughts-on-docker-post-dockercon-2018\/\"><span style=\"font-weight: 400;\">my colleague James noted from last year&#8217;s conference<\/span><\/a><span style=\"font-weight: 400;\">, DockerCon 2019 had numerous sessions and customer case studies dedicated to legacy application transformation. Indeed, even the <\/span><a href=\"https:\/\/www.docker.com\/dockercon\/2019-videos?watch=retro-gaming-with-docker\"><span style=\"font-weight: 400;\">Retro Gaming session<\/span><\/a><span style=\"font-weight: 400;\"> I attended included a nod to the business of legacy collateral. <\/span><\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">\u201cIt doesn\u2019t get much more legacy than this&#8230;\u201d <a href=\"https:\/\/t.co\/jnCnaQtNAC\">pic.twitter.com\/jnCnaQtNAC<\/a><\/p>\n<p>&mdash; Dr KellyAnn Fitzpatrick (@drkellyannfitz) <a href=\"https:\/\/twitter.com\/drkellyannfitz\/status\/1123373174098399233?ref_src=twsrc%5Etfw\">April 30, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p><span style=\"font-weight: 400;\">Strategically, one of the best customer stories I heard at DockerCon came from Don Bauer and Mike Noe of Citizens Bank speaking about their team\u2019s containerization journey. The <\/span><a href=\"https:\/\/en.wikipedia.org\/wiki\/There_and_Back_Again_(disambiguation)\"><span style=\"font-weight: 400;\">Tolkien-esque<\/span><\/a><span style=\"font-weight: 400;\"> title of their public session, <\/span><a href=\"https:\/\/www.docker.com\/dockercon\/2019-videos?watch=from-swarm-to-kubernetes-and-back-again\"><span style=\"font-weight: 400;\">From Swarm to Kubernetes (and Back Again)<\/span><\/a><span style=\"font-weight: 400;\">, captures the following ordered movements at Citizens Bank:<\/span><\/p>\n<ol>\n<li><span style=\"font-weight: 400;\">November 2016: begin containerization strategy using Swarm, resulting in the first production cluster in April 2018. <\/span><\/li>\n<li><span style=\"font-weight: 400;\">November 2018: migrate some \u201cCore\u201d data services to Kubernetes (via Docker Enterprise); reasons cited include <\/span><a href=\"https:\/\/helm.sh\/\"><span style=\"font-weight: 400;\">Helm<\/span><\/a><span style=\"font-weight: 400;\">, <\/span><a href=\"https:\/\/coreos.com\/operators\/\"><span style=\"font-weight: 400;\">Operator patterns<\/span><\/a><span style=\"font-weight: 400;\">, and \u201cvendor pressure\u201d. <\/span><\/li>\n<li><span style=\"font-weight: 400;\">January 2019: move these services back to Swarm. Reasons cited include new tools (e.g., <\/span><a href=\"https:\/\/blog.docker.com\/2018\/12\/docker-app-and-cnab\/\"><span style=\"font-weight: 400;\">Docker App<\/span><\/a><span style=\"font-weight: 400;\">, which solved some packaging issues), the realization that Kubernetes did not meet their needs in certain ways (e.g., there was no way to grant individual users access to a subset of nodes), and the \u201csimplicity and convenience\u201d of Swarm most closely matched the team\u2019s philosophy and processes.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">While the reasons for moving back to Swarm are themselves compelling, the sequence of moves in itself gives Docker a very strong narrative argument for Swarm\u2019s survival in a market that is so enchanted with Kubernetes. <\/span><\/p>\n<h1><span style=\"font-weight: 400;\">Docker gets a lot done in a demo<\/span><\/h1>\n<p><span style=\"font-weight: 400;\">As a medievalist, I appreciated the <\/span><i><span style=\"font-weight: 400;\">Game of Thrones<\/span><\/i><span style=\"font-weight: 400;\"> themed demos presented during the <\/span><a href=\"https:\/\/www.docker.com\/dockercon\/2019-videos?watch=dockercon-2019-keynote-day-1\"><span style=\"font-weight: 400;\">first day\u2019s keynote<\/span><\/a><span style=\"font-weight: 400;\">. <\/span><\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">Game of Thrones themed demo at DockerCon \ud83d\ude02 <a href=\"https:\/\/t.co\/KhLmHE9Cl3\">pic.twitter.com\/KhLmHE9Cl3<\/a><\/p>\n<p>&mdash; Dr KellyAnn Fitzpatrick (@drkellyannfitz) <a href=\"https:\/\/twitter.com\/drkellyannfitz\/status\/1123269606897004544?ref_src=twsrc%5Etfw\">April 30, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p><i><span style=\"font-weight: 400;\">GoT <\/span><\/i><span style=\"font-weight: 400;\">references aside, the setup showcased <\/span><a href=\"https:\/\/blog.docker.com\/2019\/04\/announcing-docker-enterprise-3-0\/\"><span style=\"font-weight: 400;\">new Docker Enterprise 3.0<\/span><\/a><span style=\"font-weight: 400;\"> features through the lens of developer productivity and with the promise that \u201cAs developers you simply need to focus only on writing code, complaining on Twitter, and going to Stack Overflow when you get stuck\u2026.not learning a whole new methodology.\u201d Speed and ease of deployment were highlighted as two key components in developer productivity. The audience saw an app created in Docker Desktop Enterprise and deployed with the Docker Kubernetes Services (DKS) in a matter a minutes. A third key point highlighted was that Docker Enterprise 3.0 ensures that Kubernetes environments on developer desktops match those of test and production servers: a move to deliver on the promise of consistency offered by containers.<\/span><\/p>\n<h1><span style=\"font-weight: 400;\">When possible, focus on affordances over hype<\/span><\/h1>\n<p><span style=\"font-weight: 400;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-medium wp-image-107\" src=\"http:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth-300x225.jpg\" alt=\"Part of the ARM display at the DockerCon 2019 Ecosystem Expo\" width=\"300\" height=\"225\" srcset=\"https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth-300x225.jpg 300w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth-768x576.jpg 768w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth-1024x768.jpg 1024w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth-1536x1152.jpg 1536w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth-480x360.jpg 480w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth-107x80.jpg 107w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth-836x627.jpg 836w, https:\/\/redmonk.com\/kfitzpatrick\/files\/2019\/06\/DC19-ARM-booth.jpg 2016w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/>With social media abuzz with news of the <\/span><a href=\"https:\/\/thehackernews.com\/2019\/04\/docker-hub-data-breach.html\"><span style=\"font-weight: 400;\">DockerHub data breach<\/span><\/a><span style=\"font-weight: 400;\"> that Docker announced the Thursday before the conference, I had expected to hear a lot about the breach in the various meetings I had the day before DockerCon began. While there was some talk of the breach, I was pleasantly surprised to hear much more talk of and enthusiasm for the <\/span><a href=\"https:\/\/www.arm.com\/company\/news\/2019\/04\/docker-and-arm-partnership\"><span style=\"font-weight: 400;\">ARM partnership<\/span><\/a><span style=\"font-weight: 400;\"> announcement that came out the Wednesday before. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Likewise, while for some Steve Singh\u2019s last DockerCon as CEO may be overshadowed by the <\/span><a href=\"https:\/\/techcrunch.com\/2019\/05\/08\/steve-singh-stepping-down-as-docker-ceo\/\"><span style=\"font-weight: 400;\">announcement a week later that he would be stepping down from the role<\/span><\/a><span style=\"font-weight: 400;\"> (he will stay on as chairman), I am instead impressed by the fact that he opened <\/span><a href=\"https:\/\/www.docker.com\/dockercon\/2019-videos?watch=dockercon-2019-keynote-day-2\"><span style=\"font-weight: 400;\">his last keynote<\/span><\/a><span style=\"font-weight: 400;\"> with an announcement of the creation of the <\/span><a href=\"https:\/\/www.docker.com\/foundation\"><span style=\"font-weight: 400;\">Docker Foundation<\/span><\/a><span style=\"font-weight: 400;\">. This philanthropic foundation supports organizations like <\/span><a href=\"https:\/\/codepath.org\/\"><span style=\"font-weight: 400;\">CodePath<\/span><\/a><span style=\"font-weight: 400;\">, which has gotten some exposure in <\/span><a href=\"https:\/\/www.insidehighered.com\/news\/2019\/06\/05\/nonprofit-boot-camp-infiltrates-college-computer-science-curricula\"><span style=\"font-weight: 400;\">recent higher ed discussions<\/span><\/a><span style=\"font-weight: 400;\">, and when Singh welcomed CodePath CEO and founder <\/span><a href=\"https:\/\/twitter.com\/MichaelwEllison\"><span style=\"font-weight: 400;\">Michael Ellison<\/span><\/a><span style=\"font-weight: 400;\"> to the stage to talk about his organization\u2019s goal of increasing diversity in tech through opportunity and access, it made me want to see more segments like this in more keynotes at more tech conferences.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Finally, one of the topics that buzzed continuously through many of the conversations I had at this year\u2019s DockerCon was attendance numbers for conference itself, with some gossip postulating that this year\u2019s attendance had fallen to 3000 from 6000 for the June 2018 event. Much of this buzz theorized that potential attendees had jumped ship for other events (such as <\/span><a href=\"https:\/\/www.cncf.io\/blog\/2019\/02\/12\/kubecon-cloudnativecon-north-america-2018-conference-transparency-report-a-record-breaking-cncf-event\/\"><span style=\"font-weight: 400;\">KubeCon<\/span><\/a><span style=\"font-weight: 400;\">), perhaps as part of what my colleagues Rachel and James have termed the <\/span><a href=\"https:\/\/redmonk.com\/rstephens\/2019\/05\/02\/hype-cycles-and-pendulum-swings\/\"><span style=\"font-weight: 400;\">Hype Cycles and Pendulum Swings<\/span><\/a><span style=\"font-weight: 400;\"> that constitute the tech industry. It turns out the the attendance drop was not so dramatic (at 4200 attendees); in any case, as my colleague <\/span><a href=\"https:\/\/redmonk.com\/sogrady\/2018\/05\/30\/in-defense-of-small-conferences\/\"><span style=\"font-weight: 400;\">Stephen has noted<\/span><\/a><span style=\"font-weight: 400;\">, there is something to be said about the quality of developer experience at smaller events. I would argue that it is also important to consider why attendees make their way to an event. For my part, I would take one attendee who (like my walking comrade) is there to take practical steps of education and adoption over ten who are there for swag and cocktail receptions and hype.<\/span><\/p>\n<p><b>Disclaimer:<\/b><span style=\"font-weight: 400;\"> Docker is a client and paid for my T&amp;E for DockerCon 2019.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the best parts about being an analyst: you get to choose the experiential framework from which you analyze a given piece of tech or event. Events, especially, offer us a myriad of lenses. At a keynote you can choose to sit up front in a section reserved for press and watch the reactions<\/p>\n","protected":false},"author":47,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[14],"tags":[],"class_list":["post-105","post","type-post","status-publish","format-standard","hentry","category-conferences"],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/posts\/105","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/comments?post=105"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/posts\/105\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/media?parent=105"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/categories?post=105"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/kfitzpatrick\/wp-json\/wp\/v2\/tags?post=105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}