I’m sure by now everyone reading this has heard a great deal about Continuous Delivery, which I’ll refer to as CD from here on. In short, you do it to accelerate the process of software delivery – which means you can see the value of coding more quickly.
DevOpsCon 2016 will take place in Munich between 5-8 December. What is the idea behind DevOpsCon? How does this conference bring together a broad range of topics such as Continuous Delivery to Microservices, Cloud, Container and Corporate Culture? Program-Chair Sebastian Meyen will give you some insights in this article.
In his DevOpsCon keynote, Markus Andrezak, the founder of ueberproduct, explains why the aim of DevOps should be effectiveness (doing the right thing) and not efficiency.
In his DevOpsCon keynote, Jeff Sussna talks about Conway’s Law and explores the relationship between organizations and systems.
It’s that time of the year again! According to Puppet’s newest DevOps Salary Report, “DevOps engineers, architects, software developers and engineers, and systems developers and engineers in the United States are more likely than not to make more than $100,000.” Let’s see what else is new.
In the emerging world of DevOps and the cloud, most developers are trying to learn new technologies and methodologies. The focus tends to be on adding capabilities such as resiliency and scaling to an application. Still, one critical item consistently overlooked is security. We talked to JAX London speaker Steve Poole about what can be done to keep your system secure and what happens when you leave the door open.
The million-dollar question about the level of productivity in software development teams is the following: How does their productivity scale with the team size? Forget everything you knew about the ideal team size. Are you familiar with the Ringelmann effect?
Each Monday we take a step back and analyze what has happened in the previous week. Last week we presented the fifth release candidate of Angular 2, we shed some light on what Java Champion Jeff Genender thinks of Java EE 8 and we launched a microservices checklist. Our first interviewee was Viktor Farcic, Senior Consultant at CloudBees. But that’s not all.
“DevOps isn’t any single person’s job — it’s everyone’s job.” Practicing DevOps in the true sense of the word may be challenging, but once you’ve overcome the obstacles and preconceptions, everything becomes easier. We asked Atlassian’s Michael Knight and Nick Wright to tell us how this company benefits from (genuinely) putting DevOps into practice.
I learned the hard way building PaaS and SaaS frameworks, and perhaps there is no easy way, but here are some tips on how you can move beyond CI to CD by taking advantage of Jenkins Workflow.
Do agile and DevOps really go hand in hand in the real world? Can an agile transition be considered successful without DevOps? What do we need to understand about agile and DevOps? These are just a few questions that have remained unanswered. We talked to Zubin Irani, CEO at cPrime, a full-service consultancy that implements agile transformations and delivers agile solutions, about the importance of agile in today’s tech environment and what it means to be fully agile.
From nimble startups to large enterprises, organizations across all industries are actively adopting DevOps practices to gain and maintain a lasting business advantage over their competitors. Making the transition to a DevOps culture can be difficult, however, especially for enterprises.
Learning how to operate reliably at scale in a cloud environment was one of the challenges Netflix faced when it migrated all its services to the cloud. JAXenter editor Gabriela Motroc talked to Mike McGarr, the Engineering Manager for the Netflix Developer Productivity team and JAX DevOps speaker, about Netflix’s decision to migrate its services to the cloud, the challenges the company faced, the lesson learned and the Netflix culture.
This year at DevOpsCon we are trying to break the pattern of definitions. Our speakers are teaching us that without embracing the two-pizza team concept and acknowledging that open source is now default the DevOps conversation cannot evolve.