From waterfall to DevOps, there have been a multitude of movements that have strived to drive software programming efficiency forwards. But not all have been able to liberate developers from the pressure to deliver results faster.
Any enterprise that can begin treating its infrastructure as code, opens itself up to major performance improvements with automated tests, code repositories and build servers. This excerpt from “Amazon Web Service in Action” introduces us to the basics of Infrastructure as Code.
Bill is an IT manager at Parts Unlimited. It’s Tuesday morning and Bill gets a call from the CEO. The company’s new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but is massively over budget and very late. Bill must fix the mess in ninety days or else Bill’s entire department will be outsourced.
Programmers continue to suffer from burnouts, increasing responsibilities and a growing pressure to deliver more and more functionality to customers. But what role do developers need to play in business? And what is the true purpose of business?
Pierre Fricke is back to discuss DevOps and its role in what he is the calling the battle between the creative developers and the process junkies. What will the future bring for the role of DBAs?
How can you help your company navigate the DevOps path? Gordon Haff believes it takes strong sponsorship from management, but you also need to curate your approach to what fits in with your organization and company values.
Jeff Sussna wants to elevate the manageability of microservices to the DevOps level. To do this, organizations have to shift their definition of system-level quality from stability to resilience. Let us start treating microservices as the complex systems they are.
Setting the rules, planning ahead, keeping important questions in mind – all this and more on the DevOps journey of development to delivery in software with James Fryman.
Are your continuous integration and delivery efforts for documentation floundering? It might serve you well to read up on how OpenStack treat documents like code and implement a strategy to successfully merge and publish.
Like with all enterprise processes, there are dos and don’ts. DevOps Do #1: Do switch to a DevOps approach with a DevOps professional, says DevOps expert Giant Swarm’s Matthias Lübken. Don’t #1: Never ever be ambitious with goals.
The countdown to the JAX London 2015 is on and we’ve put the spotlight on DevOps and Microservices. Come along and hear from leading technologists and experts on the topics that are making waves in the IT world.
The partnership that exists between open source and DevOps is undeniable to Mark Hinkle, who believes the culture behind DevOps is paramount if you want improved delivery of software and services.
Microservices advocate James Lewis tells us why IT systems will always be built the way the organisations are, and why large organisations are feeling the pain of not adopting new IT approaches.
Customer goals are not always at the forefront of the design process, but Jeff Sussna believes that IT must revise its approach to ‘usability’ in order to achieve true quality in the mind of the customer. Customer experience here is key.