Containers DEVELOPMENT and MANAGEMENT

THE 2018 DZONE GUIDE TO Containers DEVELOPMENT AND MANAGEMENT

VOLUME II

RESEARCH PARTNER SPOTLIGHT THE DZONE GUIDE TO CONTAINERS: DEVELOPMENT AND MANAGEMENT

Key Research Findings

BY JORDAN BAKER - CONTENT COORDINATOR, DZONE

DEMOGRAPHICS • 27% of respondents work for organizations sized 100-999 711 software professionals responded to this year's Containers employees; 19% for organizations that employ 1,000-9,999 Guide Survey, with 507 complete responses. The demographics people; 14% for organizations sized 10,000+ employees. for these respondents are as follows: • In terms of industry, 27% work for software vendors; 14% • 40% identify as software developers/engineers; 19% work in finance/banking; 9% work in e-commerce; 9% identify as developer team leads; 11% identify as architects. work in consulting.

• 30% work for organizations headquartered in the United • The average experience among respondents is States; 25% work for organizations headquartered approximately 12 years. in Europe; 14% work for organizations headquartered in South/Central Asia. • 59% primarily code in Java, 9% in JavaScript/Node.js, and 8% in Ruby. • 34% of respondents work on teams sized two to DZONE.COM/GUIDES five members; 32% work on teams with six to 10 DZONE.COM/GUIDES members; 11% are part of teams with 11-15 members.

GENERAL USE OF CONTAINERS AND told us that their organization is considering adopting PREVALENCE OF DOCKER container technology. Of those who use containers, they 45% of respondents told us that their organization appear to be rather heavily utilized throughout the is currently using container technology, while another 18% development process. 87% of container users told us they

GRAPH 01. Does your organization currently use container GRAPH 02. What benefits do container technologies offer technologies? your organization?

THE DZONE GUIDE TO CONTAINERS: DEVELOPMENT AND MANAGEMENT PAGE 2 OF 8 DZONE.COM/GUIDES THE DZONE GUIDETO CONTAINERS: DEVELOPMENT AND MANAGEMENT told useDocker usthatthey for theircontainers, 49%use third, respectively. Interestingly, ofthosedevelopers who Swarm (29%)andAmazon ECS (28%)coming insecond and adoption rate inour2017Containers withDocker Survey), chose Kubernetes (whichsawamassive jumpfrom a35% orchestration/management technologies, 53%ofrespondents to container-based methodologies andtools. Interms of was lessofaconsensus amongrespondents whenit came While Docker reigns supreme asacontainer technology, there MANAGEMENT ANDREGISTRIES METHODS ANDTOOLS: ORCHESTRATION/ at SolarisZones. 90% are lookingatDocker, 18%atDocker Enterprise, and6% currently evaluating andconsidering container technology, third with5%ofresponses. Andofthoseorganizations thatare Enterprise. Thecontainer technology LXC came inadistant majority (91%)whouseDocker, and19%whouseDocker Among thosewhousecontainers, there isanoverwhelming of theirworkload. work inorganizations thathave containerized nomore thanhalf containerized workload of26-50%.Thus,64%respondents 1-25% oftheirworkload, and20%work inorganizations witha respondents work for organizations that have containerized in production. Breaking this down, ofcontainerized 44% containers typically saidthey runoneto 100containers A majority(61%)ofrespondents whoseorganizations use a private cloud,and45%onlocal hardware. organizations housetheircontainers on ahosted cloud,48%on containers are runisalsorather distributed. evenly 51%of in staging. The environments across whichthese 63%in QA/testing, environment, a DevOps and54% use the technology environments, in development 73%in your organization? GRAPH 03. What challengesdocontainers present to THE DZONE GUIDETO CONTAINERS:

DEVELOPMENT ANDMANAGEMENT Nexus, chosenby 18%ofrespondents. of 54%;thesecond mostpopularchoice for thiscategory was the mostpopularchoice for consideration, withaselectionrate still evaluating theirregistry needs,Docker Hubisfar andaway Of thoserespondents whotold usthattheirorganizations are Docker users optfor Docker Hubfor theircontainer registries. those organizations we know useDocker, we seethat53%of choosing Artifactory. Ifwe again compare thesenumbers to Hub for theirregistries, with21%optingfor Nexus and20% better. Ofthoseorganizations usingcontainers, 43%useDocker When itcomes to container registries, Docker products fair Swarm, and30%Amazon ECS. technologies, 57%are considering Kubernetes, 33%Docker those organizations stillevaluating orchestration/management 25% usedDocker’s own orchestration tool, Docker Swarm. For Kubernetes astheirorchestration/management tool andonly BENEFITS OFUSINGCONTAINERS as developers gain more experience withcontainers, building applications (75%)andgreater modularity(64%).And, benefit ofcontainers, followed by enhanced scalability when stated thatfaster deployment time(77%)was thebiggest The answer boilsdown to three majorbenefits.Respondents What isitaboutcontainers thatmakes themsowidelypopular? tasksdevelopment harder. their jobseasier, withonly7%stating thistechnology made a resounding 75%told usthatcontainers have indeedmade audience, "Have containers madeyour jobeasier orharder?", So, didcontainers live upto thehype? Whenwe asked our told expected usthatthey containers to make theirjobseasier. expectations priorto usingcontainers, 82%ofrespondents the lives ofdevelopers easier. Whenasked abouttheir A majorsellingpointofcontainer technology isthatitmakes or harder? GRAPH 04.Have containers madeyour jobeasier

PAGE 3OF8 THE DZONE GUIDE TO CONTAINERS: DEVELOPMENT AND MANAGEMENT

these benefits only seem to increase. In our 2017 Containers employees worry about developer experience with containers. survey, 56% of respondents reported faster deployment as a Other oft reported challenges among container adopters were benefit (a year-over-year growth rate of 21%), and 53% reported refactoring/re-architecting legacy applications (50%) and scalability as a plus (which corresponds to a 22% growth in application performance monitoring (33%). Though, again, this year's survey). Interestingly, despite the prominence of as development teams gain more experience with container Java developers among the DZone community (as noted in the technology, these problems are becoming less of an issue. In Demographics section), the percentage of Java developers who last year's survey, 68% reported developer experience as a claimed faster deployment (27% of Java devs), scalability (36% major challenge, and 70% reported refactoring/re-architecting of Java devs), and modularity (31% of Java devs) were of less legacy applications as an issue. Thus, it appears that while concern lagged behind coders from other language ecosystems. enterprise-level software teams are still learning how to best The language ecosystems that derive the most benefit from use containers, they are quickly adapting. the use of containers, as stated by the responses, tended to be Of those respondents whose companies are still deliberating Python, Node.js, and Ruby. on the use of containers, a lack of developer experience with containers was the largest concern, chosen by 71%. The second CHALLENGES IN ADOPTING CONTAINERS largest challenge reported among this group was refactoring/ As stated earlier, despite the large-scale popularity of re-architecting legacy applications (70%), followed by a distant containers, and the benefits of faster deployment, scalability, third of application performance monitoring (38%). Here and modularity for a multitude of language ecosystems, 25% again, we see concern among enterprise-level developers of organizations are still not using containers and 18% are about containers, as 23% of those reporting refactoring legacy only considering adopting them. To understand why some applications work for organizations with 100-999 employees, organizations chose not to adopt container technology, let’s 25% for organizations with 1,000-9,999 employees, and 17% for look at the challenges containers presented to those who have organizations with 10,000 or more employees. adopted them, the apparent challenges present for those

considering adopting containers, and the reasons why some Among those organizations that have chosen not to adopt organizations and developers have decided not to adopt containers, 48% report lack of developer experience as container technology. a primary concern and 24% stated that refactoring/re- DZONE.COM/GUIDES architecting legacy applications was a concern. The only DZONE.COM/GUIDES The biggest impediment reported by containers users (56%) is a organizations for which ensuring application and network lack of developer experience with this technology. Interestingly, security was a deal breaker were those sized 1,000-9,999 when we compare this concern with organizational size, employees, with 21% of respondents who work for such we see that the larger the organization, the bigger the organization reporting thusly. concern over lack of developer experience with containers. 32% of respondents working for organizations sized 100- 999 employees consider this a major obstacle and 25% of respondents working for organizations with 1,000-9,999

GRAPH 05. What percentage of your organization's GRAPH 06. How many containers is your organization workload is containerized? running in production?

THE DZONE GUIDE TO CONTAINERS: DEVELOPMENT AND MANAGEMENT PAGE 4 OF 8 To sy continers hve mde n impct in softwre development would be n understtement. More nd more developers nd orgniztions re looking to dopt continers to mke development nd testing esier. Continers re lso nturl ﬁt with microservices rchitectures tht cn improve deployment speed nd softwre qulity. Since the hype nd excitement is showing no sign of slowing down, is it worth climbing the mountin? Let’s look t wht over 500 DZone survey respondents think.

Orgniztions hve seen enormous beneﬁts from dopting continers. 77% hve reported fster deployments, nd 75% noticed they could better scle pplictions. Other beneﬁts include modulrity (64%), portbility (55%), nd environmentl consistency (47%).

Of those who hve dopted continers, 81% of respondents expected their jobs would be esier s result, nd 75% ctully noticed their jobs were esier. Only 7% found tht their jobs were more diﬃcult, nd 18% sw no chnge. It seems continers re indeed worth the hype, or t the very lest don’t mke things more diﬃcult.

As expected, Kubernetes is the most considered orchestrtion tool mong those who re considering continers (57%), followed by Docker Swarm (34%), Amazon ECS (31%), and Google Kubernetes Engine (20%). Only 7% of organizations are not considering orchestration tools.

Severl chllenges re mking orgniztions nervous bout dopting continers. The two biggest by fr re lck of developer experience (71%) nd re-fctoring legcy pplictions (70%). Other concerns include ppliction nd network security (42%) nd performnce monitoring (40%).

Orgniztions nd tems re moving fst on continers. 63% of orgniztions who hve dopted continers did so in less thn six months, nd of orgniztions who hve not yet dopted continers, only 30% hve spent over six months evluting them.

CPRGT DOE.CM 2018 THE DZONE GUIDE TO CONTAINERS: DEVELOPMENT AND MANAGEMENT

Containerization vs. Virtualization CHECKLIST The description above about containerization sounds pretty similar to virtualization, right? It is true that this concept has emerged from virtualization, but there is a huge difference between these two. Let's compare them:

APPLICATION ABSTRACTION HARDWARE ABSTRACTION Should Virtualizes the OS Virtualizes hardware Every container shares the same Every VM has its own hardware, base underlying OS application, and OS

Runs on top of hypervisor installed Runs of top of the host of the OS You Use on a bare-metal system Lighter overhead Heavier overhead

Containers? While virtualization has provided the abstraction of a machine, you can call containers a moderately upgraded version of VMs.

Container Implementation Challenges With the latest infusion of an open-source platform by Docker, BY SHRAVANI CHAKRABORTY, INTELLIPAAT this technology has grabbed a lot of attention because of the benefits achieved by its implementation. However, there are certain challenges that are faced during deployment.

• One OS crash fails the entire system: Containers are considered to be resource-efficient, as all the containers access the same OS. Potential Benefits of Containerization However, this provision makes the entire system prone to failure — The technology of containerization gained momentum after Docker a single crash in the OS will cause all the containers to crash. launched its open-source container technology and AWS started providing container services supported by Docker. The benefits • Compatibility issues: Migrating containers can be a tedious task, as you face a challenge if the server OS is not compatible, which DZONE.COM/GUIDES harnessed by this technology are: DZONE.COM/GUIDES limits its migrations ability. • Platform independence: An application that is encapsulated • Not suitable for all tasks: Containerization is better-suited for with all of its dependencies into a container is able to run on any applications that are made of small chunks of applications and can machine, making it a highly portable technology. be divided into microservices. However, some applications are not • Rewriting code is not required: One of the prime benefits a formed in this pattern, so it is not possible to subdivide. Still, these company can harvest is that developers need not write code all applications can be successfully run on virtual machines. over again for every platform the container is going to run on. This saves time, money, and effort all at the same time. How to Decide If You Should Implement • Best-suited for in-house application development: Containers Containerization of applications is best-suited for companies Your decision depends purely on your requirements. If you need to that develop in-house applications. This helps in porting run several instances of a single application, then implementing the applications and makes sure that these will function in containers can be useful. But if you want to run multiple applications, production as it used to during development. then you should go for VMs.

• Dividing any application: Containerization not only helps If you have to run just one operating system, then containers can divide in-house applications — any kind of application can be be beneficial. At the same time, if you want the freedom of running successfully divided into microservices, making the entire system any operating system, then VMs may be the better option for you. lot faster than before. Though these differences may make you consider implementing both technologies, these can co-exist on a single system serving different • Containers are quite lightweight, as in Lightweight in nature: purposes inside a firm. order to port an application, the entire operating system needs to not be encapsulated along with it. It is just the application that However, this technology is still in its nascent stage, setting space goes inside the container, which makes it less complicated and for more cutting-edge technologies to revolutionize the digital more light-weight. economy altogether.

THE DZONE GUIDE TO CONTAINERS: DEVELOPMENT AND MANAGEMENT PAGE 6 OF 8 DZONE.COM/GUIDES THE DZONE GUIDETO CONTAINERS: DEVELOPMENT AND MANAGEMENT SPONSORED OPINION PARTNER SPOTLIGHT based applications. applications. based container- your operating and building like tasks, important more on work can you so infrastructure, container your of care take can We ready. enterprise and friendly, developer native, container is which management, certified on bare metal or virtual machines. machines. virtual or metal bare on provisioned be can which IaaS highly-available and a fully-managed leveraging while nodes, worker your to access SSH You get Helm. and DNS, Dashboard, Kubernetes as such addons, cluster built-in includes Engine Container Oracle images. private manage and store to you allows and compatible v2 Docker fully is Registry The addons. proprietary no with code Kubernetes upstream standard, and runtime, Docker-based the use We first. developers put and Oracle Container Engine With easy. Kubernetes makes Oracle Management End-To-End Lifecycle Container Container Native, Developer Friendly, andEnterprise Ready Kubernetes Oracle Container Engine(OKE) andRegistry Open Source to Containers and Oracle’s Commitment release pipelines, rolling releases and rollbacks, elastic scaling, and and scaling, elastic rollbacks, and releases rolling pipelines, release management like application capabilities automatedenterprise leverage and scale, at Kubernetes on containers Docker run and Oracle Cloud is pleased to launch launch to pleased is Cloud Oracle Pipelines. Container and Containers course, of and Platform, AI Blockchain, in ERP, IoT, HCM, offerings includes portfolio SaaS and PaaS, IaaS, Oracle’s yet? Cloud Oracle considered you have but Cloud, Google and Azure Microsoft Services, Web Amazon about heard have you Sure, Kubernetes (OKE)andRegistry PRODUCT PROFILE CATEGORY WEBSITE developer.oracle.com and and Registry , which allow developers to deploy deploy to developers allow , which THE DZONE GUIDETO CONTAINERS: Oracle Container Enginefor Oracle Cloud are built with open source technologies technologies source open with built are , you leverage Kubernetes- , leverage you TWITTER @oracledevs DEVELOPMENT ANDMANAGEMENT Registry, please reach us at at us reach please Registry, and Kubernetes for Engine Container Oracle of trial To afree take Oracle’s flagship products — products flagship Oracle’s that important so are Containers Terraform. and Kubernetes, Docker, include that projects community to contributes and (CNCF) Foundation Computing Native Cloud the of member aplatinum is Oracle ease. with workflows CI/CD multi-branch multi-stage create Oracle offers offers Oracle addition, In (CI/CD) toolchain. Deployment Integration/Continuous Continuous any with interoperate can Registry and Engine Container Oracle development, application and DevOps To support environments. Kubernetes for control and visibility gain can teams DevOps and containers, with quickly started get can Developers self-healing. others — which are available via the the via available are —which others • • • • • • Yes OPEN SOURCE? FEATURES PRINCIPAL DEVELOPER MARKETINGDIRECTOR -ORACLE CLOUD WRITTEN BY AKSHAI PARTHASARATHY workflows and specific automation and specific workflows tasks You can find out more at the the at more out find You can Leverage Helm and DNS, Dashboard, Kubernetes with along CLI, and API REST full Exercise more much and domains, availability multiple balancing, load storage, persistent VMs, servers, metal bare Use public repositories and private highly-available in images container share and Store apps container-based manage and deploy Easily Container Pipelines Container Pipelines(Wercker) [email protected] Oracle Java BLOG blogs.oracle.com/developers ( Wercker Docker store Oracle Developers Portal , MySQL ), which allows you to to you allows ), which . , Oracle Linux for complex CI/CD CI/CD complex for

. , and , and PAGE 7OF8 Join the World’s Largest Developer Community

Download the latest software, tools, and developer templates

Get exclusive access to hands-on trainings and workshops

Grow your network with the Developer Champion and Oracle ACE Programs

Publish your technical articles—and get paid to share your expertise

ORACLE DEVELOPER COMMUNITY developer.oracle.com Membership Is Free | Follow Us on Social:

@OracleDevs facebook.com/OracleDevs

PUB NOTE: Please use center marks to align page. Resize Job #: R_418M_CRP00211_JoinLrgstDevCmnty_8.5x11 PRODUCTION NOTES RELEASED Ref #: M_418M_CRP00206_JoinLrgstDevCmnty_8x10.5 READER LASER% Headline: Modern ERP Cloud 5/22 Live: N/A Trim: 8.5” x 11” 01 2018 Bleed: 9” x 11.5” 8.5” x 11” Please examine these publication materials carefully. Fonts: Univers LT Std. 75 Black, 65 Bold, 55 Roman, 45 Light, Any questions regarding the materials, please 67 Bold Condensed, 57 Condensed contact Darci Terlizzi (650) 506-9775