Weekly Top 10: QA, Microservices, and Where’s the Heat in DevOps
Weekly Top 10: QA, Microservices, and Where’s the Heat in DevOps
A weekly top ten of articles outside of DZone, curated by the team at Electric Cloud.
Join the DZone community and get the full member experience.Join For Free
Read why times series is the fastest growing database category.
This week saw DevOps news ranging from QA testing to microservices to metrics. Continue reading this week’s top posts to see where the DevOps journey is heading, and what are some of the trends, tools and practices that are emerging to assure quality, speed, and security of your releases. As always, stay tuned to all the news coming from @ElectricCloud on DevOps and Continuous Delivery throughout the week to stay in the know on all things DevOps.
1) QA in the DevOps Era
In software approaches that produce monolithic applications, it is not uncommon to find siloed teams, with development, testing and operations each an island unto themselves. The responsibilities of test and development are distinct from each other and are not meshed into a hybrid team as you might see in advanced DevOps shops. “QA (quality assurance) always comes late in the game to verify or test the software developed by the development team against the predefined specifications know as software requirements,” says Venkata Vinay Pandella, team lead at Nisum Technologies Inc.
2) Making Deployment Automation Work for Your Business
Deployment automation is becoming less of a luxury and more of a requirement for software development teams that are looking to remain competitive in the current marketplace. Primarily, an automated deployment solution allows you to write your processes once, get them exactly the way you want, automatically run them, and reuse the procedures every time you deploy a new application or update across the development process in a more efficient, reliable, and predictable way.
3)7 Steps to Choosing the Right DevOps Tools
Most developers have moved beyond understanding the business value of DevOps and on to how best to implement it. The former was easy to define, while the latter has been more difficult. Why? The number and types of problem domains differ greatly from one problem domain to the next. The types of processes and tools that developers and operations professionals can apply differ a great deal as well.
4) Typical Enterprise Uses Six Cloud Computing Services, Survey Shows
More company technology workloads are shifting to both public and private clouds, with a notable emphasis on hybrid cloud adoption. At this time, organizations are using or piloting at least six different clouds, on average. Also, the epicenter of public cloud appears to be the Seattle area — while Amazon Web Services (AWS) continues to dominate the public cloud market, Microsoft (MSFT -9.57%) Azure continues to gain ground.
5) Analyst View: Where’s the Heat in DevOps?
Consumers, empowered by rich software interactions with access to Internet resources, have never had more power or choices. DevOps provides a set of practices and cultural changes—supported by complementary tools—that automates the software delivery pipeline, enabling organizations to win, serve, and retain these consumers better and faster than ever before.
6) The State of the Cloud in 2016: DevOps, Docker Momentum Grows as Hybrid Hits its Stride
Hybrid cloud adoption has grown significantly while DevOps and Docker uptake continues to explode, according to the latest RightScale State of the Cloud research report.
The report, which surveyed more than 1,000 technical professionals, found that the more things change, the more they stay the same with regards to the overall trends pervading the cloud industry. Hybrid cloud adoption has gone up from 58% in 2015 to 71% among respondents, with private cloud going up from 63% to 77%. Similarly, DevOps adoption rose to almost three quarters (74%), with Docker uptake more than doubling from 13% last year to 27% in 2016.
7) DevOps vs ITIL?
By Dr. Wissam Raffoul| Published on @computerworldau
There is debate within the IT industry about whether or not DevOps can replace ITIL. From the ITIL perspective, many IT organisations, especially in Australia, have been implementing ITIL processes since 1994 with significant investment in technology and professional services. Hence, it is impractical to just drop ITIL and adopt DevOps. This is because firstly, DevOps covers only Release Management, which is only one process of the 26 processes of ITIL v3; secondly, DevOps in not different from mature ITIL Release Management.
8) What are Containers and Microservices?
Containers encapsulate discrete components of application logic provisioned only with the minimal resources needed to do their job. Unlike virtual machines (VM), containers have no need for embedded operating systems (OS); calls are made for OS resources via an application programming interface (API). Containerisation is, in effect, OS-level virtualisation (as opposed to VMs, which run on hypervisors, each with a full embedded OS). Containers are easily packaged, lightweight and designed to run anywhere. Multiple containers can be deployed in a single VM. A microservice is an application with a single function, such as routing network traffic, making an online payment or analysing a medical result.
9) A QA Professional’s Guide to Surviving a Software Failure
“What’s the worst that could happen?” That sentiment may seem funny when someone says it right before loading up on the sriracha sauce or running their first 5K. But QA professionals know all too well that sending software to production without catching major bugs will result in the worst-case scenario. Millions of dollars, or even lives, can be lost due to a software failure. Sometimes, even an isolated issue can result in a situation that makes a QA professional want to face zombies rather than their peers on the development team. But while a serious crash can be a blow to any QA professional’s ego, it doesn’t have to be the end of the world.
10) How Do You Measure DevOps? What Does That Even Mean?
What are some of the metrics you should be monitoring to track your DevOps efforts, and which metrics should you abandon? Last Tuesday I participated in an online panel on the subject of Measuring DevOps, as part of Continuous Discussions (#c9d9), a series of community panels about Agile, Continuous Delivery and DevOps.
Published at DZone with permission of Anders Wallgren , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.